thanks for info
And on my systems, stopping sddm, palsma-x11 or plasma-wayland or gnome work well.
Greetings
1 Like
You will probably want to look this over regarding your intel GPU:
https://wiki.archlinux.org/title/Intel_graphics
There may be some things you need to manually configure in configs and in the grub entry. Itās possible to apply grub settings from the boot menu without committing them to happen automatically so you can find a combination that may work. We donāt have the resources to test for every single hardware support scenario. We could bloat our images like other distros do, but we prefer not to so the user can decide what is on their system. Sometimes that means new user expectations are going to fall short.
SDDM has itās frequent problems, but I donāt think this is one of them. If you find a bug in their upstream and want to link it here, that may clear it up.
Thank you, I will certainly take a look.
IIRC some time ago someone wrote that installing kernel-server did fix the issue.
Not 100% sure, as I go by memory.
I will try it out.
thanks.
3 out of 3 reboots are ok
(the clear weather is backā¦ hope it holds)
@rugyada thanks [what a memory!].
kernel is 6.14.2-server-3omv2590
2 Likes
Haste makes waste (gatta frettolosaā¦) Too much haste to declare resolved.
notebook B (reference above) does not resolve with kernel-server, after further reboots also notebook A does not resolve with kernel-server.
Doing further tests with:
- plasma6-sddm
- gdm
- xdm
I conclude that, on my machines, plasma6-sddm has instability problems, which gdm and even xdm do not have.
Reinstalling plasma6-sddm at the end of the process appears conflict warning (not sure if useful)
/usr/lib/sysusers.d/dbus.conf:1: Conflict with earlier configuration for user āmessagebusā in /usr/lib/sysusers.d/dbus-broker.conf:2, ignoring line.
Iām sorry.
1 Like
No sorry. Thanks for the feedback.
Maybe more useful to read all the transaction log, as usual 
If/when you manage to reinstall sddm, since the kernel-server workaround looks not working, Iād suggest to change the sddm theme to elarun or maldives and see if that will help.
reinstall-plasma6-sddm.txt (4.5 KB)
this was wanted?
about changing theme I had already done it a couple of months ago, following a forum maybe about kde, but without success.
1 Like
20250527-status-sddm.service.txt (976 Bytes)
search: " The theme at ā/usr/share/sddm/themes/breezeā requires missing ā/usr/bin/sddm-greeterā . Using fallback theme."
where can I find it?
rpm -qa|grep sddm ?
I have
plasma6-sddm
plasma6-sddm-theme-breeze
plasma6-sddm-kcm
and I have /usr/bin/sddm-greeter-qt6
ā/usr/bin/sddm-greeter-qt6ā there is;
sought: ā/usr/bin/sddm-greeterā and so I linked it:
sudo ln -s /usr/bin/sddm-greeter-qt6 /usr/bin/sddm-greeter
your suggestion:
rpm -qa | grep sddm
plasma6-sddm-0.21.0-2.x86_64 here
and then installed āplasma6-sddm-theme-breezeā and āplasma6-sddm-kcmā
another reboot and unfortunately everything as before.
I will stop here for now.
So to refresh my poor memory of where this issue is now: With plasma6-sddm graphical boot fails 9 out of 10 times approx? With gdm or xdm it works as expected? Graphics for laptop āAā is:
Device-1: Intel Alder Lake-UP3 GT2 [UHD Graphics] driver: i915 v: kernel
For laptop āBā:
Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915
v: kernel
Device-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT
620M/625M/630M/720M] driver: nouveau v: kernel
I have not contributed recently because I do not have anything to suggest. Just trying to understand the problem. The only common elements I see are Intel cpuās but they are different from one another and Toshiba but even there the Moboās are different. The BIOSās are different. If two different laptops have the same issue, and it manifests in the same way on both, it makes sense to find out what the common element is. I am left to guess work. Some setting like āFast bootā enabled on both maybe? If there is any answer we are most likely to find it from these journalctl commands. One possibility is that there is an authentication problem, like something with pam or kauth but those are just guesses. Edit: A shot in the darkā¦ Maybe some setting in KWallet?
This
still smells to me 
Can you please compress the folder /usr/share/sddm/themes/breeze and attach it here?
(add a .txt fake extension to the archive afterwards or you will not be able to attach it)
Anyway, are you doing the latest tests with 1 or 2 monitors?
@rugyada wonāt let me load the compressed.txt, it says:
Sorry, that file is too big (maximum size is 4 MB). Why not upload your large file to a cloud sharing service, then paste the link?
but it is 2.1 MiB ā¦ anyway, I removed OpenMandriva-splash.png (1.2 MiB) and compressed the rest:
breeze.zip.txt (916.2 KB)
and yes tests done with both one and two monitors (even on the other notebook B which has only integrated screen). Happy hunting!
1 Like
rename file sddm-greeter to sddm-greeter-bak (or whatever)
maybe also remove line
showClock=true
from theme.conf.user
(you can add it back later)
hello @ben79 things are as you wrote, I am annoyed that the behavior in the error is not constant. If I remember correctly it all started in December 2024 one morning after waking up from hibernation suspension (as I always do). [I had posted a joking account in coffe- break-it].
It seems to me that even Hum_Had suffer such a problem.
journal-unsuccessful-boot.txt (845.4 KB)
dmesg-unsuccessful-boot.txt (116.5 KB)
Thank you.
doneā¦ and now another restart (I HATE RESTART)
see you soonā¦
The first round is OK. But letās abandon easy enthusiasm; I need to do extensive and thorough testing.
Of course Thank you.
1 Like
Ah ma allora sarĆ sempre colpa del folletto!