May 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185232] something has gone seriously wrong: shim_init() - system does not boot anymore after installing today's updates
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185232 https://bugzilla.suse.com/show_bug.cgi?id=1185232#c35 --- Comment #35 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- (In reply to Andrei Borzenkov from comment #34) > > Is validation by shim disabled? "mokutil --sb-state". > > https://github.com/rhboot/shim/pull/362 It is apparently not limited to only this condition. https://bugzilla.redhat.com/show_bug.cgi?id=1938630 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185232] something has gone seriously wrong: shim_init() - system does not boot anymore after installing today's updates
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185232 https://bugzilla.suse.com/show_bug.cgi?id=1185232#c34 --- Comment #34 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- (In reply to Adrian Fowle from comment #33) > Something went wrong when I rebooted after an upgrade earlier in the week > and I received a message that the (installed) system could not be verified > and that the system would be halted. Is validation by shim disabled? "mokutil --sb-state". https://github.com/rhboot/shim/pull/362 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185535] New: kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 0
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185535 Bug ID: 1185535 Summary: kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During boot the following message appeared (Lenovo ThinkPad E15 2ng gen. with AMD Ryzen 7 4700U): May 02 14:35:33 localhost kernel: snd_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002) May 02 14:35:33 localhost kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 0 Hardware: Model: "ATI Audio device" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1637 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x507f Driver: "snd_hda_intel" Hardware Class: sound Model: "AMD Family 17h (Models 10h-1fh) HD Audio Controller" Vendor: pci 0x1022 "AMD" Device: pci 0x15e3 "Family 17h (Models 10h-1fh) HD Audio Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x507f Driver: "snd_hda_intel" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1185537] New: memory or memorycontroller (EDAC) seems to be detected multiple times
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185537 Bug ID: 1185537 Summary: memory or memorycontroller (EDAC) seems to be detected multiple times Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When booting a Lenovo ThinkPad E15 gen 2 with AMD Ryzen 7 mobile 4700U CPU, it seems that EDAC and RAM are detected multiple times: # journalctl -b |grep "kernel: EDAC" May 02 14:35:14 localhost kernel: EDAC MC: Ver: 3.0.0 May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 02 14:35:34 localhost kernel: EDAC amd64: F17h_M60h detected (node 0). May 02 14:35:34 localhost kernel: EDAC MC: UMC0 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC MC: UMC1 chip selects: May 02 14:35:34 localhost kernel: EDAC amd64: MC: 0: 8192MB 1: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: MC: 2: 0MB 3: 0MB May 02 14:35:34 localhost kernel: EDAC amd64: using x4 syndromes. May 02 14:35:34 localhost kernel: EDAC amd64: Node 0: DRAM ECC disabled. May 02 14:35:34 localhost kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. The machine definitely has only 16GB RAM, even if detected multiple times ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1177223] New: Tumbleweed KDE mult-user functions no longer available, no option to "switch user" from login screen or application menu.
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177223 Bug ID: 1177223 Summary: Tumbleweed KDE mult-user functions no longer available, no option to "switch user" from login screen or application menu. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: emailej(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suddenly the options for switching between multiple users s no longer available. With normal behavior on a multi-user system if a user logs in and then locks session there would be an option to start addition user session at the login screen. Now the current user with locked session is the only option to log back in. Also there should be an option application menu like Power/session > Swith User. This is no longer available. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1185524] New: Changing to NetworkManager via Yast Network throws an internal error
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185524 Bug ID: 1185524 Summary: Changing to NetworkManager via Yast Network throws an internal error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: sbmichael(a)tuta.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848939 --> http://bugzilla.opensuse.org/attachment.cgi?id=848939&action=edit y2log I installed current Tumbleweed 20210429 on a laptop and the installer proposed NetworkManager. However, at the end, the installer reported this error (and then defaulted to wicked), which is the same error that is reported if I try to change from wicked to NetworkManager from Yast Network. To my recollection, there was no issue with NetworkManager previous to the latest NetworkManager update (NetworkManager 1.30.4). The output is below and the logs attached. --- Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/lib64/ruby/gems/2.7.0/gems/cfa-1.0.2/lib/cfa/augeas_parser.rb:461:in `report_activity_error!' Details: Augeas serializing error: Failed to match tree under /store/wifi-security { "key-mgmt" = "wpa-psk" } { "auth-alg" = "open" } { "psk" = "xxxxxxxxxxx" } with pattern ( { /[.0-9A-Z_a-z-]+([].0-9@-[_a-z-]+)?/ = /(([^\t\n\r #][^\n\r#]*[^\t\n\r #]|[^\t\n\r #]))?/ } | { /#comment/ = /[^\t\n\r ].*[^\t\n\r ]|[^\t\n\r ]/ } | { })* for /etc/NetworkManager/system-connections/MEONW.nmconnection with lens /usr/share/augeas/lenses/dist/inifile.aug:459.27-460.17: -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1185534] New: kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185534 Bug ID: 1185534 Summary: kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: fs(a)suse.com Found By: --- Blocker: --- There are several syslog messages referring to kernel_lockdown.7, but no such manual page exists: # man 7 kernel_lockdown No manual entry for kernel_lockdown in section 7 I've installed all the obvious manual packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180418] New: distorted sound streaming from ogg123 via bluetooth A2DP (pulseaudio)
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180418 Bug ID: 1180418 Summary: distorted sound streaming from ogg123 via bluetooth A2DP (pulseaudio) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to stream to my bluetooth speakers using bluetooth 4 and A2DP (High Fidelity Playback), I see some odd results: When playing a Vorbis file using og123, the sound on the speaker is distorted and the speed seems too slow. However, playing a WAV file (used to make the Ggg/Vorbis file) using aplay, the sound sounds fine on the speakers. Also if I use GNOME's built-in audio test. When I switch the bluetooth profile to HSP/HFP (Headset Head Unit), ogg123 play the file the correct speed and without distortions (disregarding the poor quality that HSP delivers). It seems ogg123 is outputting via libao to pulseaudio. Some info from pulseaudio: Server Name: pulseaudio Server Version: 13.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: bluez_sink.FC_58_FA_D0_56_F7.a2dp_sink Default Source: bluez_sink.FC_58_FA_D0_56_F7.a2dp_sink.monitor Cookie: f5a6:23f1 Sink #3 State: SUSPENDED Name: bluez_sink.FC_58_FA_D0_56_F7.a2dp_sink Description: Punker Driver: module-bluez5-device.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 25 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: bluez_sink.FC_58_FA_D0_56_F7.a2dp_sink.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY Properties: bluetooth.protocol = "a2dp_sink" device.description = "Punker" device.string = "FC:58:FA:D0:56:F7" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_FC_58_FA_D0_56_F7" bluez.class = "0x240414" bluez.alias = "Punker" device.icon_name = "audio-speakers-bluetooth" Ports: speaker-output: Lautsprecher (priority: 0) Active Port: speaker-output Formats: pcm Example output from ogg123: > ogg123 -d pulse Vi-CC-RT.ogg Audio Device: PulseAudio Output Playing: Vi-CC-RT.ogg Ogg Vorbis stream: 2 channel, 44100 Hz Changes made to default system in /etc/pulse/system.pa: ### Bluetooth .ifexists module-bluetooth-policy.so load-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1171506] Update nautilus from 3.34.2 to 3.34.3 in GNOME:STABLE:3.34.
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1171506 https://bugzilla.suse.com/show_bug.cgi?id=1171506#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2021:0652-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1171506,1185026 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): nautilus-3.34.3-lp152.3.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1139927] [Build 20190630] openQA test fails in tk on qemu graphics adapter "std", text string "Hello World: Tcl/Tk" does not show up
by bugzilla_noreply＠suse.com 02 May '21

02 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1139927 https://bugzilla.suse.com/show_bug.cgi?id=1139927#c18 --- Comment #18 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: toolkits https://openqa.opensuse.org/tests/1715717 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0