openSUSE Factory December 2012

factory@lists.opensuse.org

87 participants
90 discussions

[opensuse-factory] Factory devel projects

by Kyrill Detinov

Hello. Where can I find a list of devel projects? I see in Wiki: https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory#How_to_add_a_… "A list of the current devel projects can be found in the drop-down menu on top of this page[1]." Is there a list in plain text format anywhere? [1] https://build.opensuse.org/project/status?project=openSUSE%3AFactory -- WBR Kyrill

9 years, 6 months

[opensuse-factory] kernel-default-3.6.10-15.1.i586 : cannot see HDD SDA

by ellanios82

Hello List Tumbleweed : kernel-default-3.6.10-15.1.i586 __________ my system is on /dev/sdb which is 1 TB SATA HDD - i have a /dev/sda for backups, which is 360 GB PATA HDD .............. kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK ................. - with kernel-default-3.6.10-15.1.i586 i get : command : _______ # mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist .................... [ because do not feel sufficiently 'advanced' to wrestle with bugzilla reports, since kernel 3.4.6-2.10 i have been hoping this trouble would be solved and 'go away', but, no such luck ] best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] How secure boot grub2 is going to find its configuration?

by Andrey Borzenkov

I am still not sure how secure grub2 is going to find its grub.cfg. Normally its location is dynamically added to core.img. In case of secure grub2 core.img is prebuilt and signed during package creation (or may be signed later, not sure). So it is impossible to store information about grub root directory there. The only place which can be guaranteed to be auto-detected is ESP itself. But it is not where grub2 related files are installed currently ... Do I miss something here? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] Dropping ksymoops package from Factory and the Base:System repository

by Lars Müller

Hi, ksymoops fails to build for openSUSE Factory since quite some time. Following https://bugzilla.novell.com/show_bug.cgi?id=793544#c2 it doesn't make sense to offer ksymoops when the Linux kernel is built with KALLSYMS enabled. Therefore I'm going to drop the package and ask to get it removed from openSUSE Factory too. If one is willing to keep it please speak up in the next days. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

9 years, 6 months

[opensuse-factory] ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8

by Markus Koßmann

Everytime when grub2-branding-openSUSE is update, I'am getting: ( 6/32 ) Installation von: grub2-branding-openSUSE-12.3-1.16 ..............................[fertig] Zusätzliche rpm-Ausgabe: Generating grub.cfg ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-3.7.0-1-desktop Found initrd image: /boot/initrd-3.7.0-1-desktop Found linux image: /boot/vmlinuz-3.7.0-1-default Found initrd image: /boot/initrd-3.7.0-1-default Found linux image: /boot/vmlinuz-3.6.3-1-desktop Found initrd image: /boot/initrd-3.6.3-1-desktop Found linux image: /boot/vmlinuz-3.6.3-1-default Found initrd image: /boot/initrd-3.6.3-1-default ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 Found Windows 7 (loader) on /dev/sda1 Found openSUSE 11.4 (x86_64) on /dev/sda6 Running fsck -f on that ext4 partition doesn't find any problem however. But on a clone of that partition done with dd that error also shows up. Even if it is not mounted. Very strange. Does anyone have an idea, what might cause that problem, how to fix it and ( if needed) to file a bug against what ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] libreoffice-calc-3.6.3.2.4-4.3.i586 in t'weed : Charts Disappearing

by ellanios82

Hello openSuSErs - after todays update, upon adding to Data input field . . . chart disappears. ............... best wishes for forthcoming new year -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] Plugging in AC Adapter causes 3.7.1 kernel hard lockup

by Phương Võ

Hello, I switched recently to OpenSUSE Tumbleweed from 12.2 and I meet this strange problem, that is the kernel gets hard lockup whenever I plug the AC Adapter in, after that the watchdog tried to shutdown the locked up CPU and I have kernel panic. I tried to look around for solution but couldn't find any, so if anyone can give me a pointer on how to gather more information about this behaviour (so I can file a proper bug report), or even better, a solution, I would appreciate that. Here is a few things I noted: - The lockup only happens with Linux 3.7.1, version 3.2 to 3.5 are trouble-free (I haven't tested with version 3.6 yet) - The backtraces that is shown when the lockup happens are mostly NMI watchdog's, although sometimes there are more backtrace for other CPUs as well (mostly related to hrtimer stuff). - Even if I suspend the computer before plug the adapter in, the lockup still happen right after resuming. Disabling X and using the single user mode don't help either. - Interestingly enough, plugging in before mounting root is fine, that mean the culprit is loaded later, but I don't know how to find exactly which module is causing it (no information from backtrace). Of course, reverting back to OpenSUSE 12.2 will help, but I would like to solve this if possible, after all I can't stay with 12.2 forever. Thank in advance! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] postfix config error on 12.3m3

by Patrick Shanahan

postfix-2.8.12-1.3.x86_64 /etc/postfix/main.cf contains following: daemon_directory = @daemon_directory@ sendmail_path = @sendmail_path@ newaliases_path = @newaliases_path@ mailq_path = @mailq_path@ setgid_group = @setgid_group@ html_directory = @html_directory@ manpage_directory = @manpage_directory@ sample_directory = @sample_directory@ readme_directory = @readme_directory@ which I believe an install macro should have resolved. report to bugzilla ?? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] rkhunter on tumbleweed

by ellanios82

Hello List rkhunter cronjob gives message : { cronscript for rkhunter Author: Lars Vogdt } _______________ " Warning: The following processes are using suspicious files: Command: cron UID: 0 PID: 3198 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: cron UID: 0 PID: 19803 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: egrep UID: 0 PID: 15008 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: rkhunter UID: 0 PID: 20090 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: run-crons UID: 0 PID: 19805 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: sh UID: 0 PID: 19804 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: sort UID: 0 PID: 15009 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: suse.de-rkhunte UID: 0 PID: 20087 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit Command: uniq UID: 0 PID: 15010 Pathname: /etc/crontab Possible Rootkit: Unknown rootkit " ..................... Should I worry, or, not worry ?? .......... best wishes -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

[opensuse-factory] Cursed intel graphics card, freezes desktop at random. Tried 3 different kernels

by Roger Luedecke

I have tried running three different kernels. I have 3.4 3.6 and 3.7 in parallel right now. Behavior is basically the same on all three. I have nearly googled myself into a coma. 3.4 had known intel bugs, many of which were fixed in 3.6.10, hence that install. 3.7 (from tumbleweed) was originally being tested until I read there were regressions regarding the intel drivers. My screen will suddenly become unresponsive, with only the mouse being able to move. Then shortly thereafter that will stop responding as well. It is not possible to drop to TTY. I have to hold the power down. After trying the different kernels, I have tried also the i915.modeset=0 and i915.modeset=1 in grub. The former seems to cause more problems than it solves, changing from a frozen screen to a garbled one. So far the latter is proving stable, though perhaps with slightly degraded graphical performance. > Hippie:/home/roger # hwinfo --gfxcard > 09: PCI 02.0: 0300 VGA compatible controller (VGA) > [Created at pci.319] > Unique ID: _Znp.AyhgUXFyk41 > SysFS ID: /devices/pci0000:00/0000:00:02.0 > SysFS BusID: 0000:00:02.0 > Hardware Class: graphics card > Model: "Intel 945 GM" > Vendor: pci 0x8086 "Intel Corporation" > Device: pci 0x27a2 "945 GM" > SubVendor: pci 0x1179 "Toshiba America Info Systems" > SubDevice: pci 0xff10 > Revision: 0x03 > Driver: "i915" > Driver Modules: "drm" > Memory Range: 0xf0a00000-0xf0a7ffff (rw,non-prefetchable) > I/O Ports: 0x1800-0x1807 (rw) > Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable) > Memory Range: 0xf0b00000-0xf0b3ffff (rw,non-prefetchable) > IRQ: 16 (3038 events) > I/O Ports: 0x3c0-0x3df (rw) > Module Alias: "pci:v00008086d000027A2sv00001179sd0000FF10bc03sc00i00" > Driver Info #0: > XFree86 v4 Server Module: intel > Driver Info #1: > XFree86 v4 Server Module: intel > 3D Support: yes > Extensions: dri > Config Status: cfg=no, avail=yes, need=no, active=unknown > > 10: PCI 02.1: 0380 Display controller > [Created at pci.319] > Unique ID: ruGf.EeuYq4vjbr7 > SysFS ID: /devices/pci0000:00/0000:00:02.1 > SysFS BusID: 0000:00:02.1 > Hardware Class: graphics card > Model: "Intel Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller" > Vendor: pci 0x8086 "Intel Corporation" > Device: pci 0x27a6 "Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller" > SubVendor: pci 0x1179 "Toshiba America Info Systems" > SubDevice: pci 0xff10 > Revision: 0x03 > Memory Range: 0xf0a80000-0xf0afffff (rw,non-prefetchable) > Module Alias: "pci:v00008086d000027A6sv00001179sd0000FF10bc03sc80i00" > Config Status: cfg=no, avail=yes, need=no, active=unknown -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory December 2012