March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1017272] SELinux policy files missing in distribution
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1017272 http://bugzilla.suse.com/show_bug.cgi?id=1017272#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-OU-2018:0598-1: An update that has one optional fix can now be installed. Category: optional (low) Bug References: 1017272 CVE References: Sources used: openSUSE Leap 42.3 (src): selinux-policy-20140730-2.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1083835] clusterssh doc generation is racy
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1083835 http://bugzilla.suse.com/show_bug.cgi?id=1083835#c2 --- Comment #2 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1083835) was mentioned in https://build.opensuse.org/request/show/582218 Factory / clusterssh -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907387] New: nut systemd service file (nut-driver.service) has wrong ExecStart/Stop entry.
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=907387 Bug ID: 907387 Summary: nut systemd service file (nut-driver.service) has wrong ExecStart/Stop entry. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ivar_nikolaisen(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: The nut-driver service file (/usr/lib/systemd/system/nut-driver.service) does not work because the service file is incorrect. It currently has the following settings under [Service]: ExecStart=/upsdrvctl start ExecStop=/upsdrvctl stop These are obviously not correct full paths to the upsdrvctl executable. On my machine, I have found the executable located at /usr/lib/ups/driver/upsdrvctl, and nut seems to work correctly if I change to this path (that is, after doing systemctl start nut-server.service, my UPS is identified correctly and I can query it using the upsc utility). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1081426] designer-qt5 incompatible with kdesignerplugin
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1081426 http://bugzilla.opensuse.org/show_bug.cgi?id=1081426#c5 --- Comment #5 from Wolfgang Bauer <wbauer(a)tmo.at> --- (In reply to Abdel-Rahman A. from comment #3) > Created attachment 762591 [details] > Crash backtrace (by konqi) That crash is in QtWebKit, rather unrelated to kdesignerplugin IMHO. Is your system fully up-to-date? A new QtWebKit update has been released today which contains a crash fix that looks related to your backtrace: - Add fix-nullptr-crash-in-QWebPage-selectedHtml-when-selectedRange.patch * Fix crash in QWebPage::selectedHtml() when selectedRange is nullptr Your crash is in fact in QWebPage::selectedHtml()... Thread 1 (Thread 0x7ffaa02d0780 (LWP 13615)): [KCrash Handler] #6 0x00007ffa70a6520b in () at /usr/lib64/libQt5WebKit.so.5 #7 0x00007ffa70aa6da7 in () at /usr/lib64/libQt5WebKit.so.5 #8 0x00007ffa6fd90969 in QWebPageAdapter::selectedHtml() const () at /usr/lib64/libQt5WebKit.so.5 <============================= #9 0x00007ffa72c1a82e in QWebPage::selectedHtml() const () at /usr/lib64/libQt5WebKitWidgets.so.5 #10 0x00007ffa72c22525 in QWebView::selectedHtml() const () at /usr/lib64/libQt5WebKitWidgets.so.5 #11 0x00007ffa72c22b1e in () at /usr/lib64/libQt5WebKitWidgets.so.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1081426] designer-qt5 incompatible with kdesignerplugin
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1081426 http://bugzilla.opensuse.org/show_bug.cgi?id=1081426#c4 --- Comment #4 from Abdel-Rahman A. <abogical(a)gmail.com> --- Bug occurs with Tumbleweed packages. I've attached the backtrace generated by konqi, if that helps. Information for package libqt5-qttools: --------------------------------------- Repository : openSUSE:Tumbleweed Name : libqt5-qttools Version : 5.10.0-1.1 Arch : x86_64 Vendor : openSUSE Information for package kdesignerplugin: ---------------------------------------- Repository : openSUSE:Tumbleweed Name : kdesignerplugin Version : 5.43.0-1.1 Arch : x86_64 Vendor : openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1081426] designer-qt5 incompatible with kdesignerplugin
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1081426 http://bugzilla.opensuse.org/show_bug.cgi?id=1081426#c3 --- Comment #3 from Abdel-Rahman A. <abogical(a)gmail.com> --- Created attachment 762591 --> http://bugzilla.opensuse.org/attachment.cgi?id=762591&action=edit Crash backtrace (by konqi) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017272] SELinux policy files missing in distribution
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

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

1 0

[Bug 1052437] Pulseaudio not shutting down properly after logging out
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

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

1 0

[Bug 1083413] VUL-0: CVE-2017-18197: jgraphx: XML External Entity (XXE) not prevented
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

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

1 0

[Bug 1083836] New: Combination of 4.4.116+ kernel with older KMP makes user-space crashing
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1083836 Bug ID: 1083836 Summary: Combination of 4.4.116+ kernel with older KMP makes user-space crashing Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When an old KMP is used together with the recent Leap 42.3 kernel (4.4.116 and later) leads to the unexpected crash of user-space. Typically, this is seen with drm-kmp (build-base on 42.3 GM) and the newer kernel (4.4.116-1.g1719d92 and later). The machine appears like crashing as X stops working and user loses the control (no keyboard control back to VT any longer). The bisection pointed to the patches: patches.suse/x86-entry-64-separate-cpu_current_top_of_stack-from-tss-sp0.patch patches.suse/x86-entry-64-use-a-per-cpu-trampoline-stack.patch And, reverting these two patches from the latest 42.3 KOTD fixes the problem. Actually, only reverting the latter patch patches.suse/x86-entry-64-use-a-per-cpu-trampoline-stack.patch seems enough. One more thing to be noted is that, if you rebuild the same KMP with the latest kernel and use it with the new kernel, the bug doesn't appear. The bug manifests only with the combination of old KMP and new kernel. We'll need to rebuild KMPs in anyway for addressing spectre v2 issues, so practically seen, it can be avoided by updating both kernel and KMPs at the same time. But still user may hit the issues with 3rd party KMPs that won't be synced with the kernel update. -- You are receiving this mail because: You are on the CC list for the bug.

1 1