February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 999512] Tumbleweed installation and Tumbleweed in self can not sense the hardware glide point and track point of Lenovo
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=999512 http://bugzilla.suse.com/show_bug.cgi?id=999512#c13 --- Comment #13 from Krasimir Ivanov <kiv(a)mail.orbitel.bg> --- Thank you for this suggestion. I will try to create a bug report there probably within the next week. With best regards, -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022727] yast2 problem: Window does not open if started remotely via ssh
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022727 http://bugzilla.suse.com/show_bug.cgi?id=1022727#c13 Rainer Krienke <krienke(a)uni-koblenz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #13 from Rainer Krienke <krienke(a)uni-koblenz.de> --- After searching a while for this symptom I came across this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1174257#c6 The problem seems to be dri3 forwarding over ssh. In the bug report there is a workaround. If I start yast2 on the remote side in the following way it works: $ LIBGL_DRI3_DISABLE=1 /sbin/yast2 disk Just running $ /sbin/yast2 disk does not work. Why this only happens when I connect to a SLES12SP2 system is something I cannot explain. It happens with SLES12SP2 VMs as well as physical SLES12SP2 systems. Running: $ grep DRI /var/log/Xorg.0.log 2306.669] (II) glamor: EGL version 1.4 (DRI2): [ 2306.785] (II) modeset(0): [DRI2] Setup complete [ 2306.785] (II) modeset(0): [DRI2] DRI driver: i965 [ 2306.785] (II) modeset(0): [DRI2] VDPAU driver: i965 [ 2306.808] (II) GLX: Initialized DRI2 GL provider for screen on my local 42.2 system, you see that my system is not using DRI3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1021062] New: yast2 clone_system fails to work with systemd 232
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1021062 Bug ID: 1021062 Summary: yast2 clone_system fails to work with systemd 232 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 710986 --> http://bugzilla.suse.com/attachment.cgi?id=710986&action=edit complete yast logs in the TW staging, we see this issue while clone an fresh system https://openqa.opensuse.org/tests/337891#step/yast2_clone_system/3 2017-01-20 03:32:06 <1> linux-04c2(3587) [Ruby] yast2/systemd_unit.rb:122 `systemctl show iscsid.socket --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath ` 2017-01-20 03:32:06 <3> linux-04c2(3587) [Ruby] yast2/systemd_unit.rb:151 Failed to get properties for unit 'iscsid' ; Command ` LANG=C TERM=dumb COLUMNS=1024 systemctl --no-legend --no-pager --no-ask-password show iscsid.socket --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath ` returned error: 2017-01-20 03:32:06 <3> linux-04c2(3587) [Ruby] yast/wfm.rb:236 Client call failed with 'Socket unit 'iscsid' not found' and backtrace ["/usr/share/YaST2/modules/systemd_socket.rb:79:in `find!'", "/usr/share/YaST2/modules/IscsiClientLib.rb:1089:in `getServiceStatus'", "/usr/share/YaST2/modules/IscsiClient.rb:210:in `Read'", "/usr/share/YaST2/clients/iscsi-client_auto.rb:98:in `main'", "/usr/share/YaST2/clients/iscsi-client_auto.rb:126:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:223:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:223:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:192:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:192:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:181:in `CallFunction'", "/usr/share/YaST2/modules/Call.rb:44:in `Function'", "/usr/share/YaST2/modules/AutoinstClone.rb:109:in `CommonClone'", "/usr/share/YaST2/modules/AutoinstClone.rb:199:in `block in Process'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:92:in `call'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:92:in `block in foreach'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:91:in `each'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:91:in `foreach'", "/usr/share/YaST2/modules/AutoinstClone.rb:187:in `Process'", "/usr/share/YaST2/clients/clone_system.rb:131:in `doClone'", "/usr/share/YaST2/clients/clone_system.rb:62:in `main'", "/usr/share/YaST2/clients/clone_system.rb:139:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:223:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:223:in `run_client'"] 2017-01-20 03:32:06 <3> linux-04c2(3587) [Ruby] yast/wfm.rb:257 Internal error. Please report a bug report with logs. Details: Socket unit 'iscsid' not found Caller: /usr/share/YaST2/modules/systemd_socket.rb:79:in `find!' the complete yast2 logs are attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1022271] X509_get_default_cert_file() returns an incorrect path
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022271 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:4105:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1000036] devel:languages:nodejs/nodejs: CA certificates broken on SLE11
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1000036 http://bugzilla.suse.com/show_bug.cgi?id=1000036#c10 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #10 from Adam Majer <amajer(a)suse.com> --- fixed when openssl1 gets through the QA process. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018120] tolua++: version/date in generated code
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1018120 http://bugzilla.suse.com/show_bug.cgi?id=1018120#c7 --- Comment #7 from Olaf Hering <ohering(a)suse.com> --- I'm sure there is nothing to be done on my side. The updated introduces no new problem. Just go ahead and release it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022727] yast2 problem: Window does not open if started remotely via ssh
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022727 http://bugzilla.suse.com/show_bug.cgi?id=1022727#c12 --- Comment #12 from Rainer Krienke <krienke(a)uni-koblenz.de> --- I guess I was to quick about saying that it works :-( Yesterday I simply tested if the yast2 window opens, which was originally not true, but after reinstalling gnome-keyring it worked again. However I did not test to open any module of yast2, which still does not work from my desktop. Actually I reinstalled my desktop (reconfiguring it as NFS client again) today to avoid trouble from possibly missing packages... To use NFS and centrally managed users it needs also configuration for ldap, krb5, sssd, autofs and nis. When running yast2 remotely on a SLES12SP2 host the controlcenter appears. When I select any module to start nothing happens again. If I try to run eg yast sw_single also nothing happens, no window opens. Also qdirstat does not open. On the other side I have a notebook with 42.2 where a yast2 disk started remotely on the same SLES12SP2 host does work without problems. So my guess is, that some part of the configuration from above might cause the trouble but at the moment I have no idea how to find out more. If anyone has an idea please let me know... Thanks Rainer -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 952781] New: [SiS] startx session exit puts display configuration out of range
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=952781 Bug ID: 952781 Summary: [SiS] startx session exit puts display configuration out of range Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 653900 --> http://bugzilla.opensuse.org/attachment.cgi?id=653900&action=edit dmesg output captured blindly from startx's vtty after startx exit lspci reports onboard XGI Z7/Z9 (XG20 core) video Xorg is using xf86-video-sis-0.10.8-2.1.x86_64 driver via xorg.conf and display's native 1680x1050 mode (VESA 1024x768 without any xorg.conf): To reproduce: 1-login on a TW vtty in multi-user.target 2-startx plasma or icewm session 3-exit the plasma or icewm session normally Actual behavior: 1-display put out of range 2-no action possible produces visual response before reboot effected Expected behavior: 1-normal return to bash shell on vtty -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 958306] spice-gtk: spice_audio_get_playback_volume_info_async() segfault
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=958306 http://bugzilla.suse.com/show_bug.cgi?id=958306#c20 --- Comment #20 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (958306) was mentioned in https://build.opensuse.org/request/show/454134 Factory / spice-gtk -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 999512] Tumbleweed installation and Tumbleweed in self can not sense the hardware glide point and track point of Lenovo
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=999512 http://bugzilla.suse.com/show_bug.cgi?id=999512#c12 Max Staudt <mstaudt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstaudt(a)suse.com Flags|needinfo?(kiv(a)mail.orbitel. | |bg) | --- Comment #12 from Max Staudt <mstaudt(a)suse.com> --- (Clearing old NEEDINFO for Krasimir) Thanks a bunch for your feedback! We've seen some issues of our own with Alps pointing devices recently. Unfortunately we can't look into it any further since we didn't have that machine for long. When the Alps devices do work, just not well enough, this is most probably a kernel level problem. Maybe you could be so kind as to report this upstream? https://bugzilla.kernel.org/ Please be sure to at least try our latest KOTD before reporting anything upstream: http://kernel.opensuse.org/branches/master Note to anyone with a "classic" ThinkPad (T, W, X series): These use a derivative of the classic IBM TrackPoint IV, and a Synaptics touchpad. Totally different hardware, and it works well as far as I know. -- You are receiving this mail because: You are on the CC list for the bug.

1 0