SDDM not starting at Run Level 4

Desiderius · 04-27-2021, 08:31 AM

Hi all

After many tries ( see discussion in "Little pb with KDE5", I have decided to comment out
the line of config for v3D and revert back to my orinal configuration of /boot/config.txt.

I have put the run Level to Four and restarted.

The boot finishes normally but stays on console ; looking at the boot , I check that the run Level is well 4 and that I have the message "Starting X session" : yes !

I log as root and run :

Code:

 /etc/rc.d/rc.4

It stays waiting ; relaunch with "sh -x", I see that the command :

Code:

 exec /usr/bin/sddm

is launched but waits without making anything !

I log as a normal user , starts Plasma with "startx" and it works normally !

In an Xterm, as root, I retry to launch :

Code:

 /etc/rc.d/rc.4

and here, I have an output saying that the daemon has started !

Any idea why this does not work at the boot ?

mralk3 · 04-27-2021, 09:53 AM

Did you see this post?
https://www.linuxquestions.org/quest...ml#post6232865

In short:

Code:

--- a/usr/bin/sddm      2021-03-22 13:30:32.209653646 +0700
+++ b/usr/bin/sddm      2021-03-22 13:32:55.810714919 +0700
@@ -3,4 +3,4 @@
 if [ -f /etc/default/sddm ]; then
   . /etc/default/sddm
 fi
-/usr/bin/sddm.bin "$*"
+exec /usr/bin/sddm.bin "$@"

Which should fix your issue with sddm. Let me know how it goes!

Desiderius · 04-28-2021, 02:15 AM

I made the modification you suggest in /usr/bin/sddm !

Reboot and nothing has changed : always stopped at console ; sddm does not start !

I have checked all the permissions of the directories of sdm : everything is correct.

But what I did not understand :

I enable again

Code:

 dtoverlay=vc4-fkms-v3d

and reboot

Here sddm is starting normally and asks me for logging !!!!

I look at /var/log/messages for possible errors but did not find any. When it works , I see

Code:

 elogind-daemon: New session c1 of user sddm

that I do not see in the other case of course

Desiderius · 04-28-2021, 07:30 AM

I am always looking for a solution or at least understand why it is working in one case and not the other.

After logging "manually" by logging and "startx", I have tried ( as root ) :

- to log the output and errors of sddm : nothing but I have seen numerous files in /tmp for sddm

Code:

srwx------ 1 sddm sddm 0 avril 28 11:35 /tmp/sddm-:0-bbdRln
srwx------ 1 sddm sddm 0 avril 28 13:37 /tmp/sddm-:0-BKTNYn
srwx------ 1 sddm sddm 0 avril 27 08:33 /tmp/sddm-:0-jelPuj
srwx------ 1 sddm sddm 0 avril 28 11:48 /tmp/sddm-:0-SzbldB
srwxr-xr-x 1 root root 0 avril 28 13:37 /tmp/sddm-auth38cc6e3c-bf83-4685-9db6-83dc9fc116ad
srwxr-xr-x 1 root root 0 avril 28 11:47 /tmp/sddm-auth3a918c7e-1643-451e-9354-f2568a2d2780
srwxr-xr-x 1 root root 0 avril 27 08:33 /tmp/sddm-auth9ad5df4e-95db-46d5-a766-1dc3afec8d9a
srwxr-xr-x 1 root root 0 avril 28 11:35 /tmp/sddm-authfe48241d-c7be-449e-8adb-a53d7ec4fb26

- to launch sddm by hand : it runs but do nothing nor outputs everything

But after doing that, I have looked at the process of the PI and "surprise" SDDM is running :

Code:

 
root       928     1  0 14:15 ?        00:00:00 /usr/bin/sddm.bin

but what is it doing ? is it awaiting something or some file ? I do not know !

Desiderius · 04-29-2021, 06:17 AM

One step further but yet no explanation

Looking at the sddm.log found in /var/log :

1) When SDDM works normally

Code:

[12:29:51.736] (II) DAEMON: Initializing...
[12:29:51.766] (II) DAEMON: Starting...
[12:29:51.767] (II) DAEMON: Logind interface found
[12:29:51.769] (II) DAEMON: Adding new display on vt 7 ...
[12:29:51.776] (II) DAEMON: Loading theme configuration from ""
[12:29:51.777] (II) DAEMON: Display server starting...
[12:29:51.777] (II) DAEMON: Adding cookie to "/var/run/sddm/{f80fc691-1195-4c9d-
8b1f-0e0276ed2038}"
[12:29:51.795] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sdd
m/{f80fc691-1195-4c9d-8b1f-0e0276ed2038} -background none -noreset -display
fd 17 -seat seat0 vt7
[12:29:53.836] (II) DAEMON: Setting default cursor
[12:29:53.849] (II) DAEMON: Running display setup script  "/usr/share/sddm/scrip
ts/Xsetup"
[12:29:54.559] (II) DAEMON: Display server started.
[12:29:54.559] (II) DAEMON: Socket server starting...
[12:29:54.563] (II) DAEMON: Socket server started.
[12:29:54.565] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/th
emes/breeze/theme.conf"
[12:29:54.566] (II) DAEMON: Greeter starting...
[12:29:54.650] (II) HELPER: [PAM] Starting...
[12:29:54.650] (II) HELPER: [PAM] Authenticating...
[12:29:54.650] (II) HELPER: [PAM] returning.
[12:29:54.692] (II) DAEMON: Greeter session started successfully
[12:29:55.299] (II) DAEMON: Message received from greeter: Connect
[12:30:17.756] (II) DAEMON: Message received from greeter: Login
[12:30:17.757] (II) DAEMON: Reading from "/usr/share/wayland-sessions/plasmawayl
and.desktop"
[12:30:17.759] (II) DAEMON: Reading from "/usr/share/wayland-sessions/plasmawayl
and.desktop"
[12:30:17.760] (II) DAEMON: Session "/usr/share/wayland-sessions/plasmawayland.d
esktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr
/bin/startplasma-wayland"
[12:30:17.855] (II) HELPER: [PAM] Starting...
[12:30:17.855] (II) HELPER: [PAM] Authenticating...
[12:30:17.856] (II) HELPER: [PAM] Preparing to converse...
[12:30:17.856] (II) HELPER: [PAM] Conversation with 1 messages
[12:30:17.892] (II) HELPER: [PAM] returning.
[12:30:17.896] (II) DAEMON: Authenticated successfully
[12:30:18.274] (II) HELPER: [PAM] Closing session
[12:30:18.278] (II) HELPER: [PAM] Ended.
[12:30:18.282] (II) DAEMON: Auth: sddm-helper exited successfully
[12:30:18.282] (II) DAEMON: Greeter stopped.
[12:30:18.362] (II) HELPER: Starting: "/usr/share/sddm/scripts/wayland-session /
usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
[12:30:18.370] (II) HELPER: Jumping to VT 8
[12:30:18.371] (II) HELPER: VT mode didn't need to be fixed
[12:30:18.669] (II) DAEMON: Session started

2) When SDDM does not display anything

Code:

[12:39:17.865] (II) DAEMON: Initializing...
[12:39:17.895] (II) DAEMON: Starting...
[12:39:17.896] (II) DAEMON: Logind interface found

Clearly it seems to have a problem of permissions somewhere !

BUT I have found that I can launch SDDM in "test-mode" making "/usr/bin/sddm.bin --test-mode"

When I do that (as a normal user), the Greeter appears in a window of Plasma already running and is fully functional

The log indicates it works in a normal way

Code:

[13:09:30.075] (II) DAEMON: Initializing...
[13:09:30.101] (II) DAEMON: Starting...
[13:09:30.103] (II) DAEMON: Adding new display on vt 7 ...
[13:09:30.106] (II) DAEMON: Loading theme configuration from ""
[13:09:30.106] (II) DAEMON: Display server starting...
[13:09:30.107] (II) DAEMON: Adding cookie to "./{6a94e02a-85b1-4599-a342-fbf39830036b}"
[13:09:30.143] (II) DAEMON: Setting default cursor
[13:09:30.152] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[13:09:30.741] (II) DAEMON: Display server started.
[13:09:30.741] (II) DAEMON: Socket server starting...
[13:09:30.742] (II) DAEMON: Socket server started.
[13:09:30.743] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[13:09:30.743] (II) DAEMON: Greeter starting...
[13:09:30.747] (II) DAEMON: Greeter started.
[13:09:30.747] (II) DAEMON: Adding cookie to "./{6a94e02a-85b1-4599-a342-fbf39830036b}"
[13:09:30.763] (WW) DAEMON: Failed to change owner of the auth file.
[13:09:30.834] (II) DAEMON: Greeter output: [13:09:30.833] (II) GREETER: High-DPI autoscaling not Enabled

[13:09:31.071] (II) DAEMON: Greeter output: [13:09:31.071] (II) GREETER: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"

[13:09:31.072] (II) DAEMON: Greeter output: [13:09:31.071] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop"

[13:09:31.072] (II) DAEMON: Greeter output: [13:09:31.072] (II) GREETER: Reading from "/usr/share/xsessions/xfce.desktop"

[13:09:31.072] (II) DAEMON: Greeter output: [13:09:31.072] (II) GREETER: Reading from "/usr/share/xsessions/xwmconfig.desktop"

[13:09:31.073] (II) DAEMON: Greeter output: [13:09:31.073] (II) GREETER: Reading from "/usr/share/xsessions/z_plasma-safe.desktop"

[13:09:31.075] (II) DAEMON: Greeter output: [13:09:31.075] (II) GREETER: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"

[13:09:31.124] (II) DAEMON: Greeter output: [13:09:31.124] (II) GREETER: Connected to the daemon.

[13:09:31.124] (II) DAEMON: Message received from greeter: Connect
[13:09:31.417] (II) DAEMON: Greeter output: [13:09:31.417] (II) GREETER: Loading file:///usr/share/sddm/themes/breeze/Main.qml...

[13:09:33.152] (II) DAEMON: Greeter output: [13:09:33.152] (II) GREETER: Adding view for "default" QRect(0,0 800x600)

[13:09:34.136] (II) DAEMON: Greeter output: [13:09:34.136] (WW) GREETER: Hunspell dictionary is missing for "fr_FR" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts")

[13:09:34.136] (II) DAEMON: Greeter output: [13:09:34.136] (II) GREETER: Message received from daemon: Capabilities

[13:09:34.136] (II) DAEMON: Greeter output: [13:09:34.136] (II) GREETER: Message received from daemon: HostName

^C[13:10:54.417] (WW) DAEMON: Signal received: SIGINT
[13:10:54.419] (II) DAEMON: Greeter stopping...
[13:10:54.475] (II) DAEMON: Greeter stopped.
[13:10:54.475] (II) DAEMON: Socket server stopping...
[13:10:54.476] (II) DAEMON: Socket server stopped.
[13:10:54.476] (II) DAEMON: Display server stopping...
[13:10:54.476] (II) DAEMON: Display server stopped.
[13:10:54.476] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"

So why can I launch that as a normal user and root cannot at boot ?

mikezt · 06-10-2021, 03:00 PM

I have the same problem on a A13 tablet. SDDM stop at "Logind interface found". I found a workaround:

Quote:

/etc/rc.d/rc.messagebus restart
killall sddm

So I believe there's a problem with D-Bus.