July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 805391] New: HP printer drivers may cause system instability
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=805391 https://bugzilla.novell.com/show_bug.cgi?id=805391#c0 Summary: HP printer drivers may cause system instability Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)suse.com ReportedBy: dfreeman(a)ieee.org QAContact: jsmeix(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 My system has been really unstable for a while now. It freezes for many seconds, with the mouse pointer stuck. Sometimes it will recover, but not always. I often lose my work because of this. Now today, for the first time, I have a hint at what may be wrong. After it got stuck, I received this broadcast to my system tray and my open consoles: Message from syslogd@xxx at Feb 23 15:58:24 ... kernel:[148830.733366] BUG: soft lockup - CPU#1 stuck for 38s! [python:6027] I then ran ps aux to see which process this is: user 6027 0.0 0.1 167892 4244 ? S Feb21 0:21 python /usr/bin/hp-systray I don't think it's a coincidence that this is associated with the HP proprietary drivers. I'm using hplip version 3.12.11-62.1-x86-64 from repository build.opensuse.org/Printing Reproducible: Sometimes 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 6

[Bug 812600] New: openSUSE:12.3/choqok: Bug
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=812600 https://bugzilla.novell.com/show_bug.cgi?id=812600#c0 Summary: openSUSE:12.3/choqok: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: kde-maintainers(a)suse.de ReportedBy: chri(a)gallochri.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=532731) --> (http://bugzilla.novell.com/attachment.cgi?id=532731) Italian po file for choqok Missing italian po file -- 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 809511] New: Won't suspend initially with hardware buttons. Works after the system is suspended from KDE.
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=809511 https://bugzilla.novell.com/show_bug.cgi?id=809511#c0 Summary: Won't suspend initially with hardware buttons. Works after the system is suspended from KDE. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: dac1138(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 Upon a fresh restart, the system will not enter standby by pressing the power button or by closing the laptop lid. (KDE settings are setup to do this.) If suspending the system from the KDE menus, this seems to work. After the system is suspended from the menus, the hardware buttons and closing the lid now work. After a reboot, everything is reset and the power button/lid closing does not suspend the system. Reproducible: Always Steps to Reproduce: 1. Reboot the computer 2. Press the power button or close the lid 3. Since the machine has not entered standby, put the machine into standby by using the KDE menus. 4. Bring machine back from standby and press the power button. Machine will not enter standby as it should. Actual Results: System did not enter standby after pressing the power button or closing the lid. Expected Results: Software should have entered standby. -- 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 814126] New: System instable after resume from disk
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c0 Summary: System instable after resume from disk Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: vbargsten(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=534059) --> (http://bugzilla.novell.com/attachment.cgi?id=534059) Screenshot of lock-up User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 When resuming from disk the system is instable, often leading to a lock-up (see screenshot). Occured using the 12.3 default kernel version and 3.8.4 from kernel-stable repository. I then tried suspend to disk with the debug kernel and saw the journal being filled up quite fast with messages such as Mar 26 22:10:42 vbmobil2.site systemd-journal[370]: Missed 14 kernel messages Mar 26 22:10:42 vbmobil2.site kernel: power_supply BAT1: prop CHARGE_NOW=3885000 Mar 26 22:10:42 vbmobil2.site systemd-journal[370]: Missed 14 kernel messages Mar 26 22:10:42 vbmobil2.site kernel: power_supply BAT1: prop CHARGE_NOW=3885000 Mar 26 22:10:42 vbmobil2.site systemd-journal[370]: Missed 14 kernel messages Mar 26 22:10:42 vbmobil2.site kernel: power_supply BAT1: prop CHARGE_NOW=3885000 I suspect that these messages somehow spam the system and e.g. trigger led events. Since the wireless device ath9k-phy0 is the only one underneath /sys/class/leds/, this may establish the connection to the previous observations (https://bugzilla.novell.com/show_bug.cgi?id=738586) I then tried suspend to disk and resume with the battery removed. This seemed stable (tested for about 10 suspend-resume cycles). Reproducible: Always Steps to Reproduce: 1. Suspend to disk 2. Resume Actual Results: System is instable, often leading to lockup after short time. Expected Results: Successful resume -- 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 812603] New: kworker causing high cpu load
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=812603 https://bugzilla.novell.com/show_bug.cgi?id=812603#c0 Summary: kworker causing high cpu load Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rich(a)westpoint.ltd.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 On my Samsung series 7 chronos laptop (model 700Z5C) I am seeing one of the cores being fully utilised by a kworker process. The problem appears to be the same as the one reported here https://bugzilla.kernel.org/show_bug.cgi?id=53071 I've been able to use the workaround described here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/4 to address the problem on a temporary basis (I had to disable the same entry as this user). Reproducible: Always Steps to Reproduce: 1. No special action required. Actual Results: Well over 90% CPU utilisation by kworker Expected Results: No significant cpu load from kworker. Feel free to ask for any more info that will help address 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 1

[Bug 828378] New: non functional number pad - functional only for one [initial] entry - did the same thing with opensuse 12.2
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=828378 https://bugzilla.novell.com/show_bug.cgi?id=828378#c0 Summary: non functional number pad - functional only for one [initial] entry - did the same thing with opensuse 12.2 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: naggar(a)sprintmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I upgraded my hardware [from 32 to 64 bits] when I went to opensuse 12.3 [64 bit]from 12.2 [32 bit]. Also went from a single to a six core amd cpu,and from a 250MB hd to a 2TB hd. As the problem occurred with opensuse 12.2 and again with the 12.3 version and totally different hardware I am assuming that the problem is most likely a kernel one but I have no real evidence except the deduction. It has surprised me that the problem was not corrected in the 12.3 version because it is an annoying problem as one's right hand does automatically fly to the number pad. Reproducible: Always Steps to Reproduce: 1.I downloaded both the 12.2 [32] and 12.3 [64] versions and installed them 2.I can use the numpad to enter the numeric code for the pw then the numpad becomes inoperative. The number is different from 12.2 to 12.3 3.Rebooting will get the numpad functional for the initial entry only. Actual Results: The problem is very consistent with opensuse 12.3 - [I no longer use opensuse 12.2 and the older hardware]. I seem to remember that the problem did not occur at the initial 12.2 installation but I might be wrong. Happens every time the opensuse 12.3 system boots up. Expected Results: Unfortunately the problem does not go away and reappears every time the system is running. While the numpad problem is not crippling it is very annoying and I cannot understand why nobody else has not reported it. The problem might not occur in the kernel - could it be the use of grub2? The consistency of the problem in 12.3 has baffled me. I keep expecting the next upgrade to resolve the issue. -- 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 829309] New: radeon_uvd: Can't load firmware "radeon/TAHITI_uvd.bin" - but [drm] Loading ARUBA Microcode
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=829309 https://bugzilla.novell.com/show_bug.cgi?id=829309#c0 Summary: radeon_uvd: Can't load firmware "radeon/TAHITI_uvd.bin" - but [drm] Loading ARUBA Microcode Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: x86 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: abittner(a)abittner.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:22.0) Gecko/20100101 Firefox/22.0 dmesg shows radeon_uvd: Can't load firmware "radeon/TAHITI_uvd.bin" but also: [drm] Loading ARUBA Microcode system is asus f2a85-m pro, with amd a10-5700 apu opensuse 13.1 milestone3, x86 Linux linux-5voy 3.10.0-2.gc5ad3f9-desktop #1 SMP PREEMPT Tue Jul 2 09:34:13 UTC 2013 (c5ad3f9) i686 athlon i386 GNU/Linux [ 0.161375] smpboot: CPU0: AMD A10-5700 APU with Radeon(tm) HD Graphics (fam: 15, model: 10, stepping: 01) Reproducible: Always Steps to Reproduce: 1. 2. 3. dmesg | grep -i firmwa -A 9 -B 9 [ 1.714904] radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) [ 1.714907] radeon 0000:00:01.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF [ 1.715483] [drm] Detected VRAM RAM=512M, BAR=256M [ 1.715486] [drm] RAM width 64bits DDR [ 1.715556] [TTM] Zone kernel: Available graphics memory: 259836 kiB [ 1.715558] [TTM] Zone highmem: Available graphics memory: 16298808 kiB [ 1.715559] [TTM] Initializing pool allocator [ 1.715599] [drm] radeon: 512M of VRAM memory ready [ 1.715600] [drm] radeon: 512M of GTT memory ready. [ 1.720966] radeon 0000:00:01.0: radeon_uvd: Can't load firmware "radeon/TAHITI_uvd.bin" [ 1.720987] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1.721530] [drm] Loading ARUBA Microcode [ 1.727071] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 1.727161] radeon 0000:00:01.0: WB enabled [ 1.727164] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xff288c00 [ 1.727166] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04 and cpu addr 0xff288c04 [ 1.727168] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08 and cpu addr 0xff288c08 [ 1.727170] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xff288c0c [ 1.727171] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10 and cpu addr 0xff288c10 -- 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 795389] New: Firefox 17 under KDE using gtk upload dialog
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=795389 https://bugzilla.novell.com/show_bug.cgi?id=795389#c0 Summary: Firefox 17 under KDE using gtk upload dialog Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: wengxt(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0 When firefox and kde integration installed, upload dialog will still be the gtk one, while open, save as still be the kde one. This seems happens only since firefox 17. Reproducible: Always Steps to Reproduce: 1. open a web page that can upload file 2. open upload file dialog Actual Results: a gtk dialog shows Expected Results: a kde dialog shows -- 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 813897] New: Kernel OOPS in rpc_pipe.c:469
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=813897 https://bugzilla.novell.com/show_bug.cgi?id=813897#c0 Summary: Kernel OOPS in rpc_pipe.c:469 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: gleixner(a)bib-bvb.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Sometimes a kernel OOPS occurs, and after that, local mail delivery from postfix to cyrus imapd does not work until next reboot. The system is patched using evergreen repo, and worked well for a long time. Firs occurence of this bug is 22 March 2013. Kernel OOPS: Apr 6 22:39:08 carl kernel: [110997.098888] ------------[ cut here ]------------ Apr 6 22:39:08 carl kernel: [110997.098971] kernel BUG at /usr/src/packages/BUILD/kernel-default-2.6.37.6/linux-2.6.37/net/sunrpc/rpc_pipe.c:469! Apr 6 22:39:08 carl kernel: [110997.098986] invalid opcode: 0000 [#1] SMP Apr 6 22:39:08 carl kernel: [110997.098995] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map Apr 6 22:39:08 carl kernel: [110997.099006] CPU 1 Apr 6 22:39:08 carl kernel: [110997.099009] Modules linked in: autofs4 nfs lockd fscache nfs_acl auth_rpcgss sunrpc mperf reiserfs dm_mod i2c_piix4 sg pcspkr sr_mod cdrom virtio_net floppy virtio_balloon button virtio_console virtio_blk uhci_hcd ehci_hcd virtio_pci virtio_ring virtio usbcore fan thermal processor thermal_sys [last unloaded: preloadtrace] Apr 6 22:39:08 carl kernel: [110997.099071] Apr 6 22:39:08 carl kernel: [110997.099078] Pid: 22560, comm: mount.nfs4 Not tainted 2.6.37.6-24-default #1 Bochs Bochs Apr 6 22:39:09 carl kernel: [110997.099093] RIP: 0010:[<ffffffffa02061c4>] [<ffffffffa02061c4>] __rpc_create_common+0xa4/0xe0 [sunrpc] Apr 6 22:39:09 carl kernel: [110997.099145] RSP: 0018:ffff88000b7ebae8 EFLAGS: 00010246 Apr 6 22:39:09 carl kernel: [110997.099153] RAX: 0000000000000000 RBX: ffff8800051b3980 RCX: ffffffffa020b5c0 Apr 6 22:39:09 carl kernel: [110997.099163] RDX: 0000000000001180 RSI: ffff8800051b3980 RDI: ffff88001eb89c40 Apr 6 22:39:09 carl kernel: [110997.099173] RBP: ffff88001eb89c40 R08: ffff880002000000 R09: 0000000000000000 Apr 6 22:39:09 carl kernel: [110997.099182] R10: ffff880002000000 R11: 0000000000010000 R12: ffffffffa020b5c0 Apr 6 22:39:09 carl kernel: [110997.099192] R13: ffff88001fbfb2c0 R14: ffff880002000000 R15: ffff880002000000 Apr 6 22:39:09 carl kernel: [110997.099227] FS: 00007f2e20ec1700(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000 Apr 6 22:39:09 carl kernel: [110997.099239] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 6 22:39:09 carl kernel: [110997.099246] CR2: 00007f2e21104000 CR3: 0000000037b73000 CR4: 00000000000006e0 Apr 6 22:39:09 carl kernel: [110997.099276] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 6 22:39:09 carl kernel: [110997.099305] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 6 22:39:09 carl kernel: [110997.099316] Process mount.nfs4 (pid: 22560, threadinfo ffff88000b7ea000, task ffff88000b7f22c0) Apr 6 22:39:09 carl kernel: [110997.099325] Stack: Apr 6 22:39:09 carl kernel: [110997.099330] ffffffffa02cc1d9 ffff8800051b3980 ffffffffa02ca320 ffff88001fbfb2c0 Apr 6 22:39:09 carl kernel: [110997.099345] ffff88001eb89d00 ffffffffa0206ecf 0000000000000010 ffff880000001180 Apr 6 22:39:09 carl kernel: [110997.099358] ffff88001eb89c40 00000000000080d0 0000000511bcc18d ffffffffa02cc1d9 Apr 6 22:39:09 carl kernel: [110997.099371] Call Trace: Apr 6 22:39:09 carl kernel: [110997.099594] [<ffffffffa0206ecf>] rpc_mkpipe+0x13f/0x200 [sunrpc] Apr 6 22:39:09 carl kernel: [110997.099782] [<ffffffffa02c4648>] nfs_idmap_new+0x78/0x150 [nfs] Apr 6 22:39:09 carl kernel: [110997.100067] [<ffffffffa0293a3f>] nfs4_init_client+0x8f/0x180 [nfs] Apr 6 22:39:09 carl kernel: [110997.100101] [<ffffffffa0293bb2>] nfs4_set_client+0x82/0x110 [nfs] Apr 6 22:39:09 carl kernel: [110997.100130] [<ffffffffa0293ce9>] nfs4_init_server+0xa9/0x250 [nfs] Apr 6 22:39:09 carl kernel: [110997.100161] [<ffffffffa0294649>] nfs4_create_server+0x39/0xe0 [nfs] Apr 6 22:39:09 carl kernel: [110997.100195] [<ffffffffa02a1e4c>] nfs4_remote_mount+0x6c/0x3d0 [nfs] Apr 6 22:39:09 carl kernel: [110997.100253] [<ffffffff8114b139>] vfs_kern_mount+0x89/0x280 Apr 6 22:39:10 carl kernel: [110997.100282] [<ffffffffa02a0bee>] nfs_do_root_mount+0x7e/0xc0 [nfs] Apr 6 22:39:10 carl kernel: [110997.100347] [<ffffffffa02a0d3c>] nfs4_try_mount+0x4c/0xd0 [nfs] Apr 6 22:39:10 carl kernel: [110997.100429] [<ffffffffa02a0e2a>] nfs4_get_sb+0x6a/0x100 [nfs] Apr 6 22:39:10 carl kernel: [110997.100483] [<ffffffff8114b292>] vfs_kern_mount+0x1e2/0x280 Apr 6 22:39:10 carl kernel: [110997.100499] [<ffffffff8114b3a3>] do_kern_mount+0x53/0x130 Apr 6 22:39:10 carl kernel: [110997.100515] [<ffffffff81165922>] do_mount+0x1e2/0x210 Apr 6 22:39:10 carl kernel: [110997.100530] [<ffffffff81165a3a>] sys_mount+0x9a/0xf0 Apr 6 22:39:10 carl kernel: [110997.100547] [<ffffffff81002e4b>] system_call_fastpath+0x16/0x1b Apr 6 22:39:10 carl kernel: [110997.100564] [<00007f2e207fbeea>] 0x7f2e207fbeea Apr 6 22:39:10 carl kernel: [110997.100571] Code: 33 6e f5 e0 48 89 df e8 2b 58 f5 e0 31 c0 48 8b 1c 24 48 8b 6c 24 08 4c 8b 64 24 10 4c 8b 6c 24 18 4c 8b 74 24 20 48 83 c4 28 c3 <0f> 0b 48 8b 4b 38 48 c7 c2 20 b5 20 a0 48 c7 c6 18 f2 20 a0 48 Apr 6 22:39:10 carl kernel: [110997.100640] RIP [<ffffffffa02061c4>] __rpc_create_common+0xa4/0xe0 [sunrpc] Apr 6 22:39:10 carl kernel: [110997.100671] RSP <ffff88000b7ebae8> 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 1

[Bug 804185] AUDIT-0: spice-gtk: polkit-unauthorized-privilege
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=804185 https://bugzilla.novell.com/show_bug.cgi?id=804185#c8 --- Comment #8 from Sebastian Krahmer <krahmer(a)suse.com> 2013-07-15 14:03:38 UTC --- We wont accept a new suid binary. -- 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