May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1099494] New: zypper calls snapper, snapshot creation failed while snapper already running, still stalling system
by bugzilla_noreply＠novell.com 28 Aug '20

28 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1099494 Bug ID: 1099494 Summary: zypper calls snapper, snapshot creation failed while snapper already running, still stalling system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 775554 --> http://bugzilla.suse.com/attachment.cgi?id=775554&action=edit y2logs, snapper.log, system journal, snapper cleanup journal, zypper.log ## Observation On an openSUSE Tumbleweed installation on a HDD disk (btrfs, encrypted, i.e. slow performance) calling zypper dup proposed to install around 3000 packages - as expected for openSUSE Tumbleweed upgrades. During that process it seems snapper cleanup was triggered in parallel but zypper also tried to create a snapshot but failed to do so effectively stalling the system for a very long time. Logfiles show quite some errors. E.g. from zypper.log: ``` 018-06-28 10:54:26 <2> linux-9akz(17693) [PLUGIN] PluginScript.cc(~PluginDumpStderr):75 ! INFO:root:creating post snapshot 2018-06-28 10:54:26 <5> linux-9akz(17693) [zypp] Exception.cc(log):166 PluginExecutor.cc(doSend):133 CAUGHT: Not ready to read within timeout. 2018-06-28 10:54:26 <2> linux-9akz(17693) [zypp::plugin] PluginExecutor.cc(doSend):134 Not ready to read within timeout. 2018-06-28 10:54:26 <2> linux-9akz(17693) [zypp::plugin] PluginExecutor.cc(doSend):140 Bad plugin response from PluginScript[4691] /usr/lib/zypp/plugins/commit/snapper.py: PluginF rame[](0){0} 2018-06-28 10:54:26 <2> linux-9akz(17693) [zypp::plugin] PluginExecutor.cc(doSend):141 (Expected ACK or _ENOMETHOD) 2018-06-28 10:54:26 <1> linux-9akz(17693) [zypp::plugin++] PluginScript.cc(close):229 Close:PluginScript[4691] /usr/lib/zypp/plugins/commit/snapper.py 2018-06-28 10:54:26 <1> linux-9akz(17693) [zypp::plugin++] PluginScript.cc(send):272 PluginScript[4691] /usr/lib/zypp/plugins/commit/snapper.py ->send PluginFrame[_DISCONNECT](0){0} 2018-06-28 10:54:30 <2> linux-9akz(17693) [PLUGIN] PluginScript.cc(~PluginDumpStderr):75 ! ERROR:root:creating snapshot failed: 2018-06-28 10:54:30 <2> linux-9akz(17693) [PLUGIN] PluginScript.cc(~PluginDumpStderr):75 ! ERROR:root: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ``` whereas snapper-cleanup reports ``` 2018-06-28 10:54:03 MIL libsnapper(4747) Snapper.cc(Snapper):91 - Snapper constructor 2018-06-28 10:54:03 MIL libsnapper(4747) Snapper.cc(Snapper):92 - libsnapper version 0.5.4 2018-06-28 10:54:03 MIL libsnapper(4747) Snapper.cc(Snapper):93 - config_name:root disable_filters:false 2018-06-28 10:54:03 MIL libsnapper(4747) AsciiFile.cc(reload):114 - loading file /etc/snapper/configs/root 2018-06-28 10:54:03 MIL libsnapper(4747) AsciiFile.cc(getValue):235 - key:SUBVOLUME value:/ 2018-06-28 10:54:03 MIL libsnapper(4747) AsciiFile.cc(getValue):235 - key:FSTYPE value:btrfs 2018-06-28 10:54:03 MIL libsnapper(4747) AsciiFile.cc(getValue):235 - key:QGROUP value:1/0 2018-06-28 10:54:03 MIL libsnapper(4747) AsciiFile.cc(getValue):235 - key:SYNC_ACL value:no 2018-06-28 10:54:03 MIL libsnapper(4747) Snapper.cc(Snapper):125 - subvolume:/ filesystem:btrfs 2018-06-28 10:54:03 MIL libsnapper(4747) Snapper.cc(loadIgnorePatterns):174 - number of ignore patterns:8 2018-06-28 10:54:03 MIL libsnapper(4747) Snapshot.cc(read):245 - found 16 snapshots 2018-06-28 10:54:03 MIL libsnapper(4747) SystemCmd.cc(SystemCmd):46 - constructor SystemCmd:"/usr/lib/snapper/plugins/grub --refresh" 2018-06-28 10:54:03 MIL libsnapper(4747) SystemCmd.cc(execute):82 - SystemCmd Executing:"/usr/lib/snapper/plugins/grub --refresh" 2018-06-28 10:54:05 MIL libsnapper(4747) SystemCmd.cc(doExecute):267 - stopwatch 1.439245s for "/usr/lib/snapper/plugins/grub --refresh" 2018-06-28 10:54:05 MIL libsnapper(4747) SystemCmd.cc(doExecute):287 - system() Returns:0 2018-06-28 10:54:05 WAR libsnapper(4747) FileUtils.cc(SDir):88 - THROW: open failed path://.snapshots errno:2 (No such file or directory) 2018-06-28 10:55:01 MIL libsnapper(4747) SystemCmd.cc(SystemCmd):46 - constructor SystemCmd:"/usr/lib/snapper/plugins/grub --refresh" 2018-06-28 10:55:01 MIL libsnapper(4747) SystemCmd.cc(execute):82 - SystemCmd Executing:"/usr/lib/snapper/plugins/grub --refresh" 2018-06-28 10:55:03 MIL libsnapper(4747) SystemCmd.cc(doExecute):267 - stopwatch 1.765667s for "/usr/lib/snapper/plugins/grub --refresh" ``` so it looks like snapper was starting up just in before, coincidence? -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1069695] New: virt-manager doesn't grab the pointer correctly
by bugzilla_noreply＠novell.com 27 Aug '20

27 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1069695 Bug ID: 1069695 Summary: virt-manager doesn't grab the pointer correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: adrien.plazas(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt-manager doesn't capture the mouse anymore: when the mouse should be grabbed (because the guest has its own mouse pointer) if I move it too far I see the host's pointer reappearing outside the window, but unfortunately the two pointers don't match and I can't access all the elements on the guest's screen. It may be because I'm using GNOME/Wayland, I didn't check with GNOME/Xorg yet. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1010996] New: With Firefox 50, ISRG X1 CA to ca-certificates-mozilla should be added
by bugzilla_noreply＠novell.com 26 Aug '20

26 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1010996 Bug ID: 1010996 Summary: With Firefox 50, ISRG X1 CA to ca-certificates-mozilla should be added Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of Firefox 50's main feature is the inclusion of the ISRG Root X1 CA certificate. This is not reflected in Leap. ca-certificates-mozilla in all distributions, including Tumbleweed and Leap, is still 2.7 from March. Please include ISRG Root X1. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 937020] New: pdfcsplain ommits czech characters
by bugzilla_noreply＠novell.com 26 Aug '20

26 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=937020 Bug ID: 937020 Summary: pdfcsplain ommits czech characters Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.jakl(a)qbicon.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36 Build Identifier: pdfcsplain from texlive ommits czech characters from resulting pdf document. At first it complained that there are some files generated with pdftex, so I've run sudo fmtutil --all, after that it works, but results are not correct. Reproducible: Always Steps to Reproduce: 1. install texlive 2. run 'sudo fmtutil --all' 3. run pdfcsplain test.tex 4. compare resulting pdf with test-13.2.pdf -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1080430] New: Mono console applications don't work with the update to terminfo 6.1
by bugzilla_noreply＠novell.com 25 Aug '20

25 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1080430 Bug ID: 1080430 Summary: Mono console applications don't work with the update to terminfo 6.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono Assignee: bnc-team-mono(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update of terminfo to 6.1, running console applications with mono doens't work anymore: ----------------------------------------------------- mono UnSIN.exe Unhandled Exception: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoDriver..ctor (System.String term) [0x00055] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver..cctor () [0x0004d] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <8f8a76535f644930b25f735cdc17065c>:0 at System.Console..cctor () [0x0008e] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at UnSIN.Program.Main (System.String[] args) [0x00006] in <7c4247c4deca4ba5a7657dbbe6ac76e0>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoDriver..ctor (System.String term) [0x00055] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver..cctor () [0x0004d] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <8f8a76535f644930b25f735cdc17065c>:0 at System.Console..cctor () [0x0008e] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at UnSIN.Program.Main (System.String[] args) [0x00006] in <7c4247c4deca4ba5a7657dbbe6ac76e0>:0 ----------------------------------------------------- My TERM is set to screen-256color, changing it to xterm fixed it. ----------------------------------------------------- TERM=xterm mono UnSIN.exe ERROR: Invalid parameters! ----------------------------------------------------- libslang2 seems to have had a similar issue see: https://build.opensuse.org/request/show/574532 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1136634] New: openSUSE matplotlib generates no graph
by bugzilla_noreply＠novell.com 20 Aug '20

20 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1136634 Bug ID: 1136634 Summary: openSUSE matplotlib generates no graph Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mhenatsch(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0 Build Identifier: I have written a Python program to generate a graphical representation of temperatures over time. The program runs correctly under Raspbian and also under Manjaro. Under both systems it generates the desired graph. Not so under openSUSE - neither under Leap 42.3 nor under Leap 15.0. It throws no exceptions and correctly prints out text, but no graph. The c ode is exactly the same as in the two other operating systems. I had installed matplotlib through Yast from the openSUSE repositories. Examining in Yast the "Technical Data" for matplotlib I found the following: License: SUSE-Matplotlib Vendor: openSUSE Packager: http://bugs.opensuse.org >From this I concluded that the openSUSE-version of matplotlib is non-standard. I uninstalled (with Yast) matplotlib and reinstalled it from the command line with "pip3 install matplotlib". This got me the original version and since then everything runs well, including the generation of graphs. Reproducible: Always Steps to Reproduce: 1.Create a Python program ending with the following code: plt.plot(timeslist, temperatureslist) plt.ylabel('Temperature [° C]') print(plt.ylabel) plt.xlabel('Time (Date and Time)') print(plt.xlabel) plt.title(timespan, fontsize=16, color='blue') plt.grid(True) plt.show() 2.Run the program. All goes well, except the generation of the graph. 3.Uninstall the SUSE-version of matplotlib and reinstall the library with "pip3 install matplotlb". Run the Python program again. You will see a nice graph! -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1095041] New: python3-botocore: :'AWSHTTPSConnection' object has no attribute 'ssl_context'
by bugzilla_noreply＠novell.com 19 Aug '20

19 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1095041 Bug ID: 1095041 Summary: python3-botocore: :'AWSHTTPSConnection' object has no attribute 'ssl_context' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Problem: > mwilck@apollon:~> aws ec2 describe-instances > > 'AWSHTTPSConnection' object has no attribute 'ssl_context' See https://github.com/boto/botocore/issues/1258 According to https://github.com/boto/botocore/issues/1258#issuecomment-323469132, this is caused by the packaged botocore replacing the vendor-supplied "requests" module with the official release. I've verified this in OBS project home:mwilck:branches:devel:languages:python:aws. Upgrading to the latest botocore version 1.10.28 does not fix the issue unless the code in the spec file that replaces the botocore-shipped requests module with the official requests module is removed. Unfortunately, it's impossible to directly upgrade to the thus modified python3-botocore package, because rpm detects file conflicts caused by the %{$python_sitelib}/requests %{buildroot}%{$python_sitelib}/botocore/vendored/requests symlink in the current package. -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1135353] New: Update spdlog-devel to 1.3.1
by bugzilla_noreply＠novell.com 18 Aug '20

18 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135353 Bug ID: 1135353 Summary: Update spdlog-devel to 1.3.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dieter-ries(a)student.ethz.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The spdlog logging library (https://github.com/gabime/spdlog) has seen quite a few releases in the last 2 years (https://github.com/gabime/spdlog/releases) including the 1.0 major release, bringing many new features, including custom log formatting etc. spdlog-devel-1.3.1 is already in tumbleweed, and also works on leap-15.1 from the devel:libraries:c_c++ project (https://build.opensuse.org/package/show/devel:libraries:c_c++/spdlog) Having up-to-date versions of spdlog-devel in Leap-15.1 at some point would be great! Cheers, D -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1006973] New: terminfo setting 'rxvt-unicode-256color' in /etc/DIR_COLORS is missing
by bugzilla_noreply＠novell.com 18 Aug '20

18 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1006973 Bug ID: 1006973 Summary: terminfo setting 'rxvt-unicode-256color' in /etc/DIR_COLORS is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: wnereiz(a)eienteiland.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- (For both openSUSE Leap 42.1 and Tumbleweed) There is rxvt-unicode setting there in /etc/DIR_COLORS currently: #Below, there should be one TERM entry for each termtype that is colorizable ... TERM rxvt-unicode ... It's not working for 256color: $ echo $TERM rxvt-unicode-256color $ dircolors -b /etc/DIR_COLORS LS_COLORS=''; export LS_COLORS The ls command output results without any colors in rxvt-unicode terminal. Try to add 'rxvt-unicode-256color': ... TERM rxvt-unicode TERM rxvt-unicode-256color ... Then it works, and colors come back. I'm not sure if 'rxvt-16color', 'rxvt-88color' and 'rxvt-256color' need to be added, because I'm using rxvt-unicode only. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 968600] New: Journal is being flooded with "'/usr/sbin/crda' failed with exit code 255" errors
by bugzilla_noreply＠novell.com 17 Aug '20

17 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=968600 Bug ID: 968600 Summary: Journal is being flooded with "'/usr/sbin/crda' failed with exit code 255" errors Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alex.richardson(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I get these messages every few seconds: Feb 28 19:35:55 Alex-laptop systemd-udevd[15510]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:35:58 Alex-laptop systemd-udevd[15513]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:35:58 Alex-laptop kernel: cfg80211: World regulatory domain updated: Feb 28 19:35:58 Alex-laptop kernel: cfg80211: DFS Master region: unset Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Feb 28 19:36:01 Alex-laptop systemd-udevd[15516]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:36:01 Alex-laptop kernel: cfg80211: World regulatory domain updated: Feb 28 19:36:01 Alex-laptop kernel: cfg80211: DFS Master region: unset Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Feb 28 19:36:05 Alex-laptop systemd-udevd[15519]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:36:05 Alex-laptop kernel: cfg80211: World regulatory domain updated: Feb 28 19:36:05 Alex-laptop kernel: cfg80211: DFS Master region: unset Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Running crda manually also doesn't seem to work: # COUNTRY=GB crda Failed to set regulatory domain: -7 Alex-laptop:~ # echo $? 249 It seems to be an informational message, but it hides all useful output for me, for now I just commented the line KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/sbin/crda" in /usr/lib/udev/rules.d/85-regulatory.rules. I don't know if this can cause any problem, but so far wireless seems to still work. The only other related thing I have found is https://bugzilla.suse.com/show_bug.cgi?id=937756 but that seems to be fixed and https://github.com/systemd/systemd/issues/922 which seems to be a different issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 2