SDDM not working at XFCE

0XBF · 05-26-2022, 08:25 AM

So you are auto-logging in with sddm, to start a cinnamon/wayland session, on an nvidia gpu?

Code:

[20:03:32.382] (II) HELPER: Starting: "/usr/share/sddm/scripts/wayland-session cinnamon-session-cinnamon"

Why not try disabling the autologin? Then you can select the other stock options for your desktop session and see if they start properly (basically what enorbet suggested a few posts back). Also, if the sddm screen loads and you can select options, then sddm is eliminated from the equation.

If regular sddm and a stock desktop work, then try cinnamon and/or wayland if thats what you're trying to run. Once you get that working, then autologin. I'm just trying to eliminate the possibility it's cinnamon exiting for its own reason, or an issue with wayland+nvidia (happens a lot), or an issue with your autologin configuration.

Gordie · 05-26-2022, 07:45 PM

I first started using autologin with Slackware 14.2 and had to spend a lot of time with DDG search engine to find what I needed to know.

It appears that not everyone has success with it. For some users you make the changes and the settings are not stored and no matter how mahy times you go back to change it to what you want the settings refuse to store with the gui. I had to find the file to change with a text editor. With Slackware post 15.0 Current the file is /etc/sddm.conf.d/kde_settings.conf

Try editing this file and see if you can't make it work for you

SunnyJim · 05-26-2022, 11:32 PM

well good news, i got it to work. In /etc/sddm.conf i un-commented Username for autologin session "User=dave" to "User=" and that did it! Yes disable Autologin appeared to do the trick. Also i was able to select on the bottom left hand side of sddm login screen "x11 plasma session" and that worked too. Oddly enough plasma wayland did not work at all. Strange, but then again i was told of possible difficulties with it. If anyone has any problems with sddm look at your sddm configuration file(s) first. Thanks guys.

SunnyJim · 05-27-2022, 10:47 PM

well i have some more up to date news. I managed to get it to work on 1 of my machines but not the other using the same /etc/sddm.conf file. Actually managed to get the second to comment on the logfile but after a bit of work the greeter would not fire up anymore. Anyhow the sddm.log file is attached for view. Maybe some one has some suggestions or comments that could be helpful. Seems like a really picky application.

enorbet · 05-28-2022, 09:38 AM

Upon a cursory view I'd say look at QT install and anything related to Wayland. If you aren't using Wayland it might be a wise start to eliminate it... certainly disable it. If you want to use Wayland, it is substantially more complex. I'd pick either Xorg or Wayland, not both on toggle. As for QT, I can't recall if it was you that doesn't install KDE Plasma. If it was you, I suggest installing it. You don't have to run it. It will only cost you some storage space and make your life easier in recompense.

LuckyCyborg · 05-28-2022, 09:50 AM

Quote:

Originally Posted by enorbet

Upon a cursory view I'd say look at QT install and anything related to Wayland. If you aren't using Wayland it might be a wise start to eliminate it... certainly disable it. If you want to use Wayland, it is substantially more complex. I'd pick either Xorg or Wayland, not both on toggle. As for QT, I can't recall if it was you that doesn't install KDE Plasma. If it was you, I suggest installing it. You don't have to run it. It will only cost you some storage space and make your life easier in recompense.

You can NOT remove Wayland because it's linked with many things. But, it's enough to leave it alone.

Anyway, it's not a surprise that Wayland/Plasma5 may not work with the NVIDIA blob - even when it works, it needs special settings of NVIDIA kernel modules.

enorbet · 05-28-2022, 11:42 AM

Well LuckyCyborg I probably should've explained better but by "eliminate" I didn't mean "delete". I meant make certain no Wayland scripts are executable and for good measure remove it from the SDDM Chooser menu. SunnyJim's most recent sddm.log has several Errors and Warnings and most of them are either Wayland or QT related. It seems prudent to solve those issues, often by disabling any calls for them in the case of Wayland, and solving any QT issues. One "W" was for "could not connect to display" and that's a deal breaker right there. IMHO the first important solution and possibly connected to Wayland init script. In any case, that seems the first step.

LuckyCyborg · 05-28-2022, 12:40 PM

Quote:

Originally Posted by enorbet

Well LuckyCyborg I probably should've explained better but by "eliminate" I didn't mean "delete". I meant make certain no Wayland scripts are executable and for good measure remove it from the SDDM Chooser menu. SunnyJim's most recent sddm.log has several Errors and Warnings and most of them are either Wayland or QT related. It seems prudent to solve those issues, often by disabling any calls for them in the case of Wayland, and solving any QT issues. One "W" was for "could not connect to display" and that's a deal breaker right there. IMHO the first important solution and possibly connected to Wayland init script. In any case, that seems the first step.

Man, no Wayland script is executed by SDDM when is activated a X11 session. There are even different session log files:

~/.local/share/sddm/wayland-session.log
~/.local/share/sddm/xorg-session.log

Also, the SDDM version shipped by Slackware until now is an X11 application, it has no business with Wayland or whatever associated scripts. I suggest to not mess with the Wayland scripts.

BTW, the file /var/log/sddm.log is the SDDM's engine and greeter log. Again, no Wayland session scripts are executed while in greeter.

enorbet · 05-28-2022, 12:57 PM

LuckyCyborg - I'm not saying a Slackware system initiates any Wayland script when an X11 session is activated but from SunnyJim's sddm.log

Code:

[14:09:35.621] (EE) GREETER: Failed to create wl_display (No such file or directory)
[14:09:35.622] (II) GREETER: Could not load the Qt platform plugin "wayland" in "" even though it was found.

This appears to be a problem BEFORE any X11 session is chosen, simply when SDDM is launched from CLI, No? I don't use Wayland at all so it may even be likely that I am mistaken, but it seems wise to eliminate variables that fail to narrow the field at the very least.

LuckyCyborg · 05-28-2022, 01:26 PM

Quote:

Originally Posted by enorbet

LuckyCyborg - I'm not saying a Slackware system initiates any Wayland script when an X11 session is activated but from SunnyJim's sddm.log

Code:

[14:09:35.621] (EE) GREETER: Failed to create wl_display (No such file or directory)
[14:09:35.622] (II) GREETER: Could not load the Qt platform plugin "wayland" in "" even though it was found.

This appears to be a problem BEFORE any X11 session is chosen, simply when SDDM is launched from CLI, No? I don't use Wayland at all so it may even be likely that I am mistaken, but it seems wise to eliminate variables that fail to narrow the field at the very least.

Huh? A successful SDDM greeter screen with login to a X11/Plasma5 session looks like this:

Code:

[21:15:05.091] (II) DAEMON: Initializing...
[21:15:05.098] (II) DAEMON: Starting...
[21:15:05.098] (II) DAEMON: Logind interface found
[21:15:05.099] (II) DAEMON: Adding new display on vt 7 ...
[21:15:05.102] (II) DAEMON: Loading theme configuration from ""
[21:15:05.102] (II) DAEMON: Display server starting...
[21:15:05.102] (II) DAEMON: Adding cookie to "/var/run/sddm/{30518f1b-531d-4b89-9964-a8aa40f289ce}"
[21:15:05.107] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{30518f1b-531d-4b89-9964-a8aa40f289ce} -background none -noreset -displayfd 17 -seat seat0 vt7
[21:15:05.878] (II) DAEMON: Setting default cursor
[21:15:05.934] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[21:15:05.978] (II) DAEMON: Display server started.
[21:15:05.978] (II) DAEMON: Socket server starting...
[21:15:05.978] (II) DAEMON: Socket server started.
[21:15:05.979] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[21:15:05.979] (II) DAEMON: Greeter starting...
[21:15:05.999] (II) HELPER: [PAM] Starting...
[21:15:05.999] (II) HELPER: [PAM] Authenticating...
[21:15:05.999] (II) HELPER: [PAM] returning.
[21:15:06.010] (II) DAEMON: Greeter session started successfully
[21:15:06.150] (II) DAEMON: Message received from greeter: Connect
[21:15:18.536] (II) DAEMON: Message received from greeter: Login
[21:15:18.536] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[21:15:18.537] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[21:15:18.537] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "dbus-run-session /usr/bin/startplasma-x11"
[21:15:18.549] (II) HELPER: [PAM] Starting...
[21:15:18.549] (II) HELPER: [PAM] Authenticating...
[21:15:18.550] (II) HELPER: [PAM] Preparing to converse...
[21:15:18.550] (II) HELPER: [PAM] Conversation with 1 messages
[21:15:18.556] (II) HELPER: [PAM] returning.
[21:15:18.556] (II) DAEMON: Authenticated successfully
[21:15:18.617] (II) HELPER: [PAM] Closing session
[21:15:18.618] (II) HELPER: [PAM] Ended.
[21:15:18.619] (II) DAEMON: Auth: sddm-helper exited successfully
[21:15:18.619] (II) DAEMON: Greeter stopped.
[21:15:18.643] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"dbus-run-session /usr/bin/startplasma-x11\""
[21:15:18.645] (II) HELPER: Adding cookie to "/home/vanya/.Xauthority"
[21:15:18.649] (II) DAEMON: Session started
[21:15:45.032] (WW) DAEMON: Signal received: SIGTERM
[21:15:45.032] (II) DAEMON: Socket server stopping...
[21:15:45.032] (II) DAEMON: Socket server stopped.
[21:15:45.032] (II) DAEMON: Display server stopping...
[21:15:45.258] (II) DAEMON: Display server stopped.
[21:15:45.258] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[21:15:45.260] (WW) DAEMON: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.

Please note the PAM dialogs and the starting of X11/Plasma5 session.

However, in SunnyJim's sddm.log there are no PAM dialogs, and apparently the SDDM tries to execute a KODI session.

So, this guy tries to autologin to a KODI session? And no PAM in his system?

I would like to ask him if he messed with the LinuxPAM package and its friends - and what the heck is this KODI session.

And biggest question: is this a full installation of Slackware 15.0 ?

SunnyJim · 05-28-2022, 04:07 PM

I would say those are pretty good questions. First off i installed kodi from sbopkg along with its dependencies but as for why i have a kodi session i would not know. Also notice the qml errors
that keep cropping up? Oh and i reinstalled qt as well and it did not help (slackpkg reinstall qt5). And when i test out the sddm-greeter i always see a kodi-session in the bottom left hand corner
so that is another indicator of strangeness too. Perhaps if i specified a particular session it might help? Anyway i am attaching my sddm.conf file for examination as i tend to experiment with it.
And no i have not messed with pam if my memory serves me right, but who can say something might have gotten messed up along the way.

LuckyCyborg · 05-28-2022, 04:27 PM

Quote:

Originally Posted by SunnyJim

Anyway i am attaching my sddm.conf file for examination as i tend to experiment with it.

Where's this file?

SunnyJim · 05-28-2022, 07:30 PM

ah i thought i attached it. this should do it

LuckyCyborg · 05-29-2022, 02:09 AM

Quote:

Originally Posted by SunnyJim

ah i thought i attached it. this should do it

You talked about /etc/sddm.conf - the log file I seen already.

Anyway, usually there is NO need to customize the config file of SDDM. So, I suggest you to replace it with the stock file from package, it have the name /etc/sddm.conf.new and to remove any file (if exists) from directory /etc/sddm.conf.d

Also ensure that you run on runlevel 4, then reboot. And tell me what happen.

Another note: IF you arrive to final of booting and the screen still shows the console (and the boot message) try to use CTRL+ALT+F7 and tell me if there you find the greeter screen.

Also, be kind to tell what graphics card you have, which driver you use and IF your computer uses Optimus or any other similar solution.

For your convenience, I also here is the Slackware's stock /etc/sddm.conf contents

Code:

[Autologin]
# Whether sddm should automatically log back into sessions when they exit
Relogin=false

# Name of session file for autologin session (if empty try last logged in)
Session=

# Username for autologin session
User=


[General]
# Halt command
HaltCommand=/usr/bin/loginctl poweroff

# Input method module
InputMethod=qtvirtualkeyboard

# Comma-separated list of Linux namespaces for user session to enter
Namespaces=

# Initial NumLock state. Can be on, off or none.
# If property is set to none, numlock won't be changed
# NOTE: Currently ignored if autologin is enabled.
Numlock=none

# Reboot command
RebootCommand=/usr/bin/loginctl reboot


[Theme]
# Current theme name
Current=breeze

# Cursor theme used in the greeter
CursorTheme=

# Number of users to use as threshold
# above which avatars are disabled
# unless explicitly enabled with EnableAvatars
DisableAvatarsThreshold=7

# Enable display of custom user avatars
EnableAvatars=true

# Global directory for user avatars
# The files should be named <username>.face.icon
FacesDir=/usr/share/sddm/faces

# Font used in the greeter
Font=

# Theme directory path
ThemeDir=/usr/share/sddm/themes


[Users]
# Default $PATH for logged in users
DefaultPath=/usr/local/bin:/usr/bin:/bin

# Comma-separated list of shells.
# Users with these shells as their default won't be listed
HideShells=

# Comma-separated list of users that should not be listed
HideUsers=

# Maximum user id for displayed users
MaximumUid=60000

# Minimum user id for displayed users
MinimumUid=1000

# Remember the session of the last successfully logged in user
RememberLastSession=true

# Remember the last successfully logged in user
RememberLastUser=true

# When logging in as the same user twice, restore the original session, rather than create a new one
ReuseSession=true


[Wayland]
# Enable Qt's automatic high-DPI scaling
EnableHiDPI=false

# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/wayland-session

# Directory containing available Wayland sessions
SessionDir=/usr/share/wayland-sessions

# Path to the user session log file
SessionLogFile=.local/share/sddm/wayland-session.log


[X11]
# Path to a script to execute when starting the display server
DisplayCommand=/usr/share/sddm/scripts/Xsetup

# Path to a script to execute when stopping the display server
DisplayStopCommand=/usr/share/sddm/scripts/Xstop

# Enable Qt's automatic high-DPI scaling
EnableHiDPI=false

# The lowest virtual terminal number that will be used.
MinimumVT=7

# Arguments passed to the X server invocation
ServerArguments=-nolisten tcp

# Path to X server binary
ServerPath=/usr/bin/X

# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/Xsession

# Directory containing available X sessions
SessionDir=/usr/share/xsessions

# Path to the user session log file
SessionLogFile=.local/share/sddm/xorg-session.log

# Path to the Xauthority file
UserAuthFile=.Xauthority

# Path to xauth binary
XauthPath=/usr/bin/xauth

# Path to Xephyr binary
XephyrPath=/usr/bin/Xephyr

SunnyJim · 05-29-2022, 12:40 PM

ok i did as you asked an replaced my sddm.conf with the one you specified and there is no /etc/sddm.conf.d directory either and all i obtained was a console as before. CTRL+ALT+F7 yields the same console as well. I have an geforce rtx 2060 video card in a pci-e slot that is using sbopkg nvidia kernel and multilib driver. No i do not use optimus my system is an msi mag b550 tomahawk. In sddm.log the greeter
is still not active and i am considering reinstalling slackware 15 on a solid state usb3.1 nvme drive to see if that will work as i am beginning to suspect pam is borked or maybe even hacked.