December 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 450330] New: kernel: BUG: scheduling while atomic: usb-storage/3455/ 0x10000100
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=450330 Summary: kernel: BUG: scheduling while atomic: usb- storage/3455/0x10000100 Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: --- Created an attachment (id=256808) --> (https://bugzilla.novell.com/attachment.cgi?id=256808) log section showing the crash I had a nice ;-) kernel crash today. My laptop did not respond to keyboard or mouse anymore, the only things that worked were ping responses and the SysRQ key to shutdown it without too much disc corrumption. Hardware: - Acer TravelMate 803 laptop - USB cardreader connected, but no card inserted While it crashed, a friend (tried to) copy about 1 GB of data to a samba share on my laptop. After a reboot, only 50 MB had reached my disk - maybe it crashed shortly after starting to copy the files. The details of the crash were fortunately logged in /v/l/m. I'm attaching the relevant section to this bugreport. -- 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 420480] New: KDE4.1: Hotkeys not working
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=420480 Summary: KDE4.1: Hotkeys not working Product: openSUSE 11.1 Version: Factory Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: one_way(a)online.de QAContact: qa(a)suse.de Found By: --- I've been using KDE since the pre-releases of 4.0. The problem described here has been present ever since, no matter whether KDE 4.0 or 4.1 is running on my "openSUSE Factory" machine. So I for the time being don't give version details... Problem: KDE4 global hotkeys are simply not working E.g. (using the KDE4 control center's component to set up hotkeys): Using "meta+some key" to launch an app -> does not work Using a "multimedia key" to do something -> does not work In both cases, however, setting up the hotkey in the control center works, the control center also recognizes the hotkey! Only when using the hotkey to spawn the defined action, nothing happens. On the same machine I'm using KDE3's amarok for listening to music. This Amarok1.4 in the KDE4 environment without any problem reacts to the multimedia keys of my keyboard - which all KDE4 apps are ignoring :(. -- 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 450172] New: GRUB setup fails in new openSUSE installation; Operating system not found.
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=450172 Summary: GRUB setup fails in new openSUSE installation; Operating system not found. Product: openSUSE 11.1 Version: RC 1 Platform: x86 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: martin.konopka(a)stuba.sk QAContact: jsrain(a)novell.com Found By: Community User my machine: a 32-bit notebook Fujitsu-Siemens AMILO Pro V3205 Partitions on my machine before installation: -a windows NTFS partition /dev/sda1 (with an ubuntu installation within it) -openSUSE 11.1 beta5 partitions: /dev/sda5 mounted to swap /dev/sda6 (ext3) mounted to / /dev/sda7 (ext3) mounted to /home Boot loader (GRUB) with openSUSE as default. Now what happened: As usually, I am trying to do a new installation of openSUSE on the openSUSE partition, now installing x86 RC1 from DVD and Addon Lang CD media. I (as always) opted to format the sda5 and sda6 partitions and to leave sda7 (with user's data) untouched. The only essential difference with my several previous successful openSUSE 11.1 beta X installations (on the same partition) was that now I have not configured network during the installation. Other difference is that now I have chosen KDE 3.5 (while previously, with beta5, it installed KDE 4.1 although I had opted 3.5; with beta4 I had KDE 4.1 intentionally). After successful installation of packages a Yast window opened with messages as follows: grub> setup --stage2=/boot/grub/stage2/ --force-lba (hd0,1) (hd0,5) Checking if "/boot/grub/e2fs_stage1" exists... yes Checking if "/boot/grub/e2fs_stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0,1)"... failed (this is not fatal) Running "embed /boot/grub/e2fs_stage1_5 (hd0,5)"... failed (this is not fatal) Running "Install --force-lba --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,1) /boot/grub/stage2 p /boot/grub/menu.lst"... failed Error 22: No such partition grub> quit I stress that I have successfully performed openSUSE 11.1 beta4 and beta5 using the identical partitions setup and options what to format and what to not format. After rebooting my notebook I can just read: Error No operating system Operating system not found [:-(] -- 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 450206] New: broken menu.lst after install
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=450206 Summary: broken menu.lst after install Product: openSUSE 11.1 Version: Beta 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gjn(a)gjn.priv.at QAContact: jsrain(a)novell.com Found By: --- I install a new RC1 and have a different menu.lst as shown, after install same section are missing ? All with ... root (hd0,x) configfile /boot/grub/menu.lst are mnissing ? I don't know why YasT2 make different sections ? -- 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 3

[Bug 450084] New: bootloader fails to create menu entry for 2nd linux
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=450084 Summary: bootloader fails to create menu entry for 2nd linux Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: jreidinger(a)novell.com ReportedBy: msvec(a)novell.com QAContact: jsrain(a)novell.com CC: juhliarik(a)novell.com Found By: --- I have two distros installed in parallel: /dev/sda5: LABEL="11.1RC1" SEC_TYPE="ext2" TYPE="ext3" /dev/sda6: LABEL="11.0" TYPE="ext3" However after installation of 11.1RC1 I don't have 11.0 in bootloader menu. -- 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 449829] New: no kernel-source for 2.6.27.7-8-default
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=449829 Summary: no kernel-source for 2.6.27.7-8-default Product: openSUSE 11.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fred.blaise(a)gmail.com QAContact: qa(a)suse.de Found By: --- No suck package available. -- 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 450344] New: Kernel-source doesn't match kernel-default
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=450344 Summary: Kernel-source doesn't match kernel-default Product: openSUSE 11.1 Version: RC 1 Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: guim2206(a)gmail.com QAContact: jsrain(a)novell.com Found By: Community User After doing a kernel update to 2.6.27.7-8.1, the kernel-source package is stuck at 2.6.27.7-4.1 and it's impossible to get the newer version. This prevent me from installing VBox guest additions (openSUSE is installed as guest in a virtual machine). -- 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 419889] New: Installation aborts prematurely (close to end)
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=419889 Summary: Installation aborts prematurely (close to end) Product: openSUSE 11.1 Version: Alpha 2 Platform: i686 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lee_matheson(a)hotmail.com QAContact: jsrain(a)novell.com Found By: Community User Installation of openSUSE-11.1 alpha2 aborts prematurely (after the first reboot, but before software repository setup) if during the partitioning setup one creates a mount point (for an extra internal ext3 partition) of: /home/username/data (ie one assigns an existing partition as a directory in ones /home/username directory). The openSUSE installer when creating the user account, does not like the presence of a mount point under /home/username/something when creating the nominal user login. This was observed with KDE-3.5 chosen on 11.1 alpha2 on a 32-bit PC. When this problem occurs, toward the end of the install, the installer, will send one to a KDM user login where one's initially chosen user name is not available, and one can only log in as root. Once logged in as root, the root user can go to YaST, where it is observed that the nominal user account was NOT created by the openSUSE installer. But then with YaST one can then easily create a proper user account for the nominal user, and then then log out as root, and log back in as the new user. This work around appears effective. Presumably one can then set up one's repositories manually. This installer bug also exists on openSUSE-11.0, although I did not write a bug report on 11.0 (I just discovered this on 11.0 also). This bug is more likely to happen to experienced users, who already have a Linux partition, and who wish to keep the existing Linux install, and decide to tell the openSUSE installer to mount their existing (say SuSE-10.3) / and /home as "/home/username/suse103slash" "/hme/username/suse103home". The installer will implement that mount, BUT that implementation does cause the installer to quit early (after properly installing sofware in / ). Because the work around is easy, and because this is likely to happen only to more experienced users, I selected a severity of MINOR. -- 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 3

[Bug 447782] New: Installer fails error -3023 setting partition label
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=447782 Summary: Installer fails error -3023 setting partition label Product: openSUSE 11.1 Version: Beta 4 Platform: Macintosh OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: osl2008(a)googlemail.com QAContact: jsrain(a)novell.com Found By: Beta-Customer 11.1 Beta 4 PPC installation (started using NET CD build 0133). Installer fails error -3023 setting partition label during "preparing disks" -- 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 447011] New: Copying /proc/vmcore failed with 'Bad address' in opensuse 11.1 Beta5
by bugzilla_noreply＠novell.com 01 Dec '08

01 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=447011 Summary: Copying /proc/vmcore failed with 'Bad address' in opensuse 11.1 Beta5 Product: openSUSE 11.1 Version: Beta 5 Platform: PowerPC-64 OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: bugproxy(a)us.ibm.com QAContact: ke(a)novell.com Found By: Third Party Developer/Partner Partner ID: LTC 49992 =Comment: #0================================================= Pavan Naregundi <pavan.naregundi(a)in.ibm.com> - Copying /proc/vmcore failed with following error on opensuse 11.1 beta5 bash-3.2# cp /proc/vmcore /root/vmcore cp: reading `/proc/vmcore': Bad address bash-3.2# ls -l /root/vmcore -r-------- 1 root root 7281311744 Nov 18 07:10 /root/vmcore bash-3.2# ls -l /proc/vmcore -r-------- 1 root root 7381978996 Nov 18 07:10 /proc/vmcore bash-3.2# linux-8b3h:~ # uname -a Linux linux-8b3h 2.6.27.5-2-ppc64 #1 SMP 2008-11-11 15:15:33 +0100 ppc64 ppc64 ppc64 GNU/Linux linux-8b3h:~ # Machine: P55A CPU type: power 5 =Comment: #1================================================= Sachin P. Sant <sachinp(a)in.ibm.com> - Bumping the severity to high as vmcore copy fails. =Comment: #2================================================= Sachin P. Sant <sachinp(a)in.ibm.com> - Pavan, please check with Linux on Power test team if they encountered same issue with SLES 11 Beta5 release ? =Comment: #3================================================= Pavan Naregundi <pavan.naregundi(a)in.ibm.com> - Tried with crashkernel=256M@32M, and copying vmcore succeeded without any errors. I used crashkernel=128M@16M as mentioned in http://en.opensuse.org/Kdump before to find the error in copying of /proc/vmcore. =Comment: #4================================================= Cijurajan Kollanoor <> - The wiki http://en.opensuse.org/Kdump says: Architecture Option i386 and x86-64 crashkernel=64M@16M IA64 crashkernel=256M (small systems) or crashkernel=512M (larger systems) ppc64 crashkernel=128M@16M Please update the crash kernel parameter for ppc64 as crashkernel=256M@32M -- 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