April 2024 - openSUSE Users - openSUSE Mailing Lists

Plasma panel bug after recent update (Leap)
by gumb 29 Apr '24

29 Apr '24

Leap 15.5, Plasma 5.27.9, x11 A few weeks since I last did updates. Just applied all the current updates and now upon login to Plasma, the default panel doesn't always appear. Logged out and back in again, it was there. Hoped it was a one-off, buggy config update. After another reboot, it took 4 login attempts until I reached a desktop with the panel showing. All the items in the panel are there as per usual, nothing lost, but a PITA and waste of time to get there. Fortunately I often go a week or more without reboots so it won't happen so often. Anybody else has seen this, or knows of a bug or bugfix? I just applied a glut of updates from the last couple of months and didn't see anything particularly Plasma or KDE-related, so it's difficult to pinpoint which package might be responsible. gumb

2 2

plymouth.start.service log entry question.
by -pj 25 Apr '24

25 Apr '24

Hello, I am using openSUSE Tumbleweed 20240421 . I have noticed a log entry concerning 'plymouth.start.service' systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. - Examining the service file shown below: cat plymouth-start.service [Unit] Description=Show Plymouth Boot Screen DefaultDependencies=no Wants=systemd-ask-password-plymouth.path systemd-vconsole-setup.service After=systemd-vconsole-setup.service systemd-udev-trigger.service systemd-udevd.service Before=systemd-ask-password-plymouth.service ConditionKernelCommandLine=!plymouth.enable=0 ConditionVirtualization=!container [Service] ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session ExecStartPost=-/usr/bin/plymouth show-splash Type=forking RemainAfterExit=yes KillMode=none SendSIGKILL=no - Should I file a bug report about this this? There is a previous Bugzilla report filed on 11-06-21 https://bugzilla.opensuse.org/show_bug.cgi?id=1192412 and it has not yet been resolved upstream. What type of KillMode do you recommend for use with this this particular service? "mixed" and "control-group" options are shown above. Are there more options than those available for this situation? Could this be a reason/reasons why sometimes when the machine is shutdown the verbose shutdown messages hang for approximately one minute and 30 seconds? Displaying the following message > A stop job is running for User Manager for UID 1000 ...... -Regards

2 2

[oS-EN] Log noise: systemd-xdg-autostart-generator
by Carlos E. R. 24 Apr '24

24 Apr '24

Hi, I see these entries in the warning log: <3.4> 2024-04-20T00:00:02.837974+02:00 Isengard systemd-xdg-autostart-generator 2297 - - Not generating service for XDG autostart app-xapp\x2dsn\x2dwatcher(a)autostart.service, error parsing Exec= line: No such file or directory <3.4> 2024-04-21T00:00:02.529630+02:00 Isengard systemd-xdg-autostart-generator 22284 - - Not generating service for XDG autostart app-xapp\x2dsn\x2dwatcher(a)autostart.service, error parsing Exec= line: No such file or directory <3.4> 2024-04-22T00:00:03.205331+02:00 Isengard systemd-xdg-autostart-generator 9209 - - Not generating service for XDG autostart app-xapp\x2dsn\x2dwatcher(a)autostart.service, error parsing Exec= line: No such file or directory <3.4> 2024-04-23T00:00:02.910814+02:00 Isengard systemd-xdg-autostart-generator 28799 - - Not generating service for XDG autostart app-xapp\x2dsn\x2dwatcher(a)autostart.service, error parsing Exec= line: No such file or directory Now, where is that bad "Exec=" line? Isengard:~ # locate watcher(a)autostart.service Isengard:~ # I don't know where to find it. -- Cheers / Saludos, Carlos E. R. (from Telcontar, using openSUSE Leap 15.4)

3 7

Unknown kernel command line parameters:
by -pj 24 Apr '24

24 Apr '24

I have openSUSE Tumbleweed 20240419, Plasma 6 installed on this machine. My question for you is when I review log with 'journalctl -b' I see two lines, relating to, I think - Unknown kernel command line parameters . The two lines are below. Thinkcentre-M57p kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.8.7-1-default root=/dev/mapper/system-root resume=/dev/system/swap nvidia_drm.modeset=1 splash=0 plymouth.enable=0 mitigations=auto nosimplefb=1 security=apparmor Apr 21 10:45:44 paul-Thinkcentre-M57p kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-6.8.7-1-default splash=0", will be passed to user space. - I have included the '/etc/default/grub' file below. The file has *different* entries, especially in the in it compared to the entries displayed in the log above. Thinkcentre-M57p:~> cat /etc/default/grub # If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. # Uncomment to set your own custom distributor. If you leave it unset or empty, the default # policy is to determine the value from /etc/os-release GRUB_DISTRIBUTOR= GRUB_DEFAULT=saved GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=11 GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/system/swap nvidia_drm.modeset=1 splash=0 plymouth.enable=0 mitigations=auto nosimplefb=1 security=apparmor" # 03-05-24 Added and Removed: Creates double outputs in /proc/cmdline root=/dev/mapper/system-root # 03-05-24 Added and Removed: (SDDM (GUI) fails with: acpi=off # 03-02-24 Swapped: the nosimplefb=1 *TO* nvidia_drm.modeset=1 # 02-18-24 Just removed the 2 lines below, from above (testing hibernate): # Removed the following from above (most likely causing lockups): i8042.nomux=1 i8042.reset i8042.noloop=1 # Removed the following from above (caused PS/2 style keyboard 'keypress' to unsuspend machine): usbcore.autosuspend=-1 GRUB_CMDLINE_LINUX="" # Uncomment to automatically save last booted menu entry in GRUB2 environment # variable `saved_entry' # GRUB_SAVEDEFAULT="true" #Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) # GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" #Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL="gfxterm" # The resolution used on graphical terminal #note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE="1920x1080" # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux # GRUB_DISABLE_LINUX_UUID=true #Uncomment to disable generation of recovery mode menu entries GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" GRUB_BACKGROUND= GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt SUSE_BTRFS_SNAPSHOT_BOOTING="true" GRUB_DISABLE_OS_PROBER="false" GRUB_ENABLE_CRYPTODISK="y" GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16" Thinkcentre-M57p:~> - This is a susepaste of the above > https://paste.opensuse.org/pastes/eea7bf4dbb1f - Thinkcentre-M57p:~> cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.8.7-1-default root=/dev/mapper/system-root resume=/dev/system/swap nvidia_drm.modeset=1 splash=0 plymouth.enable=0 mitigations=auto nosimplefb=1 security=apparmor - Can you tell me where "BOOT_IMAGE=/boot/vmlinuz-6.8.7-1-default" is coming from? I believe the "splash=0" can be safely removed and is related to Plymouth. How serious are these errors and can they be fixed and how? -regards

3 3

plasma 6 graphic hardware acceleraton
by Simon Becherer 24 Apr '24

24 Apr '24

Hi, yesterday i updated one tumbleweed system to plasma 6 graphic: Radeon RX 7900XT 20GB open surce drivers could anybody tell me where i find the settings for the hardware accelleration? (switch on off, change driver) i was looking in systemsettings workspace behavior (and other places but did not find) .. at the moment i also did not find in plasma 5 but i remember somewhere there was this settings... and, i recognized that if i use x11 "glmark2" or "vkmark" will not work. one works the other not (i am on another system now, and i have forgotten which on.) with wayland both work. simoN -- www.becherer.de

5 6

kde plasma 6 wayland invisible cursor
by Simon Becherer 24 Apr '24

24 Apr '24

Hi, a second tumbleweed system i updated this has graphic: Radeon RX 6900XT open source drivers and with wayland i have a invisible cursor. in x11 cursor is here. there is a logitech mouse connected, but i do not think this is related. (but same problem with wayland glmark2 will not show any output, see my other mail) ... its really a challange to use a desktop with invisible cursor.... so did anybody know how to solve. simoN -- www.becherer.de

1 3

ssh -X wayland
by Simon Becherer 23 Apr '24

23 Apr '24

Hi, thinking around because of updating the first tumbleweed machines to plasma 6 wayland (not connected to his here:) i have a setup: suse linux 10.1 (I586) as a virtual machine. there is running a proprietary (graphical) software, there is no way to get it at a more modern system running. i have to use this software on several other machines opensuse tumbleweed by accessing it with "ssh -X" (x11 forwarding) i do this since years, works perfect. so my question is, if i update now my tumbleweed systems will this still run if kde-plasma is finally switched to wayland? or how will it be possible to start the software multiple times on the virtual machine from different up to date tumbleweed systems (of course i need the graphical output)? anybody have similar systems/setup's and expirience? simoN -- www.becherer.de

2 2

Backend: classic_rpntrans?
by Lew Wolfgang 22 Apr '24

22 Apr '24

Hi Folks, I ran "zypper up" on a server this afternoon and everything proceeded apace. But now when I run "zypper up" I get a message right before the "continue? line saying, "Backend: classic_rpmtrans". Is something going on here I should know about? Google is not particularly helpful this time. Regards, Lew

3 3

cpupower-gui failing to apply config at boot.
by -pj 22 Apr '24

22 Apr '24

Hi, openSUSE Tumbleweed 20240418 is installed on this machine. I am noticing these messages now relating to cpupower-gui in a journalctl -b log output. https://paste.opensuse.org/pastes/3fa21ae9b076 cpupower-gui has become unable to launch through application menu as well as Konsole now. I reported a bug on cpupower-gui github page yesterday. https://github.com/vagnum08/cpupower-gui/issues/119 Started an ICEWM session (I thought it may be KDE related issue). Attempted start from Konsole by passing: # cpupower-gui -p resulting in a failure and output the same as shown in the log file. Could this possibly be an issue with the newer kernel version? uname -a 6.8.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Apr 15 06:36:47 UTC 2024 (605b284) x86_64 x86_64 x86_64 GNU/Linux What are your thoughts on this situation? -Best Regards

3 7

Upgrade help
by Fred 21 Apr '24

21 Apr '24

Was running Leap 15.0. Made a backup (rsync) of /home. Tonight installed Leap 15.5. 2 questions: * how do I permanently mount /dev/sda1 as /home? Things have changed a bit since the last time I did that. * I had 2 instances of firefox in 15.0. When I start FF in 15.5, it has no idea about my profile. If I tell it to use what appears to be the correct one, FF argues, says I'm trying to run an old version and it will (maybe) corrupt my data and gives me 2 choices: make a new profile or quit. %$#@! How do I get FF to use my data: tabs, bookmarks, etc from 15.0? Oh, yeah - the 2 instances I had on 15.0? When I start FF it picks up the tabs from one (the wrong one, of course!). Maybe I am just tired but I could not figure it out so I'm reaching out. Thanks, Fred

4 4