January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 352129] New: bootloader configuration should allow persistent options
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=352129 Summary: bootloader configuration should allow persistent options Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmuhamedagic(a)novell.com QAContact: jsrain(a)novell.com Found By: --- It is typical to share many kernel options (such as vga mode) between different kernels. Not an expert on grub, but it seems that it doesn't have such a feature. Debian has chosen to fit various options into comments of menu.lst. A sample: ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=noapic acpi=off root=/dev/mapper/bork-newroot ro ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true For example, my motherboard has a problem which wouldn't let it boot without the noapic option. The extra options make the kernel upgrade safe. -- 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 170662] root partition offered as boot partition
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=170662 User jplack(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=170662#c6 Joachim Plack <jplack(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jplack(a)novell.com | --- Comment #6 from Joachim Plack <jplack(a)novell.com> 2008-01-11 06:35:56 MST --- Bug can be either in proposal code _or_ in yast2-storage. The latter could report wrong partition layout, had those kinda bugs in the pasts My comment was meant to narrow down areas of investigation, not more. -- 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 0

[Bug 351899] New: GTK version YaST2 does not indicate status during loading components
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351899 Summary: GTK version YaST2 does not indicate status during loading components Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: de(a)lincomp.eu QAContact: jsrain(a)novell.com Found By: --- The current GTK Version of YaST does not indicate a status (e.g. mouse hourglass) while loading subcomponents. This may be confusing as some of the modules take a while to start up. Best Regards Marcus -- 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 159882] createrepo author information incorrect
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=159882 User ro(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=159882#c9 Ruediger Oertel <ro(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ro(a)novell.com |mls(a)novell.com Status|ASSIGNED |NEW --- Comment #9 from Ruediger Oertel <ro(a)novell.com> 2008-01-11 05:12:50 MST --- done for post 10.3 Micha: add the change to rpmpopt from comment # 5 -- 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 0

[Bug 352868] New: SuSEconfig and umask
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=352868 Summary: SuSEconfig and umask Product: openSUSE 11.0 Version: unspecified Platform: All OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: ro(a)novell.com ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: --- If a system uses a non default umask - in the particular case 027 set by /root/.profile - files from /etc/sysconfig/ are not world readable after an update. Last I've seen this after the update to aaa_base in 10.3. I suggest to inherit the permission from the permission set before any changes are applied to the file in question. -- 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 1

[Bug 349883] New: Opensuse 10.3 usb problem with ehci_hcd error -71
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=349883 User opensuse(a)online.ms added comment https://bugzilla.novell.com/show_bug.cgi?id=349883#c1 Summary: Opensuse 10.3 usb problem with ehci_hcd error -71 Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: opensuse(a)online.ms QAContact: qa(a)suse.de Found By: Other Hi, ehci works very unreliable in the following manner: with ehci_hcd it is very hard to print, printer hangs, printout is shifted or just a bunch of cryptic digits. This happens with both my usb printers (epson stylus color 740 and canon hl 1250) I see this kind of message if it happens with dmesg: <snip> bootsplash: status on console 0 changed to on drivers/usb/class/usblp.c: usblp0: nonzero read/write bulk status received: -71 usb 4-1: clear tt 1 (1041) error -71 hub 4-0:1.0: port 1 disabled by hub (EMI?), re-enabling... usb 4-1: USB disconnect, address 2 usb 4-1.1: USB disconnect, address 3 usb 4-1.1.1: USB disconnect, address 7 usb 4-1: clear tt 1 (8040) error -19 usb 4-1.2: USB disconnect, address 4 drivers/usb/class/usblp.c: usblp0: error -71 reading printer status usb 4-1.3: USB disconnect, address 5 usb 4-1.3.1: USB disconnect, address 8 usb 4-1.4: USB disconnect, address 6 drivers/usb/class/usblp.c: usblp0: removed usb 4-1: new high speed USB device using ehci_hcd and address 9 usb 4-1: new device found, idVendor=05e3, idProduct=0608 usb 4-1: new device strings: Mfr=0, Product=1, SerialNumber=0 usb 4-1: Product: USB2.0 Hub usb 4-1: configuration #1 chosen from 1 choice hub 4-1:1.0: USB hub found hub 4-1:1.0: 4 ports detected usb 4-1.1: new high speed USB device using ehci_hcd and address 10 usb 4-1.1: new device found, idVendor=05e3, idProduct=0608 usb 4-1.1: new device strings: Mfr=0, Product=1, SerialNumber=0 usb 4-1.1: Product: USB2.0 Hub usb 4-1.1: configuration #1 chosen from 1 choice hub 4-1.1:1.0: USB hub found hub 4-1.1:1.0: 4 ports detected usb 4-1.2: new full speed USB device using ehci_hcd and address 11 usb 4-1.2: new device found, idVendor=04f9, idProduct=0007 usb 4-1.2: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 4-1.2: configuration #1 chosen from 1 choice drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 11 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0007 usb 4-1.3: new high speed USB device using ehci_hcd and address 12 usb 4-1.3: new device found, idVendor=05e3, idProduct=0606 usb 4-1.3: new device strings: Mfr=0, Product=1, SerialNumber=0 usb 4-1.3: Product: USB2.0 Hub usb 4-1.3: configuration #1 chosen from 1 choice hub 4-1.3:1.0: USB hub found hub 4-1.3:1.0: 4 ports detected usb 4-1.4: new low speed USB device using ehci_hcd and address 13 usb 4-1.4: new device found, idVendor=046d, idProduct=c50e usb 4-1.4: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 4-1.4: Product: USB RECEIVER usb 4-1.4: Manufacturer: Logitech usb 4-1.4: configuration #1 chosen from 1 choice input: Logitech USB RECEIVER as /class/input/input8 input: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1d.7-1.4 usb 4-1.1.1: new low speed USB device using ehci_hcd and address 14 usb 4-1.1.1: new device found, idVendor=046a, idProduct=0001 usb 4-1.1.1: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 4-1.1.1: configuration #1 chosen from 1 choice input: HID 046a:0001 as /class/input/input9 input: USB HID v1.00 Keyboard [HID 046a:0001] on usb-0000:00:1d.7-1.1.1 usb 4-1.3.1: new full speed USB device using ehci_hcd and address 15 usb 4-1.3.1: new device found, idVendor=04a9, idProduct=2208 usb 4-1.3.1: new device strings: Mfr=64, Product=77, SerialNumber=0 usb 4-1.3.1: Product: CanoScan usb 4-1.3.1: Manufacturer: Canon usb 4-1.3.1: configuration #1 chosen from 1 choice lp: driver loaded but no devices found usb 4-1.2: USB disconnect, address 11 drivers/usb/class/usblp.c: usblp0: removed usb 4-1.2: new full speed USB device using ehci_hcd and address 16 usb 4-1.2: new device found, idVendor=04f9, idProduct=0007 usb 4-1.2: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 4-1.2: configuration #1 chosen from 1 choice drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0007 lsusb shows this; Bus 004 Device 024: ID 04f9:0007 Brother Industries, Ltd HL-1250 Laser Printer Bus 004 Device 023: ID 04a9:2208 Canon, Inc. CanoScan D660U Bus 004 Device 022: ID 046a:0001 Cherry GmbH My3000 Keyboard Bus 004 Device 021: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver Bus 004 Device 020: ID 05e3:0606 Genesys Logic, Inc. Bus 004 Device 018: ID 05e3:0608 Genesys Logic, Inc. Bus 004 Device 017: ID 05e3:0608 Genesys Logic, Inc. Bus 004 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 A workaround is to unload ehci_hcd, then everything works fine *exept*: 1. low transfer speed to my external hard disk 2. if I unplug my usb devices with ehci_hcd unloaded then they won't be recognized when plugged back in (i.e. there arent even any usb-messages in dmesg) 1. is OK as it is expected behavior for usb 1.0 uhci_hcd 2. Any suggestions for a better workaround resolving #2 (i.e. remove ehci_hcd without losing essential usb functionality) are welcome. 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 10

[Bug 308895] New: NetworkManager can't start Intel 3945 wifi on Dell D830
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=308895#c303834 Summary: NetworkManager can't start Intel 3945 wifi on Dell D830 Product: openSUSE 10.3 Version: Beta 3 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marcus(a)marleo.net QAContact: qa(a)suse.de Found By: --- KNetworkManager hangs at 57% when trying to start wireless networking. This doesn't seem to be related to bug #303834 because I've applied the patch to /usr/lib64/hal/scripts/linux/hal-system-killswitch-get-power-linux and it has had no effect (after reboot). (This bug was apparently fixed, but is still in 10.3 beta 3.) /var/log/NetworkManager: Sep 8 10:53:22 laptop NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported Sep 8 10:54:19 laptop syslog-ng[2710]: last message repeated 9 times lspci: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) -- 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 18

[Bug 308204] New: Wrong encoding/font in package description (pdb? autobuild? libzypp? yast2-qt? fonts?)
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=308204 Summary: Wrong encoding/font in package description (pdb? autobuild? libzypp? yast2-qt? fonts?) Product: openSUSE 10.3 Version: Beta 3 Platform: i686 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: sh(a)novell.com ReportedBy: kkaempf(a)novell.com QAContact: visnov(a)novell.com CC: ro(a)novell.com Found By: --- See attached screenshot, the authors name isn't displayed correctly during 1st stage installation. Either a bug in encoding conversion or a missing font ? -- 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 7

[Bug 351386] New: error in /etc/init.d/skeleton.compat
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351386 Summary: error in /etc/init.d/skeleton.compat Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ken(a)turnkey.com.au QAContact: qa(a)suse.de Found By: Customer At lines 159-162 there are 4 definitions of compatibility functions for init scripts on LSB and other non-SUSE systems. The returns in there are wrong. Errors like this happen on SUSE: line 162: return: /sbin/checkproc: numeric argument required In bash, "return" in a function takes a numeric argument, not the status of a command. To return the status of the command, as it's the last one, just omit the return, like this: start_daemon() { /sbin/start_daemon ${1+"$@"}; } killproc() { /sbin/killproc ${1+"$@"}; } pidofproc() { /sbin/pidofproc ${1+"$@"}; } checkproc() { /sbin/checkproc ${1+"$@"}; } It's a wonder nobody spotted this before, nobody must have attempted to use the template on SUSE since it was written, or at least not reported the problem. -- 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 350036] New: mkinitrd does not invoke splash screen
by bugzilla_noreply＠novell.com 11 Jan '08

11 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350036 Summary: mkinitrd does not invoke splash screen Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: j-engel(a)gmx.de QAContact: qa(a)suse.de Found By: --- Starting mkinitrd says Kernel image: /boot/vmlinuz-2.6.22.13-0.3-default Initrd image: /boot/initrd-2.6.22.13-0.3-default Root device: /dev/disk/by-id/scsi-SATA_Hitachi_HTS7210_MPCDN7Y4H12JGL-part6 (/dev/sda6) (mounted on / as ext3) Resume device: /dev/sda5 Device does not exist. Command failed Kernel Modules: processor thermal scsi_mod libata ata_piix fan jbd mbcache ext3 edd dm-mod dm-snapshot sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid dm-crypt Features: dm block usb luks resume.userspace resume.kernel Bootsplash: SuSE (1280x1024) /etc/bootsplash/themes/SuSE/images/silent-1280x1024.jpg: restart marker mismatch 33551 blocks -- 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