October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1232702] New: Docker does not start properly after upgrade from TW 20241023 to 20241028
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232702 Bug ID: 1232702 Summary: Docker does not start properly after upgrade from TW 20241023 to 20241028 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading from Tumbleweed 20241023 to 20241028 this morning, docker failed to start its container engine: Oct 31 12:38:51 rpi4b (dockerd)[3994]: docker.service: Referenced but unset environment variable evaluates to an empty string: DOCKER_NETWORK_OPTIONS Editing /etc/sysconfig/docker to add DOCKER_NETWORK_OPTIONS="" corrects the problem, but I'm not sure that's the right way to fix the root problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 https://bugzilla.suse.com/show_bug.cgi?id=1232696#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- To get your system up and running again quickly, you might want to check /etc/sysconfig/bootloader if there are any weird values there. I have: % grep '=' /etc/sysconfig/bootloader LOADER_TYPE="grub2-efi" SECURE_BOOT="yes" TRUSTED_BOOT="no" UPDATE_NVRAM="yes" On my legacy (non-UEFI) boot machine: % grep '=' /etc/sysconfig/bootloader LOADER_TYPE="grub2" SECURE_BOOT="yes" TRUSTED_BOOT="no" UPDATE_NVRAM="yes" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 https://bugzilla.suse.com/show_bug.cgi?id=1232696#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- I don't know how robust this all is for switching back and forth between Grub2 and systemd-boot. For experimenting with this, it might be a good idea to try it in a VM first (VirtualBox, QEMU) so you can roll back to a previous snapshot if things don't work. In any case, you DID actively switch to systemd-boot, so this did not come out of nowhere. Having said that, I also see 3 "internal errors" in those logs: y2-12-bootloader.log y2-14-bootloader.log y2-17-bootloader.log >> 2024-10-31 15:06:38 <3> altaria(49088) [Ruby] yast/wfm.rb(handle_exception):271 >> Client /usr/share/YaST2/clients/bootloader.rb failed with >> 'undefined method `>=' for nil' (NoMethodError). >> >> Backtrace: >> /usr/share/YaST2/lib/bootloader/systemdboot_widgets.rb:55:in `init' >> /usr/share/YaST2/lib/cwm/abstract_widget.rb:228:in `init_wrapper' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/fun_ref.rb:33:in `call' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/fun_ref.rb:33:in `call' >> /usr/share/YaST2/modules/CWM.rb:327:in `block in initWidgets' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:82:in `block in foreach' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:81:in `each' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:81:in `foreach' >> /usr/share/YaST2/modules/CWM.rb:310:in `initWidgets' >> /usr/share/YaST2/lib/cwm/replace_point.rb:47:in `replace' >> /usr/share/YaST2/lib/cwm/pager.rb:74:in `switch_page' >> /usr/share/YaST2/lib/cwm/pager.rb:52:in `handle' >> /usr/share/YaST2/lib/cwm/abstract_widget.rb:247:in `call' >> /usr/share/YaST2/lib/cwm/abstract_widget.rb:247:in `handle_wrapper' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/fun_ref.rb:33:in `call' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/fun_ref.rb:33:in `call' >> /usr/share/YaST2/modules/CWM.rb:353:in `block in handleWidgets' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:82:in `block in foreach' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:81:in `each' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:81:in `foreach' >> /usr/share/YaST2/modules/CWM.rb:341:in `handleWidgets' >> /usr/share/YaST2/modules/CWM.rb:798:in `Run' >> /usr/share/YaST2/modules/CWM.rb:976:in `ShowAndRun' >> /usr/share/YaST2/modules/CWM.rb:931:in `show' >> /usr/share/YaST2/lib/bootloader/config_dialog.rb:79:in `guarded_run' >> /usr/share/YaST2/lib/bootloader/config_dialog.rb:29:in `run' >> /usr/share/YaST2/lib/bootloader/main_dialog.rb:94:in `block in run_content' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:546:in `eval' >> /usr/share/YaST2/modules/Sequencer.rb:247:in `WS_run' >> /usr/share/YaST2/modules/Sequencer.rb:318:in `block in Run' >> <internal:kernel>:187:in `loop' >> /usr/share/YaST2/modules/Sequencer.rb:310:in `Run' >> /usr/share/YaST2/lib/bootloader/main_dialog.rb:112:in `run_content' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:546:in `call' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/builtins.rb:546:in `eval' >> /usr/share/YaST2/modules/Sequencer.rb:247:in `WS_run' >> /usr/share/YaST2/modules/Sequencer.rb:318:in `block in Run' >> <internal:kernel>:187:in `loop' >> /usr/share/YaST2/modules/Sequencer.rb:310:in `Run' >> /usr/share/YaST2/lib/bootloader/main_dialog.rb:69:in `run' >> /usr/share/YaST2/clients/bootloader.rb:45:in `GuiHandler' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/fun_ref.rb:33:in `call' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/fun_ref.rb:33:in `call' >> /usr/share/YaST2/modules/CommandLine.rb:1569:in `Run' >> /usr/share/YaST2/clients/bootloader.rb:36:in `main' >> /usr/share/YaST2/clients/bootloader.rb:54:in `<top (required)>' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:345:in `eval' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:345:in `run_client' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:206:in `call_builtin' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:206:in `call_builtin_wrapper' >> /usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:195:in `CallFunction' -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 https://bugzilla.suse.com/show_bug.cgi?id=1232696#c4 --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- See also https://en.opensuse.org/Systemd-boot -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 https://bugzilla.suse.com/show_bug.cgi?id=1232696#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- After merging and splitting the logs: >> y2-00-installation.log: 2024-09-28 19:57:52 y2base called with ["installation", "--arg", "initial", "qt", "--noborder", "--auto-fonts", "--fullscreen"] >> y2-01-alternatives.log: 2024-09-28 23:41:26 y2base called with ["alternatives", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-02-host.log: 2024-09-28 23:41:59 y2base called with ["host", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-03-lan.log: 2024-09-28 23:42:27 y2base called with ["lan", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-04-bootloader.log: 2024-09-28 23:42:59 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-05-add-on.log: 2024-09-29 01:02:18 y2base called with ["add-on", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-06-partitioner.log: 2024-09-29 01:02:55 y2base called with ["partitioner", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-07-sw_single.log: 2024-09-29 01:03:01 y2base called with ["sw_single", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-08-repositories.log: 2024-09-30 23:32:10 y2base called with ["repositories", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-09-repositories.log: 2024-10-02 20:31:35 y2base called with ["repositories", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-10-repositories.log: 2024-10-07 18:06:18 y2base called with ["repositories", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-11-sysconfig.log: 2024-10-14 19:45:57 y2base called with ["sysconfig", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-12-bootloader.log: 2024-10-14 22:00:20 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-13-bootloader.log: 2024-10-14 22:00:31 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] ^^^^^^^^^^^^^^^^^^^^ Switched to systemd-boot: >> 2024-10-14 22:00:41 <1> altaria(46195) [Ruby] bootloader/sysconfig.rb(write):106 >> Saving /etc/sysconfig/bootloader for systemd-boot >> y2-14-bootloader.log: 2024-10-31 15:06:31 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-15-bootloader.log: 2024-10-31 15:06:43 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] >> y2-16-bootloader.log: 2024-10-31 15:09:24 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] ^^^^^^^^^^^^^^^^^^^^ Switched to systemd-boot: >> 2024-10-31 15:09:37 <1> altaria(51718) [Ruby] bootloader/sysconfig.rb(write):106 >> Saving /etc/sysconfig/bootloader for systemd-boot Reboot (from your journalctl-b file that is part of the y2logs tarball): >> Oct 31 15:46:47 altaria kernel: >> Linux version 6.11.2-1-default (geeko@buildhost) >> (gcc (SUSE Linux) 14.2.0, GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.43.1.20240828-2) >> #1 SMP PREEMPT_DYNAMIC Fri Oct 4 17:37:58 UTC 2024 (38c846e) >> y2-17-bootloader.log: 2024-10-31 15:10:01 y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 https://bugzilla.suse.com/show_bug.cgi?id=1232696#c2 --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- >> 2024-10-14 22:00:31 <1> altaria(46195) [Ruby] bin/y2start(<main>):22 >> y2base called with ["bootloader", "qt", "-name", "YaST2", "-icon", "yast"] >> >> 2024-10-14 22:00:41 <1> altaria(46195) [Ruby] modules/Package.rb(PackageDialog):315 >> Asking for packages: >> ["kexec-tools", "sdbootutil", "systemd-boot", "shim"] >> >> 2024-10-14 22:00:41 <1> altaria(46195) [Ruby] bootloader/sysconfig.rb(write):106 >> Saving /etc/sysconfig/bootloader for systemd-boot -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232696] YaST2 says im using systemd-boot but im not, crashes
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232696 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232700] New: Bluetooth broken after update: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232700 Bug ID: 1232700 Summary: Bluetooth broken after update: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: missoline(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, After upgrading to the latest snapshot (20241030) I am no longer able to connect to my bluetooth speaker. I have been running tumbleweed for a couple of years now and never had any problem to pair it, but now when I try to connect, get the following error in journalctl: kf.bluezqt: PendingCall Error: "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." oct. 31 14:38:11 localhost.localdomain bluetoothd[1200]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to D4:F5:47:AC:1B:70: Connection refused (111) However when triple checking as I was filing this report, I realized that I am able to connect to other bluetooth devices. This one seems to be the only one no longer working. It was connected when I upgraded to the latest snapshot so maybe something got corrupted in the profile. I'll try to unpair and pair again and will report back. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232699] New: Update neofetch - fastfetch - neowofetch with new Tumbleweed logo
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232699 Bug ID: 1232699 Summary: Update neofetch - fastfetch - neowofetch with new Tumbleweed logo Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epp(a)mcom.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Submitting as Enhancement, not a bug. Update neofetch, fastfetch, neowofetch with the new Tumblweeed logo. -- You are receiving this mail because: You are on the CC list for the bug.

1 0