Bug 499190 - SDDM does work only after systemctl restart sddm!
Summary: SDDM does work only after systemctl restart sddm!
Status: CONFIRMED
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages Unstable Edition (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-27 12:07 UTC by Gilberto Ferreira
Modified: 2025-10-15 10:51 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gilberto Ferreira 2025-01-27 12:07:18 UTC
SUMMARY
Whe boot or reboot, the sddm doesn't started and just give me the black screen.
Doing control + alt + f4, and systemctl restart sddm, them sddm start properly
The error message is that:
● sddm.service - Simple Desktop Display Manager
     Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: enabled)
     Active: active (running) since Mon 2025-01-27 08:52:19 -03; 36s ago
       Docs: man:sddm(1)
             man:sddm.conf(5)
   Main PID: 770 (sddm)
      Tasks: 2 (limit: 18442)
     Memory: 21.4M (peak: 23.6M)
        CPU: 118ms
     CGroup: /system.slice/sddm.service
             └─770 /usr/bin/sddm

jan 27 08:52:20 karis sddm[770]: Adding new display...
jan 27 08:52:20 karis sddm[770]: Loaded empty theme configuration
jan 27 08:52:20 karis sddm[770]: Xauthority path: "/run/sddm/xauth_KylhYs"
jan 27 08:52:20 karis sddm[770]: Using VT 2
jan 27 08:52:20 karis sddm[770]: Display server starting...
jan 27 08:52:20 karis sddm[770]: Writing cookie to "/run/sddm/xauth_KylhYs"
jan 27 08:52:20 karis sddm[770]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_KylhYs -noreset -displayfd 16
jan 27 08:52:20 karis sddm[770]: Failed to read display number from pipe
jan 27 08:52:20 karis sddm[770]: Display server stopping...
jan 27 08:52:20 karis sddm[770]: Attempt 1 starting the Display server on vt 2 failed

STEPS TO REPRODUCE
1. Install Neon Unstable
2. SDDM fail
3. Do control + alt + f4 and systemctl restart sddm, them sddm start properly

OBSERVED RESULT
sddm doesn't started


EXPECTED RESULT
sddm started properly

SOFTWARE/OS VERSIONS

ADDITIONAL INFORMATION
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-x64v3-xanmod1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G
Memory: 15.1 GiB of RAM
Graphics Processor 1: AMD Radeon R7 Graphics
Graphics Processor 2: AMD Radeon 500 Series
Manufacturer: Acer
Product Name: Aspire A515-41G
System Version: V1.09
Comment 1 Julien Delquié 2025-10-15 10:51:18 UTC
I have a similar issue only on one of my Gentoo.

The thing I can see in journalctl -b:
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: "kwin_core: Failed to open /dev/dri/card0 device (Device or resource busy)\n"
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: "kwin_wayland_drm: failed to open drm device at \"/dev/dri/card0\"\n"
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: "kwin_wayland_drm: No suitable DRM devices have been found\n"
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: "QThreadStorage: entry 7 destroyed before end of thread 0x558d64fe87d0\nQThreadStorage: entry 1 destroyed before end of thread 0x558d64fe87d0\nQThreadStorage: entry 0 destroyed before end of thread 0x558d
64fe87d0\n"
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: wayland compositor finished 1 QProcess::NormalExit
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: quitting helper-start-wayland
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: Stopping... "/usr/bin/sddm-greeter-qt6"
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: wayland greeter finished 15 QProcess::CrashExit
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper-start-wayland[1033]: quitting helper-start-wayland
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper[991]: [PAM] Closing session
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper[991]: pam_unix(sddm-greeter:session): session closed for user sddm
oct. 15 12:45:53 ordiyp.taniere.lan sddm-helper[991]: [PAM] Ended.
oct. 15 12:45:53 ordiyp.taniere.lan sddm[976]: Auth: sddm-helper exited successfully
oct. 15 12:45:53 ordiyp.taniere.lan sddm[976]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS

My sddm configuration is set to use Wayland, not X.

And if I perform a systemctl restart sddm, from console (Ctrl+Alt+F2), sddm starts correctly.