| View previous topic :: View next topic |
| Author |
Message |
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 184
Location: 11.435765792823453, 143.05926743686274
|
 Posted: Wed Oct 23, 2024 8:25 pm Post subject: SDDM exits on launch and drops to shell [resolved] |
 |
|
when launching, or re-starting display-manager through openRC, as well as launching SDDM via the console manually, the screen slightly brightens for a moment, and shows a cursor, before darkening again. it then flashes bright and dark a few times, before exiting to console
Xorg seems to be working fine, as startx does bring up 3 terminals as expected of default behavior
sddm.log
standout lines:
| Code: |
[20:04:43.649] (WW) DAEMON: Auth: sddm-helper exited with 4
[20:04:43.649] (II) DAEMON: Greeter stopped. SDDM::Auth::HELPER_DISPLAYSERVER_ERROR
|
after this, it falls back from x11 to x11-user launch, resulting in this:
| Code: |
[20:04:44.214] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[20:04:44.215] (II) DAEMON: Greeter session started successfully
[20:04:44.215] (II) HELPER: [PAM] Closing session
[20:04:44.215] (II) HELPER: [PAM] Ended.
[20:04:44.216] (WW) DAEMON: Auth: sddm-helper exited with 5
[20:04:44.216] (II) DAEMON: Greeter stopped. SDDM::Auth::HELPER_TTY_ERROR
|
Xorg.0.log
Xorg.0.log.old
(one attempted launch generated both)
things tried:
adding sddm user to tty group - no result
downgrading sddm to previous release - no result
this is an LLVM system.
if more information or additional test would help, please let me know hat else to do/share.
any help is appreciated
-S
Last edited by Shadow_Fury on Thu Nov 07, 2024 12:05 am; edited 1 time in total |
|
| Back to top |
|
 |
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 652
|
| Posted: Wed Oct 23, 2024 10:57 pm Post subject: Re: SDDM exits on launch and drops to shell |
|
|
| Shadow_Fury wrote: | | Xorg seems to be working fine, as startx does bring up 3 terminals as expected of default behavior |
Is /etc/init.d/dbus running? < It's a dependency of sddm, but not picked up by display-manager when "sddm" is set in conf.d/display-manager. |
|
| Back to top |
|
|
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 184
Location: 11.435765792823453, 143.05926743686274
|
| Posted: Wed Oct 23, 2024 11:19 pm Post subject: Re: SDDM exits on launch and drops to shell |
|
|
| Ralphred wrote: | | Shadow_Fury wrote: | | Xorg seems to be working fine, as startx does bring up 3 terminals as expected of default behavior |
Is /etc/init.d/dbus running? < It's a dependency of sddm, but not picked up by display-manager when "sddm" is set in conf.d/display-manager. |
dbus is running, at least once the system is at the login shell (pretty sure NetworkManager is starting it, however there is no difference in sddm behavior between booting and running it from the shell (at which point dbus is definitely running) , so i don't think that's it.
whilst i was chrooted from an installation CD just now, i decided to try launching SDDM from the chroot shell, and got a different result (i didn't expect it to work, but thought it might reveal something). i saw a brief flash of the SDDM screen, then the system froze. |
|
| Back to top |
|
|
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 652
|
| Posted: Thu Oct 24, 2024 10:15 am Post subject: |
|
|
| I don't think it'll be this, but I'm getting vague recollections of similar sddm.log entries when support for my ancient gpu was dropped from mesa: Run startx as root, and make sure glxgears works, just to disprove it's a similar issue. |
|
| Back to top |
|
|
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 184
Location: 11.435765792823453, 143.05926743686274
|
| Posted: Thu Oct 24, 2024 11:57 am Post subject: |
|
|
| Ralphred wrote: | | I don't think it'll be this, but I'm getting vague recollections of similar sddm.log entries when support for my ancient gpu was dropped from mesa: Run startx as root, and make sure glxgears works, just to disprove it's a similar issue. |
both glxgears, and vkcube work correctly.
also, it's a (relativley) modern GPU, and i'm running manufacturer drivers (RTX-2080 ti, with nvidia's open source kernel drivers)
from looking it up, i know that the sddm-greeter process returns different numbers for different errors, but can't for the life of me find out what 4 is supposed to represent |
|
| Back to top |
|
|
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 184
Location: 11.435765792823453, 143.05926743686274
|
| Posted: Fri Oct 25, 2024 11:03 am Post subject: |
|
|
ok, did some investigating, and there is a difference in the sddm log from the liveGUI iso, and my system (bear in mind that the livegui uses wayland, but SDDM itself seems to still launch using X.)
liveGUI:
| Code: |
[10:43:27.168] (II) HELPER: [PAM] Starting...
[10:43:27.168] (II) HELPER: [PAM] Authenticating...
[10:43:27.171] (II) HELPER: [PAM] Preparing to converse...
[10:43:27.171] (II) HELPER: [PAM] Conversation with 1 messages
[10:43:27.172] (II) HELPER: [PAM] returning.
[10:43:27.173] (II) DAEMON: Authentication for user "gentoo" successful
[10:43:27.175] (II) HELPER: [PAM] Preparing to converse...
[10:43:27.175] (II) HELPER: [PAM] Conversation with 1 messages
|
my system:
| Code: |
[20:04:43.312] (II) HELPER: [PAM] Starting...
[20:04:43.312] (II) HELPER: [PAM] Authenticating...
[20:04:43.312] (II) HELPER: [PAM] returning.
[20:04:43.351] (II) HELPER: Writing cookie to "/tmp/xauth_cMVnuz"
[20:04:43.351] (II) HELPER: Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-RvOVEX"
[20:04:43.352] (II) DAEMON: Greeter session started successfully
[20:04:43.369] (II) DAEMON: Message received from greeter: Connect
[20:04:43.647] (II) HELPER: [PAM] Closing session
[20:04:43.648] (II) HELPER: [PAM] Ended.
[20:04:43.649] (WW) DAEMON: Auth: sddm-helper exited with 4
[20:04:43.649] (II) DAEMON: Greeter stopped. SDDM::Auth::HELPER_DISPLAYSERVER_ERROR
|
in the liveGUI, a conversation with PAM is occurring, though i don't know if that's relevant. the fact that no errors are raised indicates that the PAM negotiation was a success.
full liveGUI log |
|
| Back to top |
|
|
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 652
|
| Posted: Fri Oct 25, 2024 12:52 pm Post subject: |
|
|
| Shadow_Fury wrote: | | bear in mind that the livegui uses wayland, but SDDM itself seems to still launch using X. |
I think that's what's responsible for the different log entries, Writing cookie to "/tmp/xauth_cMVnuz" reads like "auth succesful, here's the cookie".
The VT1/VT7 switching in the logs is "odd", but I think it's time to drop emerge --info sddm, and short of any obvious malady there push it upstream as an llvm bug. |
|
| Back to top |
|
|
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 184
Location: 11.435765792823453, 143.05926743686274
|
| Posted: Fri Oct 25, 2024 1:17 pm Post subject: |
|
|
| Ralphred wrote: | | Shadow_Fury wrote: | | bear in mind that the livegui uses wayland, but SDDM itself seems to still launch using X. |
I think that's what's responsible for the different log entries, Writing cookie to "/tmp/xauth_cMVnuz" reads like "auth succesful, here's the cookie".
The VT1/VT7 switching in the logs is "odd", but I think it's time to drop emerge --info sddm, and short of any obvious malady there push it upstream as an llvm bug. |
here it is:
emerge --info sddm
just to point out, the error from the helper is weird. it claims to be an error with the display server, but X is already running, and there isn't anything (that i can find in the Xorg log about it)
also, when trying to build sddm with GCC, it fails; i don't know why. |
|
| Back to top |
|
|
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 184
Location: 11.435765792823453, 143.05926743686274
|
| Posted: Thu Nov 07, 2024 12:05 am Post subject: |
|
|
| as it turns out, re-compiling with GCC fixed the issue. Guess sddm is another thing not yet compatible with clang |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
