Desktop environment (KDE, LXQT…):
KDE Plasma 6.3.4; KDE Frameworks Version 6.13.0
Description of the issue (screenshots if relevant):
Randomly the laptop shutdown with no advice while using the pc (it seems not doing any stopping procedure, just power off).
No over-temperature in both the graphics and cpu.
Nvidia driver installed through the Welcome application (after installing nvidia drivers the welcome app is totally black).
It happens often after being a while on youtube.
Tried both chromium based browsers and firefox based, with no improvements.
I’m supposing the issue can be related to the Nvidia driver installation: should I try to safely remove them and re-enable the free ones? In this case, please suggest the right steps in the terminal.
At the moment I’m excluding an hw problem because this is not happening on Ubuntu.
Don’t know if it could be related or it’s another issue I have:
I already tried to disable “recommended performance settings” and hardware acceleration in the browser, but not changing KDE conpositing settings.
I really don’t know how to proceed and would really appreciate some help
I was originally writing one post, but now it seems to me that there are two separated issues I’m having. The other one doesn’t let me to boot up the system, this one happens while working in the system that have the boot completed.
Just before the shutdown there is no notification (i.e. about battery critically low level), nor in kde nor in the logs (including journalctl): at least I’m not able to find any related message.
It’s still possible that the battery is causing power related issues due to its state and chemistry. This can affect system stability. Please try the other guidance suggested (remove the battery and test the PC).
The battery is integrated. I need to disassemble the laptop.
In the meanwhile, how can I safely remove the nvidia drivers and restore the situation after the first install of OM? I want to try to get rid of those too, because if I don’t use hw optimization the pc remains alive.
Can I install hyprland or cinnamon too? Are the right commands sudo dnf in hyprland and sudo dnf in cinnamon?
Before you try that, have you installed envycontrol and then put the GPU in either Hybrid or Integrated mode? That should shut down the GPU and help with battery life.
I physically disconnected the battery that now is no more detected, but I’m still experiencing random shutdowns during usage. If I leave the pc powered on and alone, the pc never shuts down.
Alright. Now that we have ruled out the failing battery as a potential source, let’s dive a little deeper.
You said it’s shutting down. By that, do you mean the power is cutting off, or that it’s going through a shutdown routine on it’s own without you initiating it?
You are saying the issue comes from watching videos on YT. Have you ever replaced the thermal pads on your GPU inside the notebook? Do you place the notebook on a flat, hard surface and not on a blanket or bed? Have you ever cleaned out the fans and heatsinks? Typically, the CPU and GPU will use the same thermal pipe and heatsink leading to a cyclone fan. If it can’t breathe, it can overheat internally, or cause thermal tolerances to breakdown over time.
The power is cutting off, and it’s not going through a shutdown routine. At least it seems so.
I have not replaced the thermal pads on the GPU inside the notebook.
I have the notebook on a flat, hard surface. Specifically it’s an alluminium support that keeps the laptop elevated.
Yes, I cleaned the internal hw.
Temperatures reaches a maximum of 78 degrees after a long while with a 4k live video from internet. Fan speed it’s always at lower speed, unless there are high temperatures then it speeds up to 3200rpm.
I forced myself to use Windows for an entire day, and I was not experiencing unexpected power off. I had only some issue with the wifi and ethernet. Hence I was thinking that these devices could cause problems to the system. The only one time Windows suddenly powered off was when I installed the updated Nvidia drivers.
Then I forced myself to use OM from the live USB for an entire day, and there was no unexpected power off.
At this point, I decided to remove the Nvidia drivers from the installed OM.
After removing the Nvidia packages I was not able to open any application from Plasma, except for yakuake with which I rebooted my system.
I logged in to kde and a black screen with a blinking underscore was entertaining me for a looong while, then kde loaded as usual. But in two minutes, while I was reading the OM welcome, the black screen came back and, after a little while, the kde login was presented to me again. At this point, I shutdown the system.
When powered on again, happened the same steps that lead me to a forced logout. I tried also the Failsafe X at login, without success: while writing in the terminal, boom, logout.
Have you any idea how to solve this? I’m not too much familiar with KDE to remove some configs by myself.
I moved these config folders away with no success:
When removing the nvidia things, the output was the following one:
❯ sudo dnf rm nvidia nvidia-firmware lib64nvidia-egl-wayland1
Dependencies resolved.
=======================================================================================================================================================================
Package Architecture Version Repository Size
=======================================================================================================================================================================
Removing:
lib64nvidia-egl-wayland1 x86_64 1.1.18-1 @rolling-x86_64 80 k
nvidia x86_64 575.51.02-1 @rolling-x86_64-non-free 695 M
nvidia-firmware noarch 20250413-1 @System 38 M
Removing dependent packages:
nvidia-32bit x86_64 575.51.02-1 @rolling-x86_64-non-free 368 M
nvidia-settings x86_64 575.51.02-1 @rolling-x86_64-non-free 1.6 M
Removing unused dependencies:
lib64crypto1.1 x86_64 1.1.1m-1 @rolling-x86_64 3.1 M
nvidia-kmod-common noarch 575.51.02-1 @rolling-x86_64-non-free 99 M
nvidia-kmod-desktop x86_64 575.51.02-1_6.14.2_3 @rolling-x86_64-non-free 183 M
nvidia-modprobe x86_64 575.51.02-1 @rolling-x86_64-non-free 42 k
nvidia-persistenced x86_64 575.51.02-1 @rolling-x86_64-non-free 44 k
Transaction Summary
=======================================================================================================================================================================
Remove 10 Packages
Freed space: 1.4 G
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : nvidia-firmware-20250413-1.noarch 1/10
Erasing : nvidia-settings-575.51.02-1.x86_64 2/10
Erasing : nvidia-575.51.02-1.x86_64 3/10
Erasing : nvidia-kmod-common-575.51.02-1.noarch 4/10
Running scriptlet: nvidia-kmod-common-575.51.02-1.noarch 4/10
Creating group 'nogroup' with GID 65534.
Creating group 'audio' with GID 81.
Creating group 'cdrom' with GID 22.
Creating group 'dialout' with GID 83.
Creating group 'disk' with GID 6.
Creating group 'input' with GID 101.
Creating group 'kmem' with GID 9.
Creating group 'kvm' with GID 36.
Creating group 'lp' with GID 7.
Creating group 'render' with GID 105.
Creating group 'sgx' with GID 106.
Creating group 'tape' with GID 21.
Creating group 'tty' with GID 5.
Creating group 'video' with GID 82.
Creating group 'users' with GID 100.
Creating group 'systemd-journal' with GID 190.
Creating user 'root' (Super User) with UID 0 and GID 0.
Creating user 'nobody' (Kernel Overflow User) with UID 65534 and GID 65534.
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/background.png
Found linux image: /boot/vmlinuz-6.14.2-desktop-3omv2590
Found initrd image: /boot/initrd-6.14.2-desktop-3omv2590.img
Found memtest image: /boot/memtest.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
File descriptor 3 (pipe:[39053]) leaked on vgs invocation. Parent PID 13942: grub2-probe
File descriptor 9 (pipe:[38135]) leaked on vgs invocation. Parent PID 13942: grub2-probe
File descriptor 3 (pipe:[39053]) leaked on vgs invocation. Parent PID 13942: grub2-probe
File descriptor 9 (pipe:[38135]) leaked on vgs invocation. Parent PID 13942: grub2-probe
File descriptor 3 (pipe:[39053]) leaked on vgs invocation. Parent PID 14077: grub2-probe
File descriptor 9 (pipe:[38135]) leaked on vgs invocation. Parent PID 14077: grub2-probe
File descriptor 3 (pipe:[39053]) leaked on vgs invocation. Parent PID 14077: grub2-probe
File descriptor 9 (pipe:[38135]) leaked on vgs invocation. Parent PID 14077: grub2-probe
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Ubuntu 24.04.2 LTS on /dev/sda4
Found AlmaLinux 8.10 (Cerulean Leopard) on /dev/mapper/almalinux_fedora-root
Adding boot menu entry for UEFI Firmware Settings ...
Adding boot menu entry for EFI firmware configuration
done
Erasing : nvidia-kmod-desktop-575.51.02-1_6.14.2_3.x86_64 5/10
Erasing : nvidia-32bit-575.51.02-1.x86_64 6/10
Erasing : lib64nvidia-egl-wayland1-1.1.18-1.x86_64 7/10
Erasing : lib64crypto1.1-1.1.1m-1.x86_64 8/10
Erasing : nvidia-modprobe-575.51.02-1.x86_64 9/10
Erasing : nvidia-persistenced-575.51.02-1.x86_64 10/10
Running scriptlet: nvidia-persistenced-575.51.02-1.x86_64 10/10
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/background.png
Found linux image: /boot/vmlinuz-6.14.2-desktop-3omv2590
Found initrd image: /boot/initrd-6.14.2-desktop-3omv2590.img
Found memtest image: /boot/memtest.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
File descriptor 3 (pipe:[44030]) leaked on vgs invocation. Parent PID 30477: grub2-probe
File descriptor 9 (pipe:[45525]) leaked on vgs invocation. Parent PID 30477: grub2-probe
File descriptor 20 (/home/silvano) leaked on vgs invocation. Parent PID 30477: grub2-probe
File descriptor 3 (pipe:[44030]) leaked on vgs invocation. Parent PID 30477: grub2-probe
File descriptor 9 (pipe:[45525]) leaked on vgs invocation. Parent PID 30477: grub2-probe
File descriptor 20 (/home/silvano) leaked on vgs invocation. Parent PID 30477: grub2-probe
File descriptor 3 (pipe:[44030]) leaked on vgs invocation. Parent PID 30622: grub2-probe
File descriptor 9 (pipe:[45525]) leaked on vgs invocation. Parent PID 30622: grub2-probe
File descriptor 20 (/home/silvano) leaked on vgs invocation. Parent PID 30622: grub2-probe
File descriptor 3 (pipe:[44030]) leaked on vgs invocation. Parent PID 30622: grub2-probe
File descriptor 9 (pipe:[45525]) leaked on vgs invocation. Parent PID 30622: grub2-probe
File descriptor 20 (/home/silvano) leaked on vgs invocation. Parent PID 30622: grub2-probe
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Ubuntu 24.04.2 LTS on /dev/sda4
File descriptor 20 (/home/silvano) leaked on vgs invocation. Parent PID 38249: /usr/bin/grub2-probe
File descriptor 20 (/home/silvano) leaked on vgs invocation. Parent PID 38249: /usr/bin/grub2-probe
Found AlmaLinux 8.10 (Cerulean Leopard) on /dev/mapper/almalinux_fedora-root
Adding boot menu entry for UEFI Firmware Settings ...
Adding boot menu entry for EFI firmware configuration
done
Running scriptlet: nvidia-persistenced-575.51.02-1.x86_64 10/10
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
Removed:
lib64crypto1.1-1.1.1m-1.x86_64 lib64nvidia-egl-wayland1-1.1.18-1.x86_64 nvidia-575.51.02-1.x86_64 nvidia-32bit-575.51.02-1.x86_64 nvidia-firmware-20250413-1.noarch
nvidia-kmod-common-575.51.02-1.noarch nvidia-kmod-desktop-575.51.02-1_6.14.2_3.x86_64 nvidia-modprobe-575.51.02-1.x86_64 nvidia-persistenced-575.51.02-1.x86_64 nvidia-settings-575.51.02-1.x86_64
Complete!
Here, it’s saying Found Ubuntu 24.04.2 LTS on /dev/sda4 and Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi that is not correct (the partitions are in /dev/sdb4 and /dev/sdb1, all OSs are on sdb*, only two data partitions are on sda*): in fact I cannot boot anymore the other OSs from the OM bootloader. I need to start them by entering the UEFI menu, and when not using the OM boot loader I have no issues (including the network devices problem in windows and ubuntu).
Is the transaction scriplet confused or something?
Thank you guys for your help! I’m new to OM and I like the paradigm under it, and I want to configure it to use for my daily work too.
I have seen this, and I don’t have nvidia hardware. It happened on ROME. Initially there was no issues but after few days, I would be automatically logged out of plasma session and brought to login screen after couple of minutes as you mentioned. This was persistent, meaning rebooting would not fix it. But after sometime it became OK by itself.
Later, I had to reinstall ROME and the issue repeated in sequence (initially OK, then auto-logouts and later fixed on its own).
My workaround was to stop ‘sddm’ and manually start X.
Login from any other virtual terminal (CTRL+ALT+F2)
Create (or if you already have, edit) the .xinitrc file.
echo 'exec /usr/bin/startplasma-x11' > ~/.xinitrc
Start X session manually with startx
When I did that, the session would not auto-logout. I could have disabled ‘sddm’ altogether but then would not have noticed the auto-fix
The issue could be intermittent or with a particular ISO build (I don’t remember which one I used) or an update fixed it (what got broken by an earlier update ). Not sure.
As for your main issue with random shutdowns, I don’t have much clue. However, I have experienced random shutdowns much like how you have described; difference is in my case it was an old-old-old acer laptop. It is currently resting in my attic. Yours seems slightly different in that you don’t have issue with other distro or Windows.
Have you tried using a different kernel? Either older or newer? There was a topic regarding wifi not working which got fixed with a kernel upgrade (rc-kernel). If you say there is no issue with other distro(s), it is worth investigating.
That can happen sometimes; the drive IDs getting swapped. That is why it is recommended to use UUIDs inside /etc/fstab. Reboot and run update-grub2. If not first time, try again. That should fix it.
Thank you for your useful suggestion! It’s happening to me exactly what you’re describing. Also after reinstalling the nvidia packages.
The lines I added to the /etc/fstab already use the UUID, but in the fstab there is no partition listed containing other OSs installed in the system, and usually there is no need to add them.
After I removed those packages, while having the sddm issue, I reinstalled the same three packages and this solved the this issue I was encountering after installing the nvidia drivers the first time:
I can correctly see the OM-Welcome now with the nvidia packages installed.
). Not sure.