August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 892253] New: updating to nvidia 340.32 => no more glx
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892253 https://bugzilla.novell.com/show_bug.cgi?id=892253#c0 Summary: updating to nvidia 340.32 => no more glx Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: epistemepromeneur(a)free.fr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 today there were an update pf nvidia driver to 340.32 after rebooting i launch the "nvidia settings" tool at "openGL/GLX information" there is an error message : "Failed to query the GLX server vendor." with glxinfo i have this : ******************************************************************************** x@linux-b4lz:~> glxinfo name of display: :0 Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Error: couldn't find RGB GLX visual or fbconfig Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Error: couldn't find RGB GLX visual or fbconfig Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". ... Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". x@linux-b4lz:~> ******************************************************************************** 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 7

[Bug 892759] New: "Install Hypervisor and Tools" fails with error: Details: undefined method `+' for nil:NilClass
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892759 https://bugzilla.novell.com/show_bug.cgi?id=892759#c0 Summary: "Install Hypervisor and Tools" fails with error: Details: undefined method `+' for nil:NilClass Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: kgronlund(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- After selecting KVM server and tools in the Install Hypervisor and Tools screen, the installer fails with an error message: Internal error. Please report a bug report with logs. Details: undefined method `+' for nil:NilClass Caller: /usr/share/YaST2/modules/VirtConfig.rb:380:in `ConfigureDom0' Excerpt from y2log: 2014-08-20 15:02:52 <1> krigpad.site(7082) [Ruby] modules/VirtConfig.rb:95 Platform is openSUSE 2014-08-20 15:02:52 <3> krigpad.site(7082) [Ruby] yast/wfm.rb:197 Client call failed with 'undefined method `+' for nil:NilClass' and backtrace ["/usr/share/YaST2/modules/VirtConfig.rb:380:in `ConfigureDom0'", "/usr/share/YaST2/clients/virtualization.rb:93:in `CheckConfiguration'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/fun_ref.rb:33:in `call'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/fun_ref.rb:33:in `call'", "/usr/share/YaST2/modules/CommandLine.rb:1591:in `Run'", "/usr/share/YaST2/clients/virtualization.rb:59:in `main'", "/usr/share/YaST2/clients/virtualization.rb:102:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:184:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:184:in `run_client'"] 2014-08-20 15:02:52 <3> krigpad.site(7082) [Ruby] yast/wfm.rb:202 Internal error. Please report a bug report with logs. Details: undefined method `+' for nil:NilClass Caller: /usr/share/YaST2/modules/VirtConfig.rb:380:in `ConfigureDom0' -- 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 890123] New: gpgme 1.5.1 Fixes possible overflow in gpgsm and uiserver engines
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=890123 https://bugzilla.novell.com/show_bug.cgi?id=890123#c0 Summary: gpgme 1.5.1 Fixes possible overflow in gpgsm and uiserver engines Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 From http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=blob;f=NEWS;h=0ea405b… Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0] ------------------------------------------------------------- * Fixed possible overflow in gpgsm and uiserver engines. [CVE-2014-3564] * Added support for GnuPG 2.1's --with-secret option. * Interface changes relative to the 1.5.0 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GPGME_KEYLIST_MODE_WITH_SECRET NEW. Reproducible: Didn't try -- 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 12

[Bug 892092] New: Users Cannot View Their Own Journalctl Logs
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892092 https://bugzilla.novell.com/show_bug.cgi?id=892092#c0 Summary: Users Cannot View Their Own Journalctl Logs Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem 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; rv:31.0) Gecko/20100101 Firefox/31.0 It's stated on freedesktop.org that "All users are granted access to their private per-user journals. However, by default, only root and users who are members of the "systemd-journal" group get access to the system journal and the journals of other users." However, that is not the case on openSUSE. Journalctl yields nothing unless it's run as root; I cannot view my own journals. This shouldn't be the default behavior. Reproducible: Always Steps to Reproduce: 1.type journalctl in a terminal and notice the lack of journals 2.type sudo journalctl 3. Notice that there are tons of logs about the user Actual Results: No journals without root privileges Expected Results: user-specific journals for users -- 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 892752] New: alljava.sh sets JAVA_HOME to wrong jdk
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892752 https://bugzilla.novell.com/show_bug.cgi?id=892752#c0 Summary: alljava.sh sets JAVA_HOME to wrong jdk Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: novell(a)chromanet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Installed was jre-1.7.0-openjdk and sun jdk1.8.0_11. Installed ant. Ant needs jre-1.5.0-gcj. $JAVA_HOME was set to jre-1.5.0, even though /usr/sbin/update-alternatives --config javac pointed to /usr/java/jdk1.8.0_11/bin/javac and /usr/sbin/update-alternatives --config java pointed to /usr/java/latest/bin/java Reason: /etc/profile.d/alljava.sh uses the first found JDK in /usr/lib64/jvm, which is java-1.5.0 -> /etc/alternatives/java_sdk_1.5.0 Workaround: added a symlink default -> /usr/java/latest Reproducible: Always Steps to Reproduce: 1. Install JDK 2. Install ant, then execute /etc/profile.d/alljava.sh 3. Check $JAVA_HOME Actual Results: $JAVA_HOME=/usr/lib64/jvm/java-1.5.0 Expected Results: $JAVA_HOME=/usr/lib64/jvm/java-1.7.0-openjdk -- 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 737527] New: arpwatch fails to start if interface is controlled by NetworkManager
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=737527 https://bugzilla.novell.com/show_bug.cgi?id=737527#c0 Summary: arpwatch fails to start if interface is controlled by NetworkManager Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: halsmit(a)t-online.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 There is this ifstatus check in the init script that fails if NM controls that device. Also, an arpwatch account would be nice. Reproducible: Always Steps to Reproduce: 1.enter IF you want to listen on to sysconfig/arpwatch 2.start arpwatch service 3. Actual Results: does not start Expected Results: does start to listen on specified 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 10

[Bug 892683] New: wpa_supplicant systemd dbus activation broken
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892683 https://bugzilla.novell.com/show_bug.cgi?id=892683#c0 Summary: wpa_supplicant systemd dbus activation broken Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: vbotka(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- the dbus config files for wpa_supplicant lack the following line: SystemdService=wpa_supplicant.service that allows systemd to take care of activating those units instead of dbus. -- 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 862824] New: lsb package modularization into sub-packages
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=862824 https://bugzilla.novell.com/show_bug.cgi?id=862824#c0 Summary: lsb package modularization into sub-packages Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: openSUSE 13.2 Status: NEEDINFO Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: pgajdos(a)suse.com ReportedBy: jsmeix(a)suse.com QAContact: qa-bugs(a)suse.de CC: jeff(a)licquia.org, rschweikert(a)suse.com InfoProvider: rschweikert(a)suse.com Found By: Development Blocker: No This is an enhancement request for modularization of the lsb package into sub-packages. The lsb package itself would require all its sub-packages to ensure that when "lsb" is intalled the system actually is LSB compliant (i.e. the system provides all requirements as outlined in the LSB specification) according to what Robert Schweikert wrote in https://bugzilla.novell.com/show_bug.cgi?id=807747#c4 and http://lists.linuxfoundation.org/pipermail/lsb-discuss/2013-May/007643.html Reasoning for the modularization into sub-packages: When a package actually requires only parts of the LSB specification (e.g. when a package actually requires only "LSB core") it would be nice when that package would not need to get the whole LSB installed. The whole LSB requires various graphical libraries, sound stuff, printing stuff, and so on which could be much too much e.g. for software that is meant to run also on a minimal server without graphical libraries, sound stuff, printing stuff, and so on. For an example see the rear package. Rear is a set of bash scripts (plus documentation) for disaster recovery in particular to be used also on server systems. If the rear RPM would "Requires: lsb" then it could not be installed on a minimal server. See my issue report to Rear upstream as "RFC: Cleanup of the LSB RPM requirements in Rear RPM" on rear-devel(a)lists.relax-and-recover.org http://pikachu.3ti.be/pipermail/rear-devel/2014-February/000293.html and subsequent postings there. I am not at all a LSB expert so that I am not the right one to actually decide about modularization of the lsb package but Jeff Licquia and Robert Schweikert are LSB experts... Robert Schweikert and Jeff Licquia, can you provide background information whether or not such a modularization of the lsb package into sub-packages makes sense and does not contradict the LSB specification. Many thanks in advance! -- 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 889307] New: Network configuration problems using wicked
by bugzilla_noreply＠novell.com 20 Aug '14

20 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=889307 https://bugzilla.novell.com/show_bug.cgi?id=889307#c0 Summary: Network configuration problems using wicked Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sboyce(a)blueyonder.co.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=600139) --> (http://bugzilla.novell.com/attachment.cgi?id=600139) /etc/wicked/ifconfig/network.xml User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 "wicked convert /etc/sysconfig/network > network.xml" "cp network.xml /etc/wicked/ifconfig" Removed /etc/sysconfig/network/ifcfg-* wickedd is always running. lancelot@slipstream:~> ps fax|grep wicked 866 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground 867 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground 868 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground 872 ? SLs 0:00 /usr/sbin/wickedd --systemd --foreground 877 ? SLs 0:00 /usr/sbin/wickedd-nanny --systemd --foreground Only localhost is configured. If I put the ifcfg-* scripts back, the network starts up. Reproducible: Always Steps to Reproduce: 1.Reboot 2. 3. Actual Results: Only localhost is configured Expected Results: Network should come up. -- 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 887051] New: yast2 sw_single segfaults
by bugzilla_noreply＠novell.com 19 Aug '14

19 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=887051 https://bugzilla.novell.com/show_bug.cgi?id=887051#c0 Summary: yast2 sw_single segfaults Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: jnelson-suse(a)jamponi.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 yast2 sw_single segfaults all the time with openSUSE Factory. zypper 'up' and 'dup' both show no updates. 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 12