January 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 420876] New: Locale sr_RS.UTF-8 don't exist
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=420876 Summary: Locale sr_RS.UTF-8 don't exist Product: openSUSE 11.0 Version: Final Platform: i386 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: developer(a)beotel.net QAContact: ke(a)novell.com Found By: Localization I'm unable to use UTF-8 characters in non-KDE programs when sr_RS locale is set. Gimp, Pidgin, and Inkscape works only when using ASCII characters. In OpenOffice I can use whatever character I want, but only in text editing - If there is a non-ASCII char in the path of a file that I want to edit (open) - it gives me an error. When I switch back to en_US.UTF-8 locale, everything is OK. I guess, if there were sr_RS.UTF-8 locale, everything would be just fine, but there is no such locale. Here is what locale -a prints: ~> locale -a | grep sr sr_ME sr_RS sr_RS@latin ~> So, sr_RS.utf8, sr_ME.utf8, sr_RS.utf8@latin are missing, I gues. ------------ This is on Fedora 9: ~> locale -a | grep sr_RS sr_RS sr_RS@latin sr_RS.utf8 sr_RS.utf8@latin On Fedora 9 there is no problem like I have on openSUSE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 462009] New: Logitech QuickCam Pro 9000, no video
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=462009 User rsmrcina(a)wi.rr.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462009#c1 Summary: Logitech QuickCam Pro 9000, no video Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rsmrcina(a)wi.rr.com QAContact: qa(a)suse.de Found By: Community User Lenovo Thinkpad T60...With OpenSuse 11.1 my Logitech QuickCam Pro 9000 shows no video. I've tried Kopete and Skype and neither work properly. The camera works fine with OpenSuse 10.3 with the uvcvideo driver. Here is the output from messages when I attach the camera: Dec 23 10:09:46 laptop kernel: usb 5-2: new high speed USB device using ehci_hcd and address 3 Dec 23 10:09:46 laptop kernel: usb 5-2: configuration #1 chosen from 1 choice Dec 23 10:09:46 laptop kernel: usb 5-2: New USB device found, idVendor=046d, idProduct=0990 Dec 23 10:09:46 laptop kernel: usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 Dec 23 10:09:46 laptop kernel: usb 5-2: SerialNumber: 21334CEB Dec 23 10:09:46 laptop kernel: Linux video capture interface: v2.00 Dec 23 10:09:46 laptop kernel: uvcvideo: Found UVC 1.00 device <unnamed> (046d:0990) Dec 23 10:09:46 laptop kernel: input: UVC Camera (046d:0990) as /devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2:1.0/input/input9 Dec 23 10:09:46 laptop kernel: usbcore: registered new interface driver snd-usb-audio Dec 23 10:09:46 laptop kernel: usbcore: registered new interface driver uvcvideo Dec 23 10:09:46 laptop kernel: USB Video Class driver (v0.1.0) Dec 23 10:09:47 laptop pulseaudio[3172]: alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 16000 Hz. Dec 23 10:09:47 laptop pulseaudio[3172]: alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1. Dec 23 10:09:47 laptop kernel: ALSA sound/usb/usbmixer.c:803: cannot get current value for control 1 master ch: err = -22 Dec 23 10:09:47 laptop pulseaudio[3172]: alsa-util.c: Unable to load mixer: Invalid argument These lines come out when I go into the Kopete configuration screen: Dec 23 10:10:19 laptop kernel: uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -32 (exp. 26). Dec 23 10:10:19 laptop kernel: uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -75 (exp. 26). Dec 23 10:10:20 laptop kernel: uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26). Dec 23 10:10:21 laptop kernel: uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26). Loaded modules: laptop:/var/log # lsmod | grep uvc uvcvideo 50732 2 compat_ioctl32 1104 1 uvcvideo videodev 31236 3 uvcvideo v4l1_compat 13096 2 uvcvideo,videodev usbcore 167276 8 uvcvideo,snd_usb_audio,snd_usb_lib,hci_usb,btusb,ehci_hcd,uhci_hcd I understand this may be a duplicate of other reports, but I didn't see reports with the same hardware. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 450883] New: drbdadm create-md $resource *crashes*
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=450883 Summary: drbdadm create-md $resource *crashes* Product: openSUSE 11.1 Version: RC 1 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- In order to prepare a disk for use by drbd, one must issue a command, 'drbdadm create-md $resource' where $resource is the name of the resource you wish to refer to from /etc/drbd.conf. On openSUSE 11.1 (RC1) this crashes: frank:~ # drbdadm create-md backup *** stack smashing detected ***: drbdmeta terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x48)[0xb7f74da8] /lib/libc.so.6(__fortify_fail+0x0)[0xb7f74d60] drbdmeta[0x8049f65] drbdmeta[0x804a302] /lib/libc.so.6(__libc_start_main+0xe5)[0xb7ea4705] drbdmeta[0x80492e1] ======= Memory map: ======== 08048000-08057000 r-xp 00000000 08:02 245563 /sbin/drbdmeta 08057000-08058000 r--p 0000e000 08:02 245563 /sbin/drbdmeta 08058000-08059000 rw-p 0000f000 08:02 245563 /sbin/drbdmeta 08059000-0807a000 rw-p 08059000 00:00 0 [heap] b7e5c000-b7e69000 r-xp 00000000 08:02 859335 /lib/libgcc_s.so.1 b7e69000-b7e6a000 r--p 0000c000 08:02 859335 /lib/libgcc_s.so.1 b7e6a000-b7e6b000 rw-p 0000d000 08:02 859335 /lib/libgcc_s.so.1 b7e6b000-b7e8e000 rw-p b7e6b000 00:00 0 b7e8e000-b7fe3000 r-xp 00000000 08:02 858493 /lib/libc-2.9.so b7fe3000-b7fe4000 ---p 00155000 08:02 858493 /lib/libc-2.9.so b7fe4000-b7fe6000 r--p 00155000 08:02 858493 /lib/libc-2.9.so b7fe6000-b7fe7000 rw-p 00157000 08:02 858493 /lib/libc-2.9.so b7fe7000-b7feb000 rw-p b7fe7000 00:00 0 b7ffd000-b801b000 r-xp 00000000 08:02 859577 /lib/ld-2.9.so b801b000-b801c000 r--p 0001d000 08:02 859577 /lib/ld-2.9.so b801c000-b801d000 rw-p 0001e000 08:02 859577 /lib/ld-2.9.so bfe08000-bfe1d000 rw-p bffeb000 00:00 0 [stack] ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] *** stack smashing detected ***: drbdmeta terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x48)[0xb7ef3da8] /lib/libc.so.6(__fortify_fail+0x0)[0xb7ef3d60] drbdmeta[0x8049f65] drbdmeta[0x804a302] /lib/libc.so.6(__libc_start_main+0xe5)[0xb7e23705] drbdmeta[0x80492e1] ======= Memory map: ======== 08048000-08057000 r-xp 00000000 08:02 245563 /sbin/drbdmeta 08057000-08058000 r--p 0000e000 08:02 245563 /sbin/drbdmeta 08058000-08059000 rw-p 0000f000 08:02 245563 /sbin/drbdmeta 08059000-0807a000 rw-p 08059000 00:00 0 [heap] b7ddb000-b7de8000 r-xp 00000000 08:02 859335 /lib/libgcc_s.so.1 b7de8000-b7de9000 r--p 0000c000 08:02 859335 /lib/libgcc_s.so.1 b7de9000-b7dea000 rw-p 0000d000 08:02 859335 /lib/libgcc_s.so.1 b7dea000-b7e0d000 rw-p b7dea000 00:00 0 b7e0d000-b7f62000 r-xp 00000000 08:02 858493 /lib/libc-2.9.so b7f62000-b7f63000 ---p 00155000 08:02 858493 /lib/libc-2.9.so b7f63000-b7f65000 r--p 00155000 08:02 858493 /lib/libc-2.9.so b7f65000-b7f66000 rw-p 00157000 08:02 858493 /lib/libc-2.9.so b7f66000-b7f6a000 rw-p b7f66000 00:00 0 b7f7c000-b7f9a000 r-xp 00000000 08:02 859577 /lib/ld-2.9.so b7f9a000-b7f9b000 r--p 0001d000 08:02 859577 /lib/ld-2.9.so b7f9b000-b7f9c000 rw-p 0001e000 08:02 859577 /lib/ld-2.9.so bfc86000-bfc9b000 rw-p bffeb000 00:00 0 [stack] ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] frank:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 23

[Bug 458866] New: kdvelop hangs on libtool
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=458866 Summary: kdvelop hangs on libtool Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: rob.bob.301(a)hotmail.com QAContact: qa(a)suse.de Found By: Community User Observed in openSUSE 11.1 RC1 64-bit. Processor: AMD Athlon single core. 4GB RAM. To reproduce: 1. Create the simplest C++ project (auto-generated) 2. Click build project. 3. The process hangs on libtool 4. Then, it seems to be generating endless error report. Note: libtool was added using a separate installation step via Yast -> Software -> software management -> search "libtool" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 304149] New: openct package broken in suse 10.1
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=304149 Summary: openct package broken in suse 10.1 Product: SUSE Linux 10.1 Version: Final Platform: 32bit OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: aj(a)dungeon.inka.de QAContact: qa(a)suse.de Found By: Community of Practice Hi, I'm the upstream maintainer of openct. I had a look at recent openct packages from suse and I'm pretty sure they are not working correctly. the hald addon uses /proc/bus/usb which does not exist in suse I'm told, it should instead use /dev/bus/usb. also the fdi map does not match smart card readers via usb interface class 0b. please use both the fdi map and hald-addon script from new openct 0.6.13 and update to 0.6.13 and you should be fine. also at least on ubuntu I had to install the hald-addon in /usr/bin, not /usr/sbin. please check the right location will be used for opensuse. thanks, Andreas -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 20

[Bug 465719] New: PowerPC targets are missing in qemu-0.9.2svn20081008
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=465719 Summary: PowerPC targets are missing in qemu-0.9.2svn20081008 Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: SchwartzkopffD(a)Alte-Leipziger.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 There are no qemu-ppc, qemu-ppc64, qemu-ppc64abi32, qemu-system-ppc qemu-system-ppc64 and qemu-system-ppcemb in qemu-0.9.2svn20081008. qemu-0.9.1 (openSUSE 11.0) contains this files. (qemu-system-z80 is also missing, but I don't need this one) Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 461273] New: Yast2 does not detect Canon IP4500 Printer properly
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=461273 Summary: Yast2 does not detect Canon IP4500 Printer properly Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)gmail.com QAContact: jsrain(a)novell.com Found By: Beta-Customer When attaching a Canon IP4500 Printer to a Notebook with freshly installed openSUSE 11.1 (from DVD) the printer is detected as "canonip4500series" and no driver offered. (Attachment 1) Only changing the "Assign Driver" input field to "Canon Pixma iP4500" will offer the drivers to choose from in "select a driver" (Attachment 2) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 462048] New: Autodetected USB printer fails after first printjob
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=462048 User egrimminck(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462048#c1 Summary: Autodetected USB printer fails after first printjob Product: openSUSE 11.1 Version: Final Platform: HP OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: egrimminck(a)novell.com QAContact: jsmeix(a)novell.com Found By: Customer Created an attachment (id=262301) --> (https://bugzilla.novell.com/attachment.cgi?id=262301) combined hp-check.log and cups-autodetect.log When connecting the Printer (USB) for the first time the following messages is displayed in the /var/log/messages: Dec 23 19:56:02 suse01 kernel: usb 6-2: new full speed USB device using uhci_hcd and address 21 Dec 23 19:56:02 suse01 kernel: usb 6-2: configuration #1 chosen from 1 choice Dec 23 19:56:02 suse01 kernel: usblp0: USB Bidirectional printer dev 21 if 0 alt 0 proto 2 vid 0x03F0 pid 0xB402 Dec 23 19:56:02 suse01 kernel: scsi14 : SCSI emulation for USB Mass Storage devices Dec 23 19:56:02 suse01 kernel: usb 6-2: New USB device found, idVendor=03f0, idProduct=b402 Dec 23 19:56:02 suse01 kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 23 19:56:02 suse01 kernel: usb 6-2: Product: photosmart 7700 series Dec 23 19:56:02 suse01 kernel: usb 6-2: Manufacturer: hp Dec 23 19:56:02 suse01 kernel: usb 6-2: SerialNumber: MY4CH2K160U0 Dec 23 19:56:02 suse01 kernel: usb-storage: device found at 21 Dec 23 19:56:02 suse01 kernel: usb-storage: waiting for device to settle before scanning Dec 23 19:56:03 suse01 kernel: ppdev0: registered pardevice Dec 23 19:56:03 suse01 hp: io/hpmud/pp.c 627: unable to read device-id ret=-1 Dec 23 19:56:03 suse01 kernel: ppdev0: unregistered pardevice Dec 23 19:56:03 suse01 kernel: scsi 14:0:0:0: Direct-Access HP photosmart 7700 1.00 PQ: 0 ANSI: 2 Dec 23 19:56:03 suse01 kernel: sd 14:0:0:0: [sdc] Attached SCSI removable disk Dec 23 19:56:03 suse01 kernel: sd 14:0:0:0: Attached scsi generic sg4 type 0 Dec 23 19:56:03 suse01 kernel: usb-storage: device scan complete After that the first test-page prints without a problem: Dec 23 19:57:13 suse01 kernel: usblp0: removed Dec 23 19:57:14 suse01 hpijs: WARNING: color pen has low ink Dec 23 19:57:14 suse01 hpijs: STATE: marker-supply-low-warning However when I try to print a second page nothing is printed, the printer doesn't respond anymore and the following messages are displayed: Dec 23 19:58:59 suse01 hpijs: WARNING: color pen has low ink Dec 23 19:58:59 suse01 hpijs: STATE: marker-supply-low-warning Dec 23 19:59:31 suse01 kernel: usb 6-2: reset full speed USB device using uhci_hcd and address 21 Dec 23 19:59:44 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 1335: unable to write data hp:/usb/photosmart_7700_series?serial=MY4CH2K160U0: 45 second io timeout Dec 23 19:59:46 suse01 kernel: usb 6-2: device descriptor read/64, error -110 Dec 23 20:00:01 suse01 kernel: usb 6-2: device descriptor read/64, error -110 Dec 23 20:00:01 suse01 kernel: usb 6-2: reset full speed USB device using uhci_hcd and address 21 Dec 23 20:00:32 suse01 kernel: usb 6-2: device descriptor read/64, error -110 Dec 23 20:00:32 suse01 kernel: usb 6-2: reset full speed USB device using uhci_hcd and address 21 Dec 23 20:00:37 suse01 kernel: usb 6-2: device descriptor read/8, error -110 Dec 23 20:00:42 suse01 kernel: usb 6-2: device descriptor read/8, error -110 Dec 23 20:00:42 suse01 kernel: usb 6-2: reset full speed USB device using uhci_hcd and address 21 Dec 23 20:00:47 suse01 kernel: usb 6-2: device descriptor read/8, error -110 Dec 23 20:00:52 suse01 kernel: usb 6-2: device descriptor read/8, error -110 Dec 23 20:00:52 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 679: invalid deviceid wIndex=0, retrying wIndex=0: No such device Dec 23 20:00:52 suse01 kernel: usb 6-2: USB disconnect, address 21 Dec 23 20:00:52 suse01 kernel: sd 14:0:0:0: Device offlined - not ready after error recovery Dec 23 20:00:52 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 688: invalid deviceid retry ret=-19: No such device Dec 23 20:00:52 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 731: invalid device_status: No such device Dec 23 20:00:52 suse01 photosmart_7700_series?serial=MY4CH2K160U0: prnt/backend/hp.c 594: ERROR: 1015 other; will retry in 30 seconds... Dec 23 20:00:52 suse01 kernel: usb 6-2: new full speed USB device using uhci_hcd and address 22 Dec 23 20:00:53 suse01 kernel: usb 6-2: device descriptor read/64, error -71 Dec 23 20:00:53 suse01 kernel: usb 6-2: device descriptor read/64, error -71 Dec 23 20:00:53 suse01 kernel: usb 6-2: new full speed USB device using uhci_hcd and address 23 Dec 23 20:00:53 suse01 kernel: usb 6-2: device descriptor read/64, error -71 Dec 23 20:00:53 suse01 kernel: usb 6-2: device descriptor read/64, error -71 Dec 23 20:00:54 suse01 kernel: usb 6-2: new full speed USB device using uhci_hcd and address 24 Dec 23 20:00:54 suse01 kernel: usb 6-2: device not accepting address 24, error -71 Dec 23 20:00:54 suse01 kernel: usb 6-2: new full speed USB device using uhci_hcd and address 25 Dec 23 20:00:54 suse01 kernel: usb 6-2: device not accepting address 25, error -71 Dec 23 20:00:54 suse01 kernel: hub 6-0:1.0: unable to enumerate USB device on port 2 Dec 23 20:01:22 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 679: invalid deviceid wIndex=0, retrying wIndex=0: No such device Dec 23 20:01:22 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 688: invalid deviceid retry ret=-19: No such device Dec 23 20:01:22 suse01 photosmart_7700_series?serial=MY4CH2K160U0: io/hpmud/musb.c 731: invalid device_status: No such device Dec 23 20:01:22 suse01 photosmart_7700_series?serial=MY4CH2K160U0: prnt/backend/hp.c 594: ERROR: 1015 other; will retry in 30 seconds... Attached the cups-autoconfig.log file and a hp-check.log file combined in one file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 29

[Bug 464295] New: fuser command cannot operate on root directory "/"
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=464295 Summary: fuser command cannot operate on root directory "/" Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mike(a)m-buchau.de QAContact: qa(a)suse.de Found By: --- Running the command "fuser -uvm /" gives you the error output Cannot stat : No such file or directory Cannot stat : No such file or directory Cannot stat : No such file or directory without any meaningful results. The culprit is psmisc-22.6-nfs4fuser.patch in the psmisc package which adds code to strip trailing slashes from the argument path names: if (this_name->filename[len-1] == '/') this_name->filename[len-1] = '\0'; Unfortunately, there is no check for a "/" argument, resulting in "/" being mangled to an empty string. A stat("", ...) system call produces the error messages above. You can use "fuser -uvm //" as a workaround, but fuser is also run by the system's boot.localfs script to kill processes with write access to the root filesystem. Currently, these processes are not killed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 471311] New: Boot hangs, udev hangs on boot
by bugzilla_noreply＠novell.com 24 Mar '09

24 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=471311 Summary: Boot hangs, udev hangs on boot Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ap21193(a)yahoo.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=269093) --> (https://bugzilla.novell.com/attachment.cgi?id=269093) /var/log/messages /var/log/boot.msg lspci and hwconf from yast User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.0.4) Gecko/2008111710 Firefox/3.0.4 My system has worked well with opensuse 9.3 and 10.2. After a successfully installation of 11.1 ( repeated successfully about three times to be sure ) the boot from disk always hangs at: After the udevadm settle timeout, the events queue contains: 137: /devices/pnp0/00:05/ppdev/partport0 55: /devices/pnp0/00:05 Failed Unfortunately when the boot hangs /var/log/messages and /var/log/boot.msg contain nothing Two times I was able to boot setting "debug" in /etc/udev/udev.conf ( boot log and messages in attachment ) I can boot always if I add --debugtrace to udevd in boot.udev ( also in this case I attach boot log and messages ) In these cases I still see the message "udevadm settle timeout" and the boot stops a while when trying to load firmware requested but the system boots. I put correctly the requested firmware files in /lib/firmware ( as I made for opensuse 10.2 ) and in /lib/firmware/2.6.27.7-9-pae In the log I can see messages about problems in firmware loading "udev firmware loader misses sysfs". My HW conf: Asus A8V deluxe 939 Athlon 3200+ Dvd LG GSA-4163B HD Hitachi hds722512vlat20 GeForce FX 5200 Avermedia BT878 WinTV PVR 150 Wireless adapter D-link DWL G520+ Reproducible: Always Steps to Reproduce: 1.Boot the system 2. 3. Actual Results: Standard boot after installation hangs every time. If I set "debug" in /etc/udev/udev.conf the system booted two time ( out of ten ) If I add --debugtrace to udevd startup in boot.udev the system boot always ( but with errors, see the logs in attachment ) Expected Results: Boot correctly I puit in attachment the logs and the configurations made when the system booted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 17