January 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 725980] New: refuses to power off
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=725980 https://bugzilla.novell.com/show_bug.cgi?id=725980#c0 Summary: refuses to power off Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Starting yesterday (21 Oct 2011 US/Central), shutting down my T61p Thinkpad results in a laptop that shuts off. For about 5 seconds. Then it powers back up again. All by itself! Can't stop it. Hold power button for 5 seconds. Shuts off. Then on again. Tap power button before booting. Shuts off. Then on again. Had to *remove the battery* to get it to stop booting. Also new, maybe relevant, maybe not: if I bring up the KDE shutdown dialog, the display is allll corrupted. 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 14

[Bug 712905] New: kde mixer doesn't retain volume between reboots
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=712905 https://bugzilla.novell.com/show_bug.cgi?id=712905#c0 Summary: kde mixer doesn't retain volume between reboots Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- At each boot, the volume is set all the way up, despite being reset before shutdown. -- 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 671349] New: Cannot enable wireless with networkmanager
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=671349 https://bugzilla.novell.com/show_bug.cgi?id=671349#c0 Summary: Cannot enable wireless with networkmanager Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: utgarda(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b10) Gecko/20110121 Firefox/4.0b10 Clicking the checkbox "enable wireless" in nm-applet does nothing, instantly it becomes unchecked again, the only effect is that I can see a "+ show more" button for a quick moment near the button "manage connections". Trying to enable wireless via nmcli is just about the same: no effect and no error messages, neither to terminal nor to /var/log/messages. Had this problem right after installing milestone 6, now updated to RC1, the problem stays. Reproducible: Always Steps to Reproduce: 1. Login and wait till nm-applet is there 2. Click on the icon "network settings", then toggle the checkbox "enable wireless" 3. Try to use networkmanager's console tools Actual Results: Nothing Expected Results: wireless networking enabled or, if impossible, some error message shown > lspci | grep Network 04:00.0 Network controller: Intel Corporation WiMAX/WiFi Link 5150 > nmcli nm wifi on > nmcli dev status DEVICE TYPE STATE eth0 802-3-ethernet connected wlan0 802-11-wireless unavailable wmx0 802-3-ethernet unavailable > sudo tail /var/log/messages .. Feb 11 13:00:42 linux-rpt7 NetworkManager[1558]: keyfile: updating /etc/NetworkManager/system-connections/Auto eth0 Feb 11 13:04:29 linux-rpt7 sudo: etsvigun : TTY=pts/1 ; PWD=/home/etsvigun ; USER=root ; COMMAND=/usr/bin/tail -f /var/log/messages Feb 11 13:04:50 linux-rpt7 sudo: etsvigun : TTY=pts/1 ; PWD=/home/etsvigun ; USER=root ; COMMAND=/usr/bin/tail /var/log/messages -- 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 27

[Bug 712188] New: control-c zypper during download: double free
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=712188 https://bugzilla.novell.com/show_bug.cgi?id=712188#c0 Summary: control-c zypper during download: double free Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other 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: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Retrieving: libqt4-x11-debuginfo-4.7.3-197.1.x86_64.rpm [error (344.2 KiB/s)] ^C OK OK! Exiting immediately... *** glibc detected *** zypper: double free or corruption (!prev): 0x0000000005293fc0 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x733b6)[0x7f45c37153b6] /lib64/libc.so.6(cfree+0x6c)[0x7f45c371a2dc] /usr/lib64/libcurl.so.4(+0x1d999)[0x7f45c2d01999] /usr/lib64/libzypp.so.810(_ZN4zypp5media9MediaCurl14disconnectFromEv+0x31)[0x7f45c49ba3b1] /usr/lib64/libzypp.so.810(_ZN4zypp5media12MediaHandler10disconnectEv+0x29)[0x7f45c4992459] /usr/lib64/libzypp.so.810(_ZN4zypp5media12MediaHandler7releaseERKSs+0x7a7)[0x7f45c49985a7] /usr/lib64/libzypp.so.810(_ZN4zypp5media11MediaAccess5closeEv+0x59)[0x7f45c498bb09] /usr/lib64/libzypp.so.810(_ZN4zypp5media11MediaAccessD1Ev+0x1b)[0x7f45c498be5b] /usr/lib64/libzypp.so.810(_ZN4zypp5media11MediaAccessD0Ev+0x9)[0x7f45c498bea9] /usr/lib64/libzypp.so.810(+0x1c9545)[0x7f45c49e9545] /usr/lib64/libzypp.so.810(_ZN5boost6detail17sp_counted_impl_pIN4zypp5media17MediaManager_ImplEE7disposeEv+0x8b)[0x7f45c49f489b] /usr/lib64/libzypp.so.810(_ZN4zypp10RW_pointerINS_5media17MediaManager_ImplENS_10rw_pointer6SharedIS2_EEED1Ev+0x49)[0x7f45c49f47b9] /lib64/libc.so.6(__cxa_finalize+0xa5)[0x7f45c36d7935] /usr/lib64/libzypp.so.810(+0x1274f6)[0x7f45c49474f6] ======= Memory map: ======== 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 9

[Bug 749733] New: systemd: booting into runlevel 1 means control-alt-delete no longer works
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=749733 https://bugzilla.novell.com/show_bug.cgi?id=749733#c0 Summary: systemd: booting into runlevel 1 means control-alt-delete no longer works Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 If you boot into runlevel 1 (by appending '1' to the grub boot), you'll get there, but control-alt-delete produces a message about starting bootsplash instead of rebooting. 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 8

[Bug 745642] New: actions policy: why is "The systemd Project" listed 5 times?
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=745642 https://bugzilla.novell.com/show_bug.cgi?id=745642#c0 Summary: actions policy: why is "The systemd Project" listed 5 times? Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Summary says it all: in the KDE control Actions Policy, why is "The systemd Project" listed 5 times? 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 742645] New: konsole fonts: try to change font (1st try) vs (2nd try) -- different results!
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=742645 https://bugzilla.novell.com/show_bug.cgi?id=742645#c0 Summary: konsole fonts: try to change font (1st try) vs (2nd try) -- different results! Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=472173) --> (http://bugzilla.novell.com/attachment.cgi?id=472173) screen capture of fonts dialog User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 I noticed a problem with konsole and fonts. Starting with *no* konsoles running, open a konsole. Choose from the Menu, "Settings", "Configure Current Profile", click the Appearance tab, and then click "Edit Font". You should see something like figure1. Choose *any* non-truetype font. Like "DEC Terminal". Cancel the dialog, and then choose "Edit Font" again. Now you'll see something like figure2 - notice that "DejaVu Sans Mono" got turned into "DejaVu Sans Mono [Misc]" and "DejaVu Sans Mono [Unknown]". The list of fonts is different. Liberation Mono disappeared. What gives? 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 4

[Bug 726471] New: libunicap2: bad udev rules
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=726471 https://bugzilla.novell.com/show_bug.cgi?id=726471#c0 Summary: libunicap2: bad udev rules Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other 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: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 libunicap2 supplies: /etc/udev/rules.d/50-euvccam.rules which causes some grumpage at startup: Oct 25 10:07:34 worklaptop udevd[11026]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:3 Oct 25 10:07:34 worklaptop udevd[11026]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:4 Oct 25 10:07:34 worklaptop udevd[11026]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:5 Oct 25 10:07:34 worklaptop udevd[11026]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:6 Oct 25 10:07:34 worklaptop udevd[11026]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:7 I suspect just changing 'SYSFS' to 'ATTRS' is probably sufficient. NOTE: found in 'Tumbleweed' and very probably also an issue for openSUSE 12.1 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 10

[Bug 725772] New: x11/evdev/nouveau crashes shortly after starting to watch a video
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=725772 https://bugzilla.novell.com/show_bug.cgi?id=725772#c0 Summary: x11/evdev/nouveau crashes shortly after starting to watch a video Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Happens every time. Start to watch a video. A few minutes later, the screen freezes. Control-Alt-Backspace does nothing. Can't switch to a VT. I use magic-sysrq keys to get this: Oct 20 21:27:16 frank kernel: [ 667.547014] runnable tasks: Oct 20 21:27:16 frank kernel: [ 667.547014] task PID tree-key switches prio exec-runtime sum-exec sum-sleep Oct 20 21:27:16 frank kernel: [ 667.547014] ---------------------------------------------------------------------------------------------------------- Oct 20 21:27:16 frank kernel: [ 667.547014] Oct 20 21:27:17 frank kernel: [ 668.000171] SysRq : Show Blocked State Oct 20 21:27:17 frank kernel: [ 668.000183] task PC stack pid father Oct 20 21:27:17 frank kernel: [ 668.000205] Xorg D 0000000000000000 0 1455 1365 0x00400004 Oct 20 21:27:17 frank kernel: [ 668.000209] 0000000000000008 ffff880132b4a000 0000000000018a2c 0000000000000000 Oct 20 21:27:17 frank kernel: [ 668.000213] 0000000000000b5b 0000000000000000 ffffc9000593e048 ffffffffffffff10 Oct 20 21:27:17 frank kernel: [ 668.000217] ffffffff812c3972 0000000000000010 0000000000000292 ffff880132b4bc38 Oct 20 21:27:17 frank kernel: [ 668.000220] Call Trace: Oct 20 21:27:17 frank kernel: [ 668.000228] Inexact backtrace: Oct 20 21:27:17 frank kernel: [ 668.000229] Oct 20 21:27:17 frank kernel: [ 668.000236] [<ffffffff812c3972>] ? ioread32+0x42/0x50 Oct 20 21:27:17 frank kernel: [ 668.000269] [<ffffffffa00ba49e>] ? nouveau_fence_update+0x10e/0x130 [nouveau] Oct 20 21:27:17 frank kernel: [ 668.000281] [<ffffffffa00ba87d>] ? __nouveau_fence_signalled+0x1d/0x30 [nouveau] Oct 20 21:27:17 frank kernel: [ 668.000292] [<ffffffffa00ba8db>] ? __nouveau_fence_wait+0x4b/0x100 [nouveau] Oct 20 21:27:17 frank kernel: [ 668.000301] [<ffffffffa0080c0a>] ? ttm_bo_wait+0xba/0x1c0 [ttm] Oct 20 21:27:17 frank kernel: [ 668.000312] [<ffffffffa00ba21e>] ? nouveau_bo_vma_del+0x8e/0xb0 [nouveau] Oct 20 21:27:17 frank kernel: [ 668.000324] [<ffffffffa00bbfd8>] ? nouveau_gem_object_close+0x88/0xa0 [nouveau] Oct 20 21:27:17 frank kernel: [ 668.000339] [<ffffffffa0046011>] ? drm_gem_handle_delete+0x81/0x110 [drm] Oct 20 21:27:17 frank kernel: [ 668.000348] [<ffffffffa00442bc>] ? drm_ioctl+0x39c/0x460 [drm] Oct 20 21:27:17 frank kernel: [ 668.000358] [<ffffffffa0046320>] ? drm_gem_destroy+0x50/0x50 [drm] Oct 20 21:27:17 frank kernel: [ 668.000364] [<ffffffff8100266c>] ? handle_signal+0xbc/0x190 Oct 20 21:27:17 frank kernel: [ 668.000367] [<ffffffff8140d86f>] ? input_event_to_user+0x4f/0x60 Oct 20 21:27:17 frank kernel: [ 668.000370] [<ffffffff81411003>] ? evdev_read+0x143/0x230 Oct 20 21:27:17 frank kernel: [ 668.000374] [<ffffffff8100bb74>] ? fpu_finit+0x14/0x30 Oct 20 21:27:17 frank kernel: [ 668.000377] [<ffffffff81164cd5>] ? do_vfs_ioctl+0x85/0x2e0 Oct 20 21:27:17 frank kernel: [ 668.000380] [<ffffffff81164fc8>] ? sys_ioctl+0x98/0xa0 Oct 20 21:27:17 frank kernel: [ 668.000384] [<ffffffff815a2212>] ? system_call_fastpath+0x16/0x1b System was 100% up-to-date as of 18:00 20 Oct 2011 US/Central. 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 9

[Bug 722084] New: kde4 network management: why need to unlock wallet *after* connecting to wireless network?
by bugzilla_noreply＠novell.com 24 Jan '13

24 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=722084 https://bugzilla.novell.com/show_bug.cgi?id=722084#c0 Summary: kde4 network management: why need to unlock wallet *after* connecting to wireless network? Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 Why does the KDE4 network management stuff need to unlock the wallet *after* connecting to a wireless network? 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