October 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 629929] New: autoyast fails to create working grub boot config for md soft raid
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=629929 http://bugzilla.novell.com/show_bug.cgi?id=629929#c0 Summary: autoyast fails to create working grub boot config for md soft raid Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: bw(a)inside-security.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=381923) --> (http://bugzilla.novell.com/attachment.cgi?id=381923) two xml parts (bootloader and partitioning) of autoyast control file User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 The relevant xml parts of the autoinstall control file (bootloader and partitioning) are attached. This works with previous openSUSE versions. Autoyast creates the partitions for the software raid and the md device correctly and is able to install, but when rebooting for second stage the kernel is not bootable because autoyast determined the wrong partition. The additionally installed custom kernel is configured as in the control file and is bootable (but not used for second stage). Editing the grub menu manually and booting leads to successful completion of the autoinstallation but the openSUSE and failsafe entries in grub.conf will still be wrong. The disk setup is: 2 swap partitions on sda1 and sdb1, md0 with raid1 on sda2 and sdb2. Result: Autoyast consistently configures grub to boot the default openSUSE kernel from (hd0,0) which leads grub to stop at "Error 17: Cannot mount selected partition" when looking for the kernel image. This bug may be related to #619837 Reproducible: Always Steps to Reproduce: 1. Use an autoyast control file with the attached xml parts included -- Configure bugmail: http://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 641967] New: System unbootable after kernel update
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

https://bugzilla.novell.com/show_bug.cgi?id=641967 https://bugzilla.novell.com/show_bug.cgi?id=641967#c0 Summary: System unbootable after kernel update Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: bg(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Blocker: --- Created an attachment (id=391596) --> (http://bugzilla.novell.com/attachment.cgi?id=391596) zypper log file after doing the latest kernel update with zypp, my system remained unbootable. The problems were: - /boot/grub/menu.lst was empty (0 byte) - initrd has not been rebuilt with the new kernel I had to do both manually from a rescue system. The setup is the following: /boot is on /dev/sda1 / is on /dev/sda11 attaching zypper.log of the latest update. -- 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 589040] New: zypper is waiting for a long time when probing non-reachable repository
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=589040 http://bugzilla.novell.com/show_bug.cgi?id=589040#c0 Summary: zypper is waiting for a long time when probing non-reachable repository Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: i386 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: s.assmann(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.8 Firefox/3.6 zypper is waiting for a long time when probing non-reachable repository. This can be confusing and annoying for the user. zypper should set a timeout if a repository not available otherwise something like the following happens: linux-xvs9:~ # ping packman.mirrors.skynet.be PING mirror004.isp.belgacom.be (195.238.1.7) 56(84) bytes of data. ^C --- mirror004.isp.belgacom.be ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms linux-xvs9:~ # time zypper up Loading repository data... Reading installed packages... Nothing to do. real 0m1.665s user 0m1.405s sys 0m0.181s linux-xvs9:~ # zypper ar http://packman.mirrors.skynet.be/pub/packman/suse/11.2/Packman.repo Adding repository 'Packman repository (openSUSE_11.2)' [done] Repository 'Packman repository (openSUSE_11.2)' successfully added Enabled: Yes Autorefresh: No URI: http://packman.mirrors.skynet.be/pub/packman/suse/11.2/ linux-xvs9:~ # time zypper up Retrieving: 11.2 [error] Error: Download interrupted at 30% Abort, retry, ignore? [a/r/i] (a): ^C OK OK! Exiting immediately... real 4m3.405s <---- :( user 0m0.398s sys 0m0.194s Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 558953] New: openOffice crashes on C-o when using scim
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=558953 http://bugzilla.novell.com/show_bug.cgi?id=558953#c0 Summary: openOffice crashes on C-o when using scim Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: bg(a)novell.com QAContact: cwei(a)novell.com Found By: Community User Blocker: --- When using scim for chinese input methods in KDE, OpenOffice.org crashes when pressing Ctrl-o while a document is open. When starting ooo on the command line, I get the follwoing message: Failed to create XIC Unfortunately, no core file is generated even with ulimit -c unlimited. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 568082] New: kde4 file dialogue hangs if one inserts an image
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=568082 http://bugzilla.novell.com/show_bug.cgi?id=568082#c0 Summary: kde4 file dialogue hangs if one inserts an image Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: sven.burmeister(a)gmx.net QAContact: cwei(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 At some point the kde4 file dialogue starts to hang before refreshing, i.e. it takes minutes until the content is shown and again minutes until e.g. switching from thumbnail on -> off or any scrolling in that dialogue. The process does not use any CPU while hanging. Maybe related. If one adds a new file to the folder one got an image from and opens the "add picture" file dialogue again the picture is not shown until one refreshes manually via F5. Reproducible: Always -- Configure bugmail: http://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 621447] New: grub writes vga=<something> in it's configuration, what is useless given KMS is active
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=621447 http://bugzilla.novell.com/show_bug.cgi?id=621447#c0 Summary: grub writes vga=<something> in it's configuration, what is useless given KMS is active Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: dieter.jurzitza(a)t-online.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.4) Gecko/20100513 SUSE/3.6.4-153.5 Firefox/3.6.4 The grub configuration keeps writing useless parameters (vga=<something>) into it's config file, as KMS ignores this parameter. Grub should switch to something like video=<something>, what both does not break KMS _and_ allows meaningful console resolutions to be set up. The current kernel KMS solution is only working if the edid values are correct. Blindly relying on edid makes no sense. Or, alternatively, ask edid for the screen size in addition. A 21' screen should not be configured for more than 1600x1200 points, this holds true for tube screens at least. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 11.3 with an vga-monitor 2. an useless entry vga=<something> for grub is generated 3. the console resolution is to large by far. Actual Results: The configuration does not work as the vga=something parameter is silently ignored. Expected Results: A working console resolution. This bug is a consequence of the bug 619803. Obviously there is (or used to be) an awareness that the console resolution ought to be configurable via grub. This does not work any more as it is done now. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 624993] New: final 11.0 update
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=624993 http://bugzilla.novell.com/show_bug.cgi?id=624993#c0 Summary: final 11.0 update Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: maintenance(a)opensuse.org ReportedBy: meissner(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- tracker bug for final 11.0 update -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 557158] New: YaST2 crashes in 2nd stage of kvm
by bugzilla_noreply＠novell.com 05 Oct '10

05 Oct '10

http://bugzilla.novell.com/show_bug.cgi?id=557158 http://bugzilla.novell.com/show_bug.cgi?id=557158#c0 Summary: YaST2 crashes in 2nd stage of kvm Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mt(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=328634) --> (http://bugzilla.novell.com/attachment.cgi?id=328634) yas2 logs after the crash and initial boot Whie opensuse-11.2 installation in kvm, yast2 crashed at the end of 2nd stage. qemu-kvm -m 512 -enable-kvm -vga std -boot d -cdrom /space/tmp/iso/openSUSE-11.2-NET-x86_64.iso -hda /space/kvm/opensuse112_1/hda.img -net nic,model=virtio,vlan=0,macaddr=86:AD:3D:08:37:10 -net tap,vlan=0,script=/space/kvm/opensuse112_1/qemu-ifup,downscript=/space/kvm/opensuse112_1/qemu-ifup The qemu-ifup script just adds the tap to the bridge. This bug differs from bug 537350 (virtualbox installation) -- there are no kernel Oopses. Manual execution of /usr/lib/YaST2/startup/YaST2.Second-Stage just after the initial boot worked fine. Logs are on the way... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 641481] New: OpenSUSE doesn't recognize Wireless USB adapter TP-Link LT-WN722N (Atheros chipset)
by bugzilla_noreply＠novell.com 04 Oct '10

04 Oct '10

https://bugzilla.novell.com/show_bug.cgi?id=641481 https://bugzilla.novell.com/show_bug.cgi?id=641481#c0 Summary: OpenSUSE doesn't recognize Wireless USB adapter TP-Link LT-WN722N (Atheros chipset) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: v.plessky(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729) OpenSUSE 11.3 doesn't recognize Wireless USB adapter TP-Link LT-WN722N (Atheros chipset) All updates via #zypper up have been applied. #lsusb -v Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 idVendor 0x0cf3 Atheros Communications, Inc. idProduct 0x9271 bcdDevice 1.08 iManufacturer 16 iProduct 32 iSerial 48 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 60 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Reproducible: Always Steps to Reproduce: 1. Insert TP-Link Wireless USB adapter 2. It's not recognized -- 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 6

[Bug 641928] New: 2.6560861 Kernel panic not syncing vfs:unable to mount root fs on unknown-block(0,0)
by bugzilla_noreply＠novell.com 04 Oct '10

04 Oct '10

https://bugzilla.novell.com/show_bug.cgi?id=641928 https://bugzilla.novell.com/show_bug.cgi?id=641928#c0 Summary: 2.6560861 Kernel panic not syncing vfs:unable to mount root fs on unknown-block(0,0) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: 32bit OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: pcryer(a)ix.netcom.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 I just upgraded to opensuse 11.3 from 11.2 the stock kernel that was installed from the dvd vmlinuz-2.6.34-12-default works fine when I did my first online update after upgrading there was a a kernel update to 2.6.34.7-0.3.1-default when the update was finished and i did a reboot the above msg '2.6560861 kernel panic not syncing VFS:unable to mount root fs on unknown-block(0,0)' came up. I reinstalled the stock kernel 2.6.34-12-default to get my system working again a little bit about my system I use a ASUS T2-p motherboard intel p4 cpu 3.20GHZ 2.0 gib memory filesystem Mount Megs Used Avail %Used fs Type /dev/sda5 / 20480.6 13268.1 7212.5 65% reiserfs /dev/sda1 /boot 68.3 58.4 9.2 87% ext2 devtmpfs /dev 1010.8 0.5 1010.4 0% devtmpfs tmpfs /dev/shm 1011.0 1.6 1009.4 0% tmpfs /dev/sda11 /home 83695.4 76937.5 6757.9 92% reiserfs /dev/sda9 /opt 3616.0 618.5 2997.5 17% reiserfs /dev/sda10 /tmp 20441.4 14849.0 5592.4 73% reiserfs /dev/sda6 /usr 20480.6 12993.8 7486.8 63% reiserfs /dev/sda8 /var 3584.6 1657.8 1926.8 46% reiserfs Reproducible: Always Steps to Reproduce: 1.reboot 2. 3. Actual Results: I just tried reebooting the same message comes up I have the online update with the same kernel update i do not want to install kernel 2.6.34.7-0.3.1 again is there anything else I can do also I checked my log files I could not find anything about the error is there a specfic log to look at -- 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