OK this is what I did:-
Rebooted to start over. My default display manager is already set to SDDM.
At login screen selected X11 desktop which failed to log in.
Ctrl + Alt + F3 to get to VT and logged in.
Ran command:-
sudo journalctl -b | egrep "sddm|plasma" > out.log
ran startx to get back to dektop gui. (Couldn’t get back from VT Ctrl + Alt +F7?)
Saved out.log on susepaste and here it is:-
Ok, that’s good.
I note the following occurs…
Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: Starting X11 session: "" "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Session started false
Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Closing session
Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Ended.
Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Auth: sddm-helper exited with 2
In a working situation something like the following should be reported…
Sep 16 21:23:02 linux-lptp1 sddm-helper[1438]: Starting X11 session: "" "/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
Sep 16 21:23:02 linux-lptp1 sddm[998]: Session started true
Sep 16 21:23:02 linux-lptp1 sddm-helper[1172]: [PAM] Closing session
Sep 16 21:23:02 linux-lptp1 sddm-helper[1172]: pam_unix(sddm-greeter:session): session closed for user sddm
Sep 16 21:23:02 linux-lptp1 sddm-helper[1172]: pam_kwallet5(sddm-greeter:session): pam_kwallet5: pam_sm_close_session
Sep 16 21:23:02 linux-lptp1 sddm-helper[1172]: [PAM] Ended.
Sep 16 21:23:02 linux-lptp1 sddm[998]: Auth: sddm-helper exited successfully
Sep 16 21:23:02 linux-lptp1 sddm[998]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Please also show
cat /var/lib/sddm/state.conf
OK, I did this from console and saved to a file but here is the text:-
[Last]
# Name of the last logged-in user.
# This user will be preselected when the login screen appears
User=alastair
# Name of the session for the last logged-in user.
# This session will be preselected when the login screen appears.
Session=/usr/share/xsessions/plasma5.desktop
That checks out as expected.
Do you have a configuration in /etc/sddm.conf.d/kde_settings.conf?
Also, anything reported in your user’s ~/.local/share/sddm/xorg-session.log?
Hi, in short no and no!
alastair@HP-Z640-1:~> cd /etc/sddm.conf.d/
alastair@HP-Z640-1:/etc/sddm.conf.d> ls
alastair@HP-Z640-1:/etc/sddm.conf.d> ls -l
total 0
alastair@HP-Z640-1:/etc/sddm.conf.d> cd ~/.local/share/sddm
alastair@HP-Z640-1:~/.local/share/sddm> ls
wayland-session.log xorg-session.log
alastair@HP-Z640-1:~/.local/share/sddm> ls
wayland-session.log xorg-session.log
alastair@HP-Z640-1:~/.local/share/sddm> cat xorg-session.log
alastair@HP-Z640-1:~/.local/share/sddm> cat xorg-session.log
alastair@HP-Z640-1:~/.local/share/sddm>
I think submitting a bug report is needed here…
https://bugzilla.opensuse.org/index.cgi
Hi Dean,
Well I have tried to post a bug. Not too familiar with process or protocol but here it is:-
https://bugzilla.opensuse.org/show_bug.cgi?id=1215403
I am hoping you can edit and add important info as my initial post will no doubt show my ignorance!
And of course many thanks.
@Budgie2 It reads ok. You will be asked for more info as/when they require it.
Upstream SDDM apparently decided VT7 is no longer a proper place to run X sessions. Try F2 next time. I’ve eliminated SDDM from all but two of my many Plasma installations.
Many thanks. Out of interest which would be your preferred DM on TW KDM system.
I am not sure if I should jump ship just yet but would be good to know.
I posted a very modest bug report so it is not likely to receive a high priority. What surprises me is that so few have this problem.
Thanks for the help again,
Alastair.
@Budgie2 I’m a die hard GNOME/GDM user on Tumbleweed… 
For MicroOS/Hyprland, it’s TTY1 and use a script to fire it up…
if [ -z "${DISPLAY}" ] && [ "${XDG_VTNR}" == 1 ]; then
exec Hyprland > /dev/null 2>&1
fi
It’s been the same for more than 20 years, since before my first installation of SUSE 8.0: KDM, which I had been using in Mandrake, just not from OSS any more since KDE4 was embraced by the the distro. Its default theme, selected by configuring null for theme, is intelligently compact, using only the center portion of the screen where the mouse pointer initially appears for the few objects any DM need provide. Its configuration file kdmrc by default is over 22k, incorporating annotation of its massive configurability.
Fedora users can still get it from standard repos, which still provides an ancient X11/Xorg server 1.20.14, only .01 newer than 15.4’s.
Hi and thanks for this. I too started with SUSE 8.0. I might still have the original box somewhere but I am not a coder, just had to find a replacement for OS2 and then Warp 4 when it all eventually went sour due to licence dispute with M$.
I would like to try reverting to KDM with X11 but how do I go about this without creating more problems please? I get a dependency problem when I try and install.
Nothing provides libDCOP.so.4()(64bit)
Are you trying to install with something other than zypper? If:
# rpm -qf /opt/kde3/lib64/libDCOP.so.4
kdelibs3-3.5.10-lp155.264.1.x86_64
#doesn’t help I’ll check in TW later.
I was using Yast to install. All went well but there is the one dependency cited. I asked before ignoring.
I tried zypper:-
sudo zypper in kdelibs3-3.5.10-lp155.264.1.x86_64
[sudo] password for root:
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
'kdelibs3-3.5.10-lp155.264.1.x86_64' not found in package names. Trying capabilities.
No provider of 'kdelibs3-3.5.10-lp155.264.1.x86_64' found.
Resolving package dependencies...
Nothing to do.
alastair@HP-Z640-1:~>
Zypper can’t find Leap packages in TW repos.
Makes sense but this suggests I should be moving back to Leap. Not what I wanted as the direction is towards TW in the future.
How should I proceed?
It certainly does not:
KDE3 repos
To be honest and to summarize your last threads:
In my humble opinion it would make sense to backup your important data and install a fresh and unaltered Tumbleweed. Your system is “grown” and was altered in so many ways that it is nearly impossible to trace a fault.
And the recommendation from mrmazda to install software from the KDE3 repo will blow up your system finaly. The KDE3 repo provides up to 17! years old package versions without any security or bugfixes. This alone is an absolute no-go! Using such unsecure software only “because i like the old look and i use it since 20 years” only shows the lack of understanding of basic IT security.
Even if it is technically possible to run 17 years old software on an up to date operating system is no reason to risk your security and privacy.
Maybe trinity is better than KDE3:
https://www.trinitydesktop.org/
https://wiki.trinitydesktop.org/OpenSUSE_Trinity_Repository_Installation_Instructions