October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1232567] With Firefox 132 cannot download files - firefox is from mozilla repo
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232567 https://bugzilla.suse.com/show_bug.cgi?id=1232567#c12 --- Comment #12 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Wolfgang Rosenauer from comment #11) > I'm not even using KDE which was one of the confusing things because the > patches should not do anything on non-KDE desktops. > But I think here were more people with issues not running KDE. At least in > the ml thread there were reports from Gnome. So, what are these KDE patches about and where do they come from? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232567] With Firefox 132 cannot download files - firefox is from mozilla repo
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232567 https://bugzilla.suse.com/show_bug.cgi?id=1232567#c11 --- Comment #11 from Wolfgang Rosenauer <wolfgang(a)rosenauer.org> --- I'm not even using KDE which was one of the confusing things because the patches should not do anything on non-KDE desktops. But I think here were more people with issues not running KDE. At least in the ml thread there were reports from Gnome. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232292] New: Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232292 Bug ID: 1232292 Summary: Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default, three days on a row. Machine hibernates normally, but on restore, keyboard leds freeze, does not respond. Display shows the frozen screen saver animation. Machine appears frozen. There is nothing saved on the log after the apparently successful hibernation. I am removing this kernel and going back to 5.14.21-150500.55.73-default, but I still have the journal if you are interested. journal entries: Oct 24 02:37:36 Telcontar sudo[20578]: root : TTY=pts/43 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl hibernate Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:36 Telcontar sudo[20578]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. Oct 24 02:37:36 Telcontar ModemManager[1718]: <info> [sleep-monitor] system is about to suspend Oct 24 02:37:36 Telcontar sudo[20578]: pam_unix(sudo:session): session closed for user root Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:36 Telcontar leafnode[19718]: <QUIT Oct 24 02:37:36 Telcontar leafnode[19718]: >205 Always happy to serve! Oct 24 02:37:36 Telcontar dovecot[3429]: [redacted] Oct 24 02:37:36 Telcontar systemd[1]: Reached target Sleep. Oct 24 02:37:36 Telcontar systemd[1]: Starting Hibernate... Oct 24 02:37:36 Telcontar systemd-sleep[20599]: INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate Oct 24 02:37:36 Telcontar systemd-sleep[20599]: INFO: Running prepare-grub .. Oct 24 02:37:36 Telcontar mine-time[20608]: Inside /usr/lib/systemd/system-sleep/mine-time. Params -pre--hibernate-. Oct 24 02:37:36 Telcontar mine-sleep[20609]: Hibernating the system now (pre)... Oct 24 02:37:36 Telcontar systemd-sleep[20606]: service: no such service upsd.service Oct 24 02:37:37 Telcontar systemd-sleep[20599]: running kernel is grub menu entry main-os (vmlinuz-5.14.21-150500.55.83-default) Oct 24 02:37:37 Telcontar systemd-sleep[20599]: preparing boot-loader: selecting entry main-os, kernel /boot/5.14.21-150500.55.83-default Oct 24 02:37:37 Telcontar systemd-sleep[20599]: running /usr/sbin/grub2-once "main-os" Oct 24 02:37:37 Telcontar systemd-sleep[20599]: time needed for sync: 0.0 seconds, time needed for grub: 0.2 seconds. Oct 24 02:37:37 Telcontar systemd-sleep[20599]: INFO: Done. Oct 24 02:37:39 Telcontar xinetd[3425]: EXIT: nntp status=0 duration=392(sec) Oct 24 02:37:39 Telcontar sudo[21410]: root : TTY=pts/43 ; PWD=/root ; USER=root ; COMMAND=/usr/local/sbin/beep Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:39 Telcontar sudo[21410]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. Oct 24 02:37:39 Telcontar sudo[21410]: pam_unix(sudo:session): session closed for user root Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:41 Telcontar systemd-sleep[20593]: Entering sleep state 'hibernate'... Oct 24 02:37:41 Telcontar kernel: PM: hibernation: hibernation entry -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232567] With Firefox 132 cannot download files - firefox is from mozilla repo
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232567 https://bugzilla.suse.com/show_bug.cgi?id=1232567#c10 --- Comment #10 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Wolfgang Rosenauer from comment #9) > I'm still trying to understand what the issue could be. > > I've now built a new release with all patches applied again because I wanted > to have build where I can do more testing. Those builds are not published > but they are in OBS. > > So everyone who wants to help testing and has an OBS account can grab the > version 132.0-7.1 (should not matter if for TW or Leap) and try again. > > Be warned that this is actually the very same patchlevel which broke before > BUT I installed it here on my TW and I CANNOT reproduce the issue anymore. > And that is where I'm lost right now because from code review I do not see a > problem (maybe I miss something) but also cannot reproduce anymore. > Therefore I'm blocked and would be very interested in feedback from others > with this version. I've tried MozillaFirefox-132.0-7.1.x86_64 with TW20241028, and it doesn't work. I'm not sure whether this is relevant, since I don't know the KDE integration patches introduced with Firefox 132: Are you using kmozillahelper? I am using the builtin xdg-desktop-portal integration instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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