November 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1155693] Yast2 fails to open the system - network settings module
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155693 http://bugzilla.suse.com/show_bug.cgi?id=1155693#c4 Knut Alejandro Anderssen González <knut.anderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mizban(a)web.de) --- Comment #4 from Knut Alejandro Anderssen González <knut.anderssen(a)suse.com> --- (In reply to Knut Alejandro Anderssen González from comment #3) > (In reply to Michael Izban from comment #1) > > Hi, > > > > I have nearly the same problem with my Tumbleweed. > > > > Starting the Yast2-network-configuration-modul stops at "Reading > > Device-Configuration" (i don't know the exact english error-description, as > > i'm German) with the error > > We have refactored yast2-network recently and seems some configuration is > not handled correctly at all. > > Although the title of the bug fits with our problem, the reason is > different, in this case some problem reading the current udev rules in the > system, I will check it but maybe we should move it to a separate bug. > > > > > > > Internal error. Please report a bug report with logs. > > Run save_y2logs to get complete logs. > > > > Caller: /usr/share/YaST2/lib/y2network/udev_rule.rb:232:in `block in > > part_by_key' > > > > Details: undefined method `key' for nil:NilClass > > > > > > > > > > A Reinstallation of the Yast-modules and finally a "zypper -dup" didn't help. > > > > I've no idea, where to search. > > Still have to check logs for knowing exactly what is wrong but at least from > what you have pasted it seems related to udev rules as already commented > previously And for that need logs :) so, please attach as described in: https://en.opensuse.org/openSUSE:Report_a_YaST_bug Even better if already reported as a separate bug. > > > > > Bye > > Michael -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155151] OpenVPN: Unit dbus-org.freedesktop.resolve1.service not found
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155151 Stephan Kulow <coolo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo(a)suse.com Assignee|bnc-team-screening(a)forge.pr |max(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155691] AUDIT-0: slack: home:giovanism/slack: setuid binary whitelisting request for chrome-sandbox
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

1 0

[Bug 1155691] AUDIT-0: home:giovanism:slack: setuid binary whitelisting request
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155691 http://bugzilla.suse.com/show_bug.cgi?id=1155691#c3 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.gerstner(a)suse.com --- Comment #3 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Thank you for opening the bug! (In reply to giovanmail(a)gmail.com from comment #2) > (In reply to Johannes Segitz from comment #1) > > do you intend to submit this to openSUSE? rpmlint will (soonish) ignore such > > issues in home directories, so if this for your own use nothing needs to be > > done here and it should solve itself > > When do I expect this change to take effect? There is no fixed date we can give you yet but it's probably a few weeks. Us actually reviewing the code would also take a while, however. Do you have plans to forward this package to openSUSE:Factory? The chrome-sandbox you package here is actually already packaged in the chromium package. What is the background of that? Could you probably use just the chrome-sandbox from the chromium package? Then no review would be necessary at all. Having the same setuid binary twice in the distribution would be rather unfortunate anyways. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155151] OpenVPN: Unit dbus-org.freedesktop.resolve1.service not found
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155151 Reinhard Max <max(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|max(a)suse.com |bnc-team-screening(a)forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155639] 'yast2 lan' tool does not store WIRELESS_WPA_PSK credentials in the WLAN wireless configuration file
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155639 http://bugzilla.suse.com/show_bug.cgi?id=1155639#c1 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com Flags| |needinfo?(soocki(a)mailbox.or | |g) --- Comment #1 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Sebastian Makowiecki from comment #0) > Fresh Tumbleweed install, when trying to establish connection to a WPA-PSK > protected WLAN network the 'yast2 lan' tool exits silently, the wireless > interface stays down with no apparent effect. The only symptom/indication > (besides the lack of connection) of the things not going right is the error > of the wicked systemd service in the form of ’WIRELESS_WPA_PSK value not > specified'. > > The solution/workaround is to manually add the WIRELESS_WPA_PSK='passphrase' > line to the wireless interface wicked configuration file at > '/etc/sysconfig/network/ifcfg-wlp4s0' followed by the restart of thw wicked > systemd service. If at any time after that the 'yast2 lan' tool is used > again the line disappears from the file and the procedure need to be > repeated. > > This issue was briefly discussed in the forum at: > > https://forums.opensuse.org/showthread.php/538061-Wicked-can-t-connect-WLAN- > WIRELESS_WPA_PSK-value-not-specified-systemd-wicked-unit-error?p=2918607 Thanks for report. Can you please attach your yast logs? (output of save_y2logs ) It will help us to point to specific part of code responsible for it. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 950955] New: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=950955 Bug ID: 950955 Summary: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Jan.Hebler(a)Kabeldeutschland.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rtkit-daemon produces the following Error-Messages: ... Okt 19 07:06:19 tablette rtkit-daemon[3051]: Failed to make ourselves RT: Operation not permitted ... If i understand Lennart Poettering here https://bugzilla.redhat.com/show_bug.cgi?id=1229700 correct, the Kernel-Option CONFIG_RT_GROUP_SCHED should turned off. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1155462] xdg-terminal broken because kreadconfig is not found
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

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

1 0

[Bug 1155108] Tumbleweed OpenMP Programs Compiled With clang9 and libomp9-devel Receive SEGV During Exit Processing
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155108 http://bugzilla.suse.com/show_bug.cgi?id=1155108#c9 --- Comment #9 from Aaron Puchert <aaronpuchert(a)alice-dsl.net> --- The fix seems to work, I've opened a submit request to Factory: https://build.opensuse.org/request/show/745131. If you want, you can already try out the binaries from devel:tools:compiler (as soon as it's done building). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155243] [Build 509.3] openQA test fails in install_otherDE_pattern - most of lxqt package build failed in Leap 15.2
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155243 http://bugzilla.suse.com/show_bug.cgi?id=1155243#c2 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Michael Vetter <mvetter(a)suse.com> --- I started to look at it, and the fixes are fairly easy. SR#744996 to openSUSE:Leap:15.2/liblxqt SR#744997 to openSUSE:Leap:15.2/lxqt-about SR#745004 to openSUSE:Leap:15.2/lxqt-config SR#745006 to openSUSE:Leap:15.2/lxqt-globalkeys SR#745008 to openSUSE:Leap:15.2/lxqt-notificationd SR#745009 to openSUSE:Leap:15.2/lxqt-panel SR#745010 to openSUSE:Leap:15.2/lxqt-policykit SR#745011 to openSUSE:Leap:15.2/lxqt-powermanagement SR#745129 to openSUSE:Leap:15.2/lxqt-session SR#745132 to openSUSE:Leap:15.2/lxqt-runner Have to wait for the build to settle so I can see which other ones still fail. -- You are receiving this mail because: You are on the CC list for the bug.

1 0