July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189592] yast2 ncurses stage2 shares console with systemd messages
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1189592 https://bugzilla.suse.com/show_bug.cgi?id=1189592#c4 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- There is no way to know when systemd will be quiet; it (or even other processes) might decide to write to the system console at any time, even after the boot process is finished. Yes, this is annoying; I reported something even more severe many years ago as bug #941106 (which is STILL not fixed; it was only pushed aside). But if we are to use the YaST NCurses UI (the text mode), the only thing that makes sense to do it on the tty that is immediately visible after rebooting; and that is tty1, which is also the system console. If we tried to start YaST on, say, tty2 or tty3, how would a user sitting at the console know when and how to switch to that tty? Even if we'd write a message to the console ("Please switch to tty2 with Alt-F2"), that would easily get ignored, and if syslog messages keep flooding the screen, it would also just scroll away. Automatically switching to tty2 would be just as antisocial and user-unfriendly as what I experienced in bug #941106: A user trying to log in or just trying to read the messages would be just thrown off in the middle of what he is doing. Not a good alternative. Having said that, there aren't that many options. If your installation process requires a second stage or a firstboot workflow and the Qt (graphical) YaST UI which does not have this problem is not available, there is still manually refreshing the NCurses UI screen with Ctrl-L. If it's just one or two messages, that is a quick and easy fix. If a runaway process that keeps respawning keeps spamming the console, this obviously doesn't work; but in that case, that is a more serious problem than the firstboot workflow because that constant respawn will keep the machine very busy, so it should be fixed first. I don't think there is anything better than we can do here. Sorry. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227339] New: Crash after starting the aeon installation, mount issue?
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227339 Bug ID: 1227339 Summary: Crash after starting the aeon installation, mount issue? Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: i686 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: geo.kocheril(a)uos.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0 Build Identifier: Trying a fresh Aeon install on a laptop (thinkpad ryzen7), secure boot enabled. Booting with usb stick was ok, after choosing the "install now" crashes with error "Command /usr/bin/mount -o compress=zstd:1, subvol=/@/home /dev/dm-6 /var/lib/tik/mig/mt FAILED" tried it several times, reproducible error. Reproducible: Always Steps to Reproduce: 1.start from usb stick aeon rc2 2. start "install now", choos not to decrypt/import old user data on disk 3.crashes with mnt error, see above Actual Results: crash, installation aborted. Expected Results: installation finished laptop is running Vanilla OS beta. i do have tik.log -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227339] Crash after starting the aeon installation, mount issue?
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227339 https://bugzilla.suse.com/show_bug.cgi?id=1227339#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |geo.kocheril(a)uos.de Flags| |needinfo?(geo.kocheril@uos. | |de) --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- can you please provide the tik.log as suggested in the error message you recieved when the install errored It's on the ignition partition of the USB stick -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1012883] System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30)
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1012883 Peer FRANK <peer.frank(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peer.frank(a)web.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227313] /usr/etc/X11/xinit/xinitrc.common leaves behind zombie nvidia-settings process
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227313 https://bugzilla.suse.com/show_bug.cgi?id=1227313#c2 --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- Also, possibly there is some error message with your config file. So try this on a working nvidia desktop. nvidia-settings --load-config-only nvidia-settings --load-config-only & Any error message? Or just works? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227313] /usr/etc/X11/xinit/xinitrc.common leaves behind zombie nvidia-settings process
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227313 https://bugzilla.suse.com/show_bug.cgi?id=1227313#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(alanas.00(a)mail.ru | |) Assignee|gfx-bugs(a)suse.de |sndirsch(a)suse.com CC| |alanas.00(a)mail.ru Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- I no longer can remember why I put this process in the background. It's so long ago I added this to xinit startup process, that I no longer can find the changelog for it. :-( Could you try without putting the nvdia-settings process in the background, i.e. remove the '&' a the end: # # Load nvidia settings # if test -r $HOME/.nvidia-settings-rc && type -p nvidia-settings > /dev/null ; then nvidia-settings --load-config-only > /dev/null 2>&1 fi -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227327] New: "splash" parameter missing in pxe boot
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227327 Bug ID: 1227327 Summary: "splash" parameter missing in pxe boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: karl.vandenbogaert(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- when installing through PXE boot, the "splash" kernel parameter is missing in /etc/default/grub regarding installing from the iso. the problem was already present in Leap 15.5 and still present in 15.6 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226497] No boot from software RAID after upgrade to 15.6 on Supermicro H12DSi-NT6
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226497 https://bugzilla.suse.com/show_bug.cgi?id=1226497#c2 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(georg.pfuetzenreu | |ter(a)suse.com) CC| |georg.pfuetzenreuter(a)suse.c | |om, mchang(a)suse.com --- Comment #2 from Michael Chang <mchang(a)suse.com> --- Hi Georg, As far as I can tell, there are no major changes in how grub handles software RAID in version 2.12. It should not fail like that when encountering a problem. Normally, a failed root device access should drop you into a rescue shell, providing some information for troubleshooting. This makes me suspect that the issue might not be specific to software RAID. Instead, it could be a new regression in version 2.12 caused by the newly introduced bli module, which may also render the screen black indefinitely. [1] Please check if this is the case by disabling 25_bli in grub.cfg. Follow these steps after updating to grub 2.12: > 1. chmod -x /etc/grub.d/25_bli > 2. grub2-mkconfig -o /boot/grub2/grub.cfg Ensure that the following section is completely **removed** from the resulting grub.cfg: > ### BEGIN /etc/grub.d/25_bli ### > if [ "$grub_platform" = "efi" ]; then > insmod bli > fi > ### END /etc/grub.d/25_bli ### Finally, reboot and check if it makes any difference? [1] https://mail.gnu.org/archive/html/grub-devel/2023-07/msg00077.html Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084909] trackerbug: packages do not build reproducibly from hostname
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1084909 https://bugzilla.suse.com/show_bug.cgi?id=1084909#c56 --- Comment #56 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:2289-1: An update that has three fixes can now be installed. Category: recommended (important) Bug References: 1084909, 1222218, 1224179 Maintenance Incident: [SUSE:Maintenance:33968](https://smelt.suse.de/incident/33968/) Sources used: openSUSE Leap 15.6 (src): qemu-linux-user-8.2.4-150600.3.3.1, qemu-8.2.4-150600.3.3.1 Basesystem Module 15-SP6 (src): qemu-8.2.4-150600.3.3.1 SUSE Package Hub 15 15-SP6 (src): qemu-linux-user-8.2.4-150600.3.3.1, qemu-8.2.4-150600.3.3.1 Server Applications Module 15-SP6 (src): qemu-8.2.4-150600.3.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227174] VUL-0: CVE-2024-39705: python-nltk: remote code execution through the integrated data package download functionality
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227174 https://bugzilla.suse.com/show_bug.cgi?id=1227174#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1227174) was mentioned in https://build.opensuse.org/request/show/1185062 Factory / python-nltk -- You are receiving this mail because: You are on the CC list for the bug.

1 0