March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 449982] New: hwinfo --dsl does not list pppoe devices
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=449982 Summary: hwinfo --dsl does not list pppoe devices Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: snwint(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de CC: mzugec(a)novell.com Found By: Development I don't know whether this is a bug in hwinfo or in YaST. The YaST dsl module calls hwinfo --dsl but that doesn't scan for pppoe dsl devices (hwinfo --pppoe does that). So either YaST needs to additionally call hwinfo --pppoe or hwinfo --dsl needs to be changed to also scan for pppoe devices. -- 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 449825] New: xfce4-session crashes at login
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=449825 Summary: xfce4-session crashes at login Product: openSUSE 11.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- xfce4-session crashes at login. this already happend yesterday before updating from factory to RC1 now. it happened after some small xfce config changes including switching the splash screen to "balou" (see traceback below). after switching splash back to "mouse" xfce4-session does not crash anymore! BUT: this only happens to my work account! for a newly created account xfce4-session does not crash, even after simple setup changes including balou splash. how can I provide more data? for now I just avoid the nicebalou splash;) harald harald > rpm -qf /usr/bin/xfce4-session xfce4-session-4.4.3-2.6 gdb traceback shows 6 stacked calls to balou_fadeout() -- here is the top of the traceback (I'll attach the trace back) --- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< --- #0 0x00007f6d58ff3a95 in xfce_expand_variables () from /usr/lib64/libxfce4util.so.4 #1 0x000000000041208f in ?? () #2 0x0000000000412585 in ?? () #3 0x000000000040eef8 in ?? () #4 0x000000000040f1b8 in ?? () #5 0x000000000040be18 in ?? () #6 0x00007f6d59c06ce5 in _SmsProcessMessage () from /usr/lib64/libSM.so.6 #7 0x00007f6d597f27e2 in IceProcessMessages () from /usr/lib64/libICE.so.6 #8 0x0000000000409d00 in ?? () #9 0x00007f6d557bf0db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #10 0x00007f6d557c28ad in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x00007f6d557c2a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x00007f6d539338ac in balou_fadeout () from /usr/lib64/xfce4/splash/engines/libbalou.so #13 0x00007f6d53935fed in ?? () from /usr/lib64/xfce4/splash/engines/libbalou.so #14 0x000000000041174f in ?? () #15 0x0000000000412026 in ?? () #16 0x0000000000412585 in ?? () #17 0x000000000040eef8 in ?? () #18 0x000000000040f1b8 in ?? () #19 0x000000000040be18 in ?? () #20 0x00007f6d59c06ce5 in _SmsProcessMessage () from /usr/lib64/libSM.so.6 #21 0x00007f6d597f27e2 in IceProcessMessages () from /usr/lib64/libICE.so.6 #22 0x0000000000409d00 in ?? () #23 0x00007f6d557bf0db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #24 0x00007f6d557c28ad in ?? () from /usr/lib64/libglib-2.0.so.0 #25 0x00007f6d557c2a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #26 0x00007f6d539338ac in balou_fadeout () from /usr/lib64/xfce4/splash/engines/libbalou.so #27 0x00007f6d53935fed in ?? () from /usr/lib64/xfce4/splash/engines/libbalou.so #28 0x000000000041174f in ?? () #29 0x0000000000412026 in ?? () #30 0x0000000000412585 in ?? () #31 0x000000000040eef8 in ?? () #32 0x000000000040f1b8 in ?? () #33 0x000000000040be18 in ?? () #34 0x00007f6d59c06ce5 in _SmsProcessMessage () from /usr/lib64/libSM.so.6 #35 0x00007f6d597f27e2 in IceProcessMessages () from /usr/lib64/libICE.so.6 #36 0x0000000000409d00 in ?? () #37 0x00007f6d557bf0db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #38 0x00007f6d557c28ad in ?? () from /usr/lib64/libglib-2.0.so.0 #39 0x00007f6d557c2a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #40 0x00007f6d539338ac in balou_fadeout () from /usr/lib64/xfce4/splash/engines/libbalou.so [ ...] #102 0x00007f6d557bf0db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #103 0x00007f6d557c28ad in ?? () from /usr/lib64/libglib-2.0.so.0 #104 0x00007f6d557c2ddd in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #105 0x00007f6d5932a227 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 #106 0x000000000040a0d8 in ?? () #107 0x00007f6d5520c586 in __libc_start_main () from /lib64/libc.so.6 #108 0x00000000004096b9 in ?? () #109 0x00007fff626873d8 in ?? () #110 0x000000000000001c in ?? () #111 0x0000000000000001 in ?? () #112 0x00007fff626891e0 in ?? () #113 0x0000000000000000 in ?? () (gdb) q --- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< --- -- 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 479737] New: Request for clarification: Always openSUSE or OpenSUSE at the beginning of a sentence?
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=479737 Summary: Request for clarification: Always openSUSE or OpenSUSE at the beginning of a sentence? Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: trans(a)michael-skiba.de QAContact: ke(a)novell.com Found By: --- User-Agent: Opera/9.63 (X11; Linux i686; U; en) Presto/2.1.1 Not sure if it's a bug or not, but in the add-on-creator.xx.po we've a string that is called "OpenSUSE", this makes me wonder since I heard someone complaining about the misstyping of openSUSE the other day. I think since openSUSE is a name it should always be written in that particular way, regardless if it's at the beginning of a sentencen/list/quote or not. Is that correct(would make this string a bug) or not? Regards 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 5

[Bug 481495] New: linux kernel-default-2.6.27.19-3.2.1 crashes
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481495 User dobromir(a)chello.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=481495#c4 Summary: linux kernel-default-2.6.27.19-3.2.1 crashes Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dobromir(a)chello.pl QAContact: qa(a)suse.de Found By: --- Created an attachment (id=276735) --> (https://bugzilla.novell.com/attachment.cgi?id=276735) photo of the crash information from the kernel (from phone) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 linux kernel from package kernel-default-2.6.27.19-3.2.1 crashes often. On vanilla instalation everything works great. Reproducible: Always Steps to Reproduce: 1. start in single mode 2. run fsck on ext3 part 3. wait for crash Actual Results: I firs saw it few times working on KDE environment (about 1-2hours each time), so i thought that this is a hardware or nvidia driver bug. But this is not the case. After few crashes i started in single mode and started fsck. The crash also appeared. So removed nvidia driver (kernel is not tainted), and do the same procedure again. Three other probes also crashed my computer. Expected Results: kernel crash (see attachment) lenvo y530 notebook cpuinfo: vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz stepping : 6 cpu MHz : 800.000 cache size : 3072 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm bogomips : 4533.45 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: lspci: 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation GeForce 9600M GS (rev a1) 02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02) 03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection 07:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 07:03.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 07:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 07:03.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) -- 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 449083] New: No screen with Ati Radeon Xpress 1150 integrated graphig chipset
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=449083 Summary: No screen with Ati Radeon Xpress 1150 integrated graphig chipset Product: openSUSE 11.1 Version: Beta 5 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: sndirsch(a)novell.com ReportedBy: matti.kukkola(a)gmail.com QAContact: sax2-maintainer-bugs(a)forge.provo.novell.com Found By: Beta-Customer Created an attachment (id=255594) --> (https://bugzilla.novell.com/attachment.cgi?id=255594) My xorg.conf I installed KDE desktop and instalation went good until I have to had run Desktop. I got only black screen and some out of area message from display. I had problems with my laptop display, too. My Desktop computer is Fujitsu Siemens Scaleo J and motherboard is Asus M2R-FVM. I had these problems with openSUSE 10.3 and Desktop computer, too. You can find old reports some here. It was fixed and now problem is back. Regard Matti -- 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 37

[Bug 478465] New: kde4-k3b lacks option to create CD/DVD from ISO file
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=478465 Summary: kde4-k3b lacks option to create CD/DVD from ISO file Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: u.buckesfeld(a)gmx.de QAContact: qa(a)suse.de Found By: Community User K3b Version 1.60.0 Using KDE 4.2.00 (KDE 4.2.0) "release 102" Looks like there's no way to create a CD or DVD from an ISO. -- 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 482324] New: Useless "Create test case" link
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=482324 Summary: Useless "Create test case" link Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: bugzilla AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Bugzilla contains a link "Create test case" in the bug attributes section of show_bug.cgi (at the top of the right box, above the "Created: <date> by <reporter>" paragraph. This link (to tr_new_case.cgi) is useless for external bugreporters - the only thing I get is a page to enter a code to validate my mail address. I guess the reason is that tr_new_case.cgi is restricted to "novellonly" - if I'm right, please hide the "Create test case" link for non-novell people. -- 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 467014] New: encrypted partition: no padlock found
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=467014 Summary: encrypted partition: no padlock found Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- encrypted partition: no padlock found Two similar computers, almost identical configurations. On both -- encrypted partitions. On 64-bit -- no error message about padlocks. On 32-bit -- just after entering password (while booting), there is an error. I just really hope this partition is correctly encrypted, because while installing there was no info about errors or correctness. The errors from /var/log/boot.msg modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.27.7-9-pae/kernel/drivers/crypto/padlock-aes.ko): No such device modprobe: WARNING: Error inserting padlock_sha (/lib/modules/2.6.27.7-9-pae/kernel/drivers/crypto/padlock-sha.ko): No such device -- 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 482316] New: /etc/init.d/kbd mounts /proc/bus/usb and loads wrong hci/hcd modules
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=482316 User cstender(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482316#c46113 Summary: /etc/init.d/kbd mounts /proc/bus/usb and loads wrong hci/hcd modules Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: cstender(a)novell.com QAContact: qa(a)suse.de CC: seife(a)novell.com Found By: Development VirtualBox is unable to catch usb devices if I use a crypto home. After debugging I found out that the following code in /etc/init.d/kbd gets executed when you're using a crypto home: # # load usb drivers in runlevel S # case "${PREVLEVEL}${RUNLEVEL}" in N1|NS) test -f /proc/cpuinfo || mount -n -t proc proc /proc 2>/dev/null # [bugzilla #46113] # we come here although heading for runlevel 5. # I'll comment out diabling hotplug for now. jw. # test -f /proc/sys/kernel/hotplug && echo /bin/true > /proc/sys/kernel/hotplug 2>/dev/null test -d /proc/bus/usb || modprobe usbcore >/dev/null 2>&1 mount -n -t usbfs usbfs /proc/bus/usb >/dev/null 2>&1 for mod in ehci-hcd ohci-hcd uhci-hcd usb-ohci usb-uhci ; do echo -n $mod" " modprobe $mod >/dev/null 2>&1 done # [bugzilla #284348] # sleep is no longer needed. horay! # # echo # echo "wait 3 seconds for USB initialisation ..." # sleep 3 for mod in usbhid input hid keybdev ; do modprobe $mod >/dev/null 2>&1 done ;; esac AFAIK mounting /proc/bus/usb is deprecated and should be removed. Furthermore the module names *-hci and *-hcd have changed to *_hci and *_hcd. I'm not sure we need this at all because udev loads all of these modules before /etc/init.d/kbd gets executed. -- 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 481195] New: vnc install option leaves vnc open after install without password
by bugzilla_noreply＠novell.com 05 Mar '09

05 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481195 Summary: vnc install option leaves vnc open after install without password Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: jjohnson(a)vbi.vt.edu QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 Setting option in install: vnc=1 and then supplying a password works fine. What is troublesome is that once the install is complete, VNC is still listening but no longer requires a password to open a session. Reproducible: Always Steps to Reproduce: 1. Boot from preferred installation environment 2. Add vnc=1 to 'Boot Options' 3. Install OS 4. After installation connect to machine via VNC or web browser without password Actual Results: Once installed using vnc=1 option, you are not required to enter a password to establish VNC connection Expected Results: At a minimum the password that was requested during install should be required -- 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 8