February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 927786] kernel deadlock in networking
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

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

1 0

[Bug 954138] openSUSE 13.2 does not detect 5 TB USB disk and crashes when it is unplugged
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

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

1 0

[Bug 961739] KVM:
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

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

1 0

[Bug 951194] Some Haswell laptops wake up without reason from S3
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

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

1 0

[Bug 919596] Hyper-V: Add processing of MTU reduced by the host
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

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

1 0

[Bug 959568] BD-RE in random access mode fails
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

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

1 0

[Bug 964154] New: invalid DECLARED bug
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

http://bugzilla.opensuse.org/show_bug.cgi?id=964154 Bug ID: 964154 Summary: invalid DECLARED bug Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: misi(a)ship.hu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Egbert Eich 2016-01-28 19:47:15 UTC WROTE: "You are still using the NVIDIA binary driver although you are using Tumbleweed. I guess, you should have deinstalled it before you switched from 13.2 to TW. Point is, there is no NVIDIA driver for TW. Using a driver for Leap or 13.2 will most likely lead to issues and this is what you might be seeing here. Your best option would be to deinstall the NVIDIA driver. There are some hints on: https://en.opensuse.org/SDB:NVIDIA_drivers#Easy_way_to_get_NVIDIA_drivers how to do this. Since the configuration you are using is not supported, closing as INVALID." Grrrrrrrrrrrrrrrrrrrrrrr. I updated from 13.2 to Tumbleweed. The program let me to do it: zypper dup worked via repository change. Nobody warns me: do this, do that... and what is supported. After this I did ONLY such things as the official updates AND install recommended nvidia driver. If the legacy xdm would not exist and work the whole system would be a catastrophe. It is an (almost fully) WORKING SYSTEM. Was, before upgrade. I MUST use hardware accelerated nvidia driver and it is a valid option for OpenSuSE, moöreover it is a vendor-launched proprietary driver. You should test the vnc/ssvnc ---> Xvnc/x11vnc ---> xdm-kdm(or,switched)ssdm ---> other desktop applications ---> graphical programs combination-chain. The workflow should be transparent in ideal case. YOU let me to do this and declared it invalid? It is an incorrect behavior. You deteriorate my system... then fix it. What can I do? Throw out the whole system, hardware and software? You should TEST thoroughly a distribution BEFORE launch instead develop a system AFTER official launch. It is tragic. If I can not think before what the circumstances would result, the the configuration will be simply not supported... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 964184] CUPS sends invalid orientation-requested IPP parameter value, producing scaled and shifted printouts
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=964184 http://bugzilla.suse.com/show_bug.cgi?id=964184#c3 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roland_wirth(a)web.de Hardware|x86-64 |All Found By|--- |Community User Flags| |needinfo?(roland_wirth@web. | |de) OS|Other |openSUSE 42.1 --- Comment #3 from Johannes Meixner <jsmeix(a)suse.com> --- Roland Wirth, when you copy the original file as is (i.e. unchanged) from your workstation to the print server machine and then print the original file directly on the print server machine via command line like lp -d xerox_2ndfloor -o fit-to-page <file_name> does it then print out as you expect (without your pstops wrapper workaround) ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 431221] zypper should add $root in any case
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=431221 http://bugzilla.suse.com/show_bug.cgi?id=431221#c7 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #7 from Michael Andres <ma(a)suse.com> --- The current policy works fine for many years now; we won't change it. If there's actually a use-/business case, please enter a feature request at https://fate.opensuse.org/. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 964548] VUL-1: KDE lockscreen bypass by switching display off and on
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

http://bugzilla.opensuse.org/show_bug.cgi?id=964548 http://bugzilla.opensuse.org/show_bug.cgi?id=964548#c5 Martin Gräßlin <kde(a)martin-graesslin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kde(a)martin-graesslin.com --- Comment #5 from Martin Gräßlin <kde(a)martin-graesslin.com> --- Upstream maintainer speaking. >From the xsession output it looks like the lockscreen successfully exited. It prints "Grab Released" which is in method void KSldApp::doUnlock() which is called from three places: 1) If the kscreenlocker_greet failed to start. This would print an error message "Greeter Process not available" which is not in the log 2) If logind send the Unlock dbus signal 3) If kscreenlocker_greet exits with exit code 0. This can happen after grace time (given description not the case), after logind Unlock or - the normal case - after the password was accepted successfully. Given the information in the bug report I can exclude case 1), consider case 2) unlikely and am sure that the condition grace time of number 3) is not the case. So I assume we found a new way to exit kscreenlocker_greet successfully. My gut feeling tells me it's related to Qt's utterly broken multi screen handling including crashes when screens are turned off (see "requesting unexisting screen 0" in log). But to figure that out we would need the debug output of kscreenlocker_greet which is only available since http://commits.kde.org/kscreenlocker/a68dda3dd2a8a60e7f03beb5f0e652ef10fedb… So we need to manually try that. @Dirk: can you please try to run: 1) run "kscreenlocker_greet --testing" from a konsole 2) turn off the display Afterwards please tell us whether the application exited or not. If it did, please add the debug output from the konsole. Please note that kscreenlocker_greet is installed into the libexec directory and is not in $PATH. Unfortunately I do not know where openSUSE installs that file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0