I tried Tumbleweed a couple of days ago - snapshot20240819.
It installs well, but I cannot login as user. I can login as root.
If I go to [ctrl][alt][F1], I can login as user, and startx to start X11.
All my files are available in that mode.
Any clues how to get the login screen working? I don’t like to go the tty route everytime I boot.
Leap 15.6 works fine on the same configuration and I am back to that for now.
TIA,
Wai
PS. I run Asrock B650E Taichi Lite, AMD Ryzen 7800X3D, Radeon RX 7800 XT 16GB
Strange problem, maybe the journal is giving some hints on what is going on?
sudo journalctl -b
will give you the journal for your current boot. If you see something in it please share it in this topic, use the Prefromatted text button for formatting it.
Included the log should be the following - after fresh reboot
login as user wai - SuSE loginscreen X11 - failed as described in the original post
login as user wai in tty mode, generated the journalctl output. Succesful, but startx won’t work anymore, I get no graphical desktop, only a console in this snapshot.
Not included in the journal, but did execute before the fresh reboot:
login as root - SuSE loginscreen X11 - succesful
login as user wai - SuSE loginscreen Wayland - failed as described
I did try to login without password as per your instructions, but I can see no effect. I still have to enter a password in de SuSE loginscreen and the result is the same login-loop.
Thanks for the log, for those that want to have a look, do it fast, when writing only 22 hours left
I did copy the part that looks interesting:
systemd[1]: Created slice User Slice of UID 1000.
systemd[1]: Starting User Runtime Directory /run/user/1000...
systemd-logind[1375]: New session 3 of user wai.
systemd[1]: Finished User Runtime Directory /run/user/1000.
systemd[1]: Starting User Manager for UID 1000...
systemd-logind[1375]: New session 4 of user wai.
(systemd)[1977]: pam_unix(systemd-user:session): session opened for user wai(uid=1000) by wai(uid=0)
(systemd)[1977]: pam_kwallet5(systemd-user:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this.
sddm-helper[1758]: [PAM] Closing session
sddm-helper[1758]: pam_systemd(sddm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1758) opened.
sddm-helper[1758]: pam_unix(sddm-greeter:session): session closed for user sddm
sddm-helper[1758]: pam_kwallet5(sddm-greeter:session): pam_kwallet5: pam_sm_close_session
sddm-helper[1758]: [PAM] Ended.
sddm[1561]: Auth: sddm-helper exited successfully
systemd[1]: session-1.scope: Deactivated successfully.
sddm[1561]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
systemd-logind[1375]: Session 1 logged out. Waiting for processes to exit.
systemd-logind[1375]: Removed session 1.
systemd-xdg-autostart-generator[1985]: Configuration file /home/wai/.config/autostart/nordvpnstart.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
systemd-xdg-autostart-generator[1985]: Configuration file /home/wai/.config/autostart/basket.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
systemd-xdg-autostart-generator[1985]: Configuration file /home/wai/.config/autostart/viridi.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
systemd[1977]: Queued start job for default target Main User Target.
systemd[1977]: Created slice User Application Slice.
systemd[1977]: Started Submitting pending crash events (file monitor).
systemd[1977]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/wai/.cache/kcrash-metadata/*.ini).
systemd[1977]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/wai/.cache/drkonqi/sentry-envelopes/*).
systemd[1977]: Started Daily Cleanup of User's Temporary Directories.
systemd[1977]: Reached target Paths.
systemd[1977]: Reached target Timers.
systemd[1977]: Starting D-Bus User Message Bus Socket...
systemd[1977]: Listening on Socket to launch DrKonqi for a systemd-coredump crash.
systemd[1977]: Listening on PipeWire PulseAudio.
systemd[1977]: Listening on PipeWire Multimedia System Sockets.
systemd[1977]: Starting Create User Files and Directories...
systemd[1977]: Listening on D-Bus User Message Bus Socket.
systemd[1977]: Reached target Sockets.
systemd[1977]: Finished Create User Files and Directories.
systemd[1977]: Reached target Basic System.
systemd[1977]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/wai/.cache/kcrash-metadata/*.ini).
systemd[1977]: Reached target Main User Target.
systemd[1977]: Startup finished in 602ms.
systemd[1]: Started User Manager for UID 1000.
systemd[1]: Started Session 3 of User wai.
sddm-helper[1959]: pam_unix(sddm:session): session opened for user wai(uid=1000) by wai(uid=0)
sddm-helper[1959]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
sddm-helper[1992]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
sddm-helper[1959]: Writing cookie to "/tmp/xauth_IdgSTX"
sddm-helper[1959]: Starting X11 session: "" "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
sddm[1561]: Session started true
sddm-helper[1959]: Failed to write utmpx: No such file or directory
systemd[1977]: Created slice User Core Session Slice.
systemd[1977]: Starting D-Bus User Message Bus...
systemd[1977]: Started D-Bus User Message Bus.
dbus-daemon[2006]: [session uid=1000 pid=2006] Successfully activated service 'org.freedesktop.systemd1'
sddm-helper[1959]: [PAM] Closing session
sddm-helper[1959]: pam_systemd(sddm:session): New sd-bus connection (system-bus-pam-systemd-1959) opened.
sddm-helper[1959]: pam_unix(sddm:session): session closed for user wai
sddm-helper[1959]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
sddm-helper[1959]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
sddm-helper[1959]: Failed to write utmpx: No such file or directory
sddm-helper[1959]: [PAM] Ended.
sddm[1561]: Auth: sddm-helper exited with 127
sddm[1561]: Socket server stopping...
sddm[1561]: Socket server stopped.
sddm[1561]: Display server stopping...
systemd-logind[1375]: Session 3 logged out. Waiting for processes to exit.
systemd[1]: systemd-hostnamed.service: Deactivated successfully.
sddm[1561]: Display server stopped.
sddm[1561]: Running display stop script QList("/usr/share/sddm/scripts/Xstop")
sddm[1561]: Removing display SDDM::Display(0x5613f37966a0) ...
So the (graphical) login looks successful but “Auth: sddm-helper exited with 127” is what I think is the cause of the problem.
I did check “sddm-helper[1959]: Failed to write utmpx: No such file or directory” but I see that also in my boot log so I think that is not what is causing the problem.
Based on “Configuration file /home/wai/.config/autostart/nordvpnstart.sh is marked executable.” I think this is no clean install but one where you re-use home from a previous install and I think that could somehow triggering the problem, some old setting is causing havoc.
You’re right, I did keep my /home directory, as I always do when installing fresh. Actually, I have been running openSuSE for over 20 years now as my daily driver, and my /home partition has always moved along. Left Windows for over a decade ago and I’m not looking back.
There have been very few problems moving up the 10.x to the now current LEAP generation up to 15.6. But I can understand that the jump from Leap 15.6 to Tumbleweed runs into a conflict in the configuration.
I will try to reconstruct my /home directory while taking out the offending conflicts by cleaning ./config first. Starting with the problem that you pointed out and maybe cleaning .kde etc.
Thanks again and will let you know if it works out or not.
I haven’t looked at the logs you provided.
EDIT: and deleting ~/.config is a bit extreme at this point.
However, it’s not uncommon for Wayland to cause problems for many people (personally, we don’t feel its mature enough, so avoid using it).
Change the DE configuration to use X11 and not Wayland.
Does it work now? (for may folks, things suddenly work with X11).
Kind of ironic … we’ve been using TW for a long time on all machines, but have switched to Leap 15.6, because we got tired of constantly running zypper dup and having to deal with xxxx problem or yyyy problem.
Thanks both of you for your replies,
I made some progress.
Firstly, I agree that Wayland is almost good enough for my use, but just not there yet.
ATM it distorts my dual screen layout when using citrix. Other than that it seems to work well. As I need the citrix interface for some work that I do, it will have to be X11 for now.
Back to Tumbleweed; I created a new user and was able to logon.
Then I copied all of my /home data to that user and made it the owner and all.
Again I was not able to logon. After several tries to pinpoint the problem, I just deleted everything in .config en .KDE that I could find.
Still no joy. As I have to move on with some work ahead, I had to reinstall Leap 15.6 again. I will revisit Tumbleweed again in a couple of weeks, next stop is creating a new user and copy only the personal stuff, not excluding .kde etc.
If all else fails, it is very true that 15.6 works nice, and I can wait if I have to. OpenSuSE has always been a stable environment. Maybe one exception (was it 10.2 or 10.3)?
