November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 848792] New: AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 52: Invalid mode, 'x' must be preceded by exec qualifier 'i', 'p', 'c', or 'u'
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848792 https://bugzilla.novell.com/show_bug.cgi?id=848792#c0 Summary: AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 52: Invalid mode, 'x' must be preceded by exec qualifier 'i', 'p', 'c', or 'u' Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM AssignedTo: kvm-bugs(a)forge.provo.novell.com ReportedBy: srinidhi(a)novell.com QAContact: jdouglas(a)suse.com Found By: --- Blocker: --- In openSUSE 13.1 RC2, apparmor doesn't start correctly when libvirt-daemon package is installed: # systemctl status apparmor.service -l apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/boot.apparmor) Active: active (exited) since Sun 2013-11-03 13:50:14 IST; 45s ago Process: 3087 ExecStart=/etc/init.d/boot.apparmor start (code=exited, status=0/SUCCESS) Nov 03 13:50:14 srinidhi.blr.novell.com boot.apparmor[3087]: Starting AppArmor AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 52: Invalid mode, 'x' must be preceded by exec qualifier 'i', 'p', 'c', or 'u' Nov 03 13:50:14 srinidhi.blr.novell.com boot.apparmor[3087]: /etc/apparmor.d/usr.sbin.libvirtd failed to load..failed Nov 03 13:50:14 srinidhi.blr.novell.com boot.apparmor[3087]: ..done Nov 03 13:50:14 srinidhi.blr.novell.com systemd[1]: Started LSB: AppArmor initialization. Additional information (not sure if it would help): # rpm -qi libvirt-daemon Name : libvirt-daemon Version : 1.1.2 Release : 2.4.1 Architecture: x86_64 Install Date: Thu Oct 31 18:39:03 2013 Group : Development/Libraries/C and C++ Size : 2302503 License : LGPL-2.1+ Signature : RSA/SHA256, Tue Oct 29 14:04:43 2013, Key ID b88b2fd43dbdc284 Source RPM : libvirt-1.1.2-2.4.1.src.rpm Build Date : Tue Oct 29 14:03:10 2013 Build Host : cloud113 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://libvirt.org/ Summary : Server side daemon and supporting files for libvirt library Description : Server side daemon required to manage the virtualization capabilities of recent versions of Linux. Requires a hypervisor specific sub-RPM for specific drivers. Distribution: openSUSE 13.1 # rpm -qi apparmor-parser Name : apparmor-parser Version : 2.8.2 Release : 4.5.1 Architecture: x86_64 Install Date: Thu Oct 31 17:55:52 2013 Group : Productivity/Networking/Security Size : 892054 License : GPL-2.0+ Signature : RSA/SHA256, Mon Oct 21 17:14:08 2013, Key ID b88b2fd43dbdc284 Source RPM : apparmor-2.8.2-4.5.1.src.rpm Build Date : Mon Oct 21 17:13:13 2013 Build Host : build17 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : https://launchpad.net/apparmor Summary : AppArmor userlevel parser utility Description : The AppArmor Parser is a userlevel program that is used to load in program profiles to the AppArmor Security kernel module. This package is part of a suite of tools that used to be named SubDomain. Distribution: openSUSE 13.1 -- 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 848806] New: Make whois case-insensitive
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848806 https://bugzilla.novell.com/show_bug.cgi?id=848806#c0 Summary: Make whois case-insensitive Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: api AssignedTo: adrian(a)suse.com ReportedBy: jengelh(a)inai.de QAContact: adrian(a)suse.com Found By: Beta-Customer Blocker: --- Are usernames in the Novell identity provider actually case-sensitive or not? If they are, the Build Service, and eventually osc whois should support case-insensitive search. -- 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 819812] New: syslinux 5.0+ is now available. Please upgrade factory to 5.0+
by bugzilla_noreply＠novell.com 03 Nov '13

03 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=819812 https://bugzilla.novell.com/show_bug.cgi?id=819812#c0 Summary: syslinux 5.0+ is now available. Please upgrade factory to 5.0+ Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 syslinux 5.0+ is now available. 4.04 comes with some nasty bugs http://www.zytor.com/pipermail/syslinux/2011-February/016433.html and others. 4.06 is available, too, but since 5.0.1 is now out, it would be ideal to use that version. 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 826660] New: yast2 installer from KDE Live CD calls "hostname --fqdn" which takes ~30 seconds to fail
by bugzilla_noreply＠novell.com 03 Nov '13

03 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=826660 https://bugzilla.novell.com/show_bug.cgi?id=826660#c0 Summary: yast2 installer from KDE Live CD calls "hostname --fqdn" which takes ~30 seconds to fail Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Immediately after clicking 'Next' in the yast2 installer screen for partitioning, the entire UI simply ... stops. For about 30 seconds. Sometimes a bit more, sometimes a bit less. Strace tells me it's waiting for 'hostname' or 'hostname --fqdn' to fail or succeed. The logs say: hostname: System error 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 6

[Bug 835020] New: can't use nmcli from console to re-enable networking
by bugzilla_noreply＠novell.com 03 Nov '13

03 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=835020 https://bugzilla.novell.com/show_bug.cgi?id=835020#c0 Summary: can't use nmcli from console to re-enable networking Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 A machine I use remotely some of the time had been rebooted, so I tried to ssh in (unsuccessfully). I physically located the machine and logged into the console to investigate things, and found that no network had been configured. After a bit, I determined that network manager was "asleep" for some reason. I tried to un-sleep it, unsuccessfully. This necessitated starting a graphical login and using the (KDE, in this case) network manager applet to re-enable networking. While it's irritating that networkmanager was asleep after reboot, it's even more irritating that I couldn't wake it up from the console (as root!). linux-k1fq:~ # nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running asleep enabled enabled enabled disabled linux-k1fq:~ # nmcli nm sleep false Error in sleep: Rejected send message, 7 matched rules; type="method_call", sender=":1.30" (uid=0 pid=10214 comm="nmcli nm sleep false ") interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=10161 comm="/usr/sbin/NetworkManager --no-daemon ") 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 832622] New: r8169: no gig-e performance, really slow 'link' detection
by bugzilla_noreply＠novell.com 03 Nov '13

03 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=832622 https://bugzilla.novell.com/show_bug.cgi?id=832622#c0 Summary: r8169: no gig-e performance, really slow 'link' detection 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: jnelson-suse(a)jamponi.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 My Lenovo B570 has an r8169 ethernet. As reported a few others places (google "r8169 gig-e" and similar), the r8169 apparently has 'issues'. In my case, I only get 100Mbit out of it (despite being connected to a 1000Mbit switch). Also, the link detection is /really/ slow. My e1000e is near-instant. This might take 10's of seconds or more. ethtool eth0: Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0000ffff (65535) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol 0x8000 Link detected: yes ethtool -i eth0: driver: r8169 version: 2.3LK-NAPI firmware-version: rtl_nic/rtl8168e-2.fw bus-info: 0000:03:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no dmesg | grep eth0: [ 16.374342] r8169 0000:03:00.0 eth0: RTL8168e/8111e at 0xffffc90000622000, f0:de:f1:94:1b:2c, XID 0c200000 IRQ 43 [ 16.375927] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 26.760841] r8169 0000:03:00.0 eth0: link down [ 26.761880] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 36.789963] r8169 0000:03:00.0 eth0: PHY reset until link up [ 46.811547] r8169 0000:03:00.0 eth0: PHY reset until link up [ 56.833199] r8169 0000:03:00.0 eth0: PHY reset until link up [ 66.854703] r8169 0000:03:00.0 eth0: PHY reset until link up [ 76.877164] r8169 0000:03:00.0 eth0: PHY reset until link up [ 86.897893] r8169 0000:03:00.0 eth0: PHY reset until link up [ 96.919468] r8169 0000:03:00.0 eth0: PHY reset until link up [ 106.941078] r8169 0000:03:00.0 eth0: PHY reset until link up [ 116.962707] r8169 0000:03:00.0 eth0: PHY reset until link up [ 126.984350] r8169 0000:03:00.0 eth0: PHY reset until link up [ 137.005927] r8169 0000:03:00.0 eth0: PHY reset until link up [ 147.027543] r8169 0000:03:00.0 eth0: PHY reset until link up [ 157.049148] r8169 0000:03:00.0 eth0: PHY reset until link up [ 167.070716] r8169 0000:03:00.0 eth0: PHY reset until link up [ 177.092261] r8169 0000:03:00.0 eth0: PHY reset until link up [ 187.113862] r8169 0000:03:00.0 eth0: PHY reset until link up [ 197.135467] r8169 0000:03:00.0 eth0: PHY reset until link up ^^^^^ LOTS and LOTS of this I did add "options r8169 debug=16" to /etc/modprobe.d/99-local.conf I also tried Kernel:HEAD up through 3.11.0-rc3-1.ge924b54-desktop without improvement. 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 845614] New: 13.1rc1, can't run the installation second step
by bugzilla_noreply＠novell.com 03 Nov '13

03 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=845614 https://bugzilla.novell.com/show_bug.cgi?id=845614#c0 Summary: 13.1rc1, can't run the installation second step Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: All Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: epistemepromeneur(a)free.fr QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 when rebooting to finish the installation then Grub loading Welcome to GRUB! error : symbol "grub_term_highlight_color" not found entering in rescue mode ... grub rescue > Reproducible: Always Steps to Reproduce: 1.launch the installation 2.at the end there is an automatic reboot 3. see grub 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 13

[Bug 844178] New: Better choice of E17 key bindings - Ctrl+w, Alt+F2 and Alt+F4
by bugzilla_noreply＠novell.com 03 Nov '13

03 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=844178 https://bugzilla.novell.com/show_bug.cgi?id=844178#c0 Summary: Better choice of E17 key bindings - Ctrl+w, Alt+F2 and Alt+F4 Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: srinidhi(a)novell.com QAContact: qa-bugs(a)suse.de CC: tcech(a)suse.cz, simon(a)simotek.net Found By: --- Blocker: --- In the default openSUSE profile for E17, following keybindings have been defined: Ctrl+w -> Close Window Alt+F2 -> Run Everything Alt+F4 -> Kill Window Let me start with the first one because this was completely unexpected and was annoying when I first started using E17 after updating to openSUSE 13.1 Beta1. In most of the tabbed applications, for example, firefox, chromium, pidgin, etc., Ctrl+w is mapped by the application to close individual tabs. But in E17 running with openSUSE_classic profile, the keybinding is never passed to the application and the DE kicks in to close the entire application itself! It took me a while to realize this. Alt+F2 and Alt+F4 aren't really a big issue from my personal opinion, but I have an issue with the logic behind this choice. Let me try to explain: Alt+F1 -> Switch to 1st virtual desktop Alt+F2 -> Run Everything Alt+F3 -> Switch to 3rd virtual desktop Alt+F4 -> Kill Window Wouldn't it be confusing for a "new" E17 user that she can't change to 2nd and 4th desktop using similar keybindings as with 1st and 3rd desktop. Interestingly, there are no alternatives - as far as I can see - provided to switch to 2nd and 4th desktops. -- 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 779965] New: boot error: snapshot target support missing from kernel
by bugzilla_noreply＠novell.com 02 Nov '13

02 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=779965 https://bugzilla.novell.com/show_bug.cgi?id=779965#c0 Summary: boot error: snapshot target support missing from kernel Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mathias.froehlich(a)f-i.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0 When booting up 12.2 after live upgrade via zypper with a LVM snapshot volume exisiting in the root VG, the boot process is going in an infinite loop saying: snapshot target support missing from kernel? Reproducible: Always Steps to Reproduce: 1. configure system to boot using LVM volume(s), create snapshot of root volume 2. boot with systemd 3. see error loop on console Actual Results: system unable to boot Expected Results: system boot into runlevel "multi-user" -- 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 845514] New: PlayOnLinux doesnt' create a .desktop file after installation
by bugzilla_noreply＠novell.com 02 Nov '13

02 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=845514 https://bugzilla.novell.com/show_bug.cgi?id=845514#c0 Summary: PlayOnLinux doesnt' create a .desktop file after installation Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML, like Gecko) Chromium/25.0.1349.2 Chrome/25.0.1349.2 Safari/538.1 SUSE/13.1 (3.10.0) Epiphany/3.10.0 PlayOnLinux doesn't create a .desktop file after installation. Launching playonlinux from a terminal displays it as "Python". The application seems to function perfectly well otherwise. Creating a .desktop file manually still gets the application displayed as "Python". Reproducible: Always Steps to Reproduce: 1.install playonlinux 2.notice the missing menu entry 3.launch the app from terminal and notice that it's named "python" Actual Results: no .desktop file created and the item is displayed as "Python" Expected Results: A .desktop file should be created and the application should be displayed as "PlayOnLinux" This bug isn't valid on Manjaro and ElementaryOS -- 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