After a zypper dup upgrade which required a re-boot I was not able to log in to my normal X11 desktop.
I switched to Wayland and now I can log in.
Glad I was able to continue work but wish to understand why I had a problem with X11.
Now I have a new (to me) graphics adaptor Radeon Pro WX7100 I have no reason not to continue with Plasma Wayland since it all seems to work but should I now give up on X11 and move with the times?
With this non existing amount of information it may be hard to tell why you cam’t login. Did you check the journal already?
This is what I have from a quick check:-
alastair@HP-Z640-1:~> journalctl -r -b -1
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Reached target Exit the Session.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Finished Exit the Session.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Reached target Shutdown.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Removed slice User Application Slice.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped Create User's Volatile Files and Directories.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Closed Sound System.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Closed PipeWire Multimedia System Socket.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Closed D-Bus User Message Bus Socket.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped Daily Cleanup of User's Temporary Directories.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped target Timers.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped target Sockets.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped target Paths.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped target Basic System.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Stopped target Main User Target.
Sep 04 18:43:45 HP-Z640-1 systemd[2014]: Activating special unit Exit the Session...
Sep 04 18:43:10 HP-Z640-1 sddm-helper[2028]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Startup finished in 289ms.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Reached target Main User Target.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Reached target Basic System.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Reached target Sockets.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Listening on D-Bus User Message Bus Socket.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Finished Create User's Volatile Files and Directories.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Starting Create User's Volatile Files and Directories...
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Listening on Sound System.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Listening on PipeWire Multimedia System Socket.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Starting D-Bus User Message Bus Socket...
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Reached target Timers.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Reached target Paths.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Started Daily Cleanup of User's Temporary Directories.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Created slice User Application Slice.
Sep 04 18:43:10 HP-Z640-1 systemd[2014]: Queued start job for default target Main User Target.
Sep 04 18:43:09 HP-Z640-1 systemd-xdg-autostart-generator[2021]: /home/alastair/.config/autostart/minimwatch.desktop: not generating unit, >
Sep 04 18:43:09 HP-Z640-1 systemd-xdg-autostart-generator[2021]: Exec binary '/home/alastair/Downloads/minimwatch/bin/starti' does not exis>
Sep 04 18:43:09 HP-Z640-1 systemd-xdg-autostart-generator[2021]: Configuration file /home/alastair/.config/autostart/minimwatch.desktop is >
lines 4-34/34 (END)
Could it be that minimwatch line stopped the login process? Doesn’t seem likely. Am I using inadequate journalctl command?
Might try:
Switch to runlevel 3 (or 2 or 1 if preferred)
Delete the contents of ~/.cache
Switch to runlevel 5
Any change / improvement?
OK, I though my problem was because I had changed my graphics adaptor from Nvidia to AMD and not removed the Nvidia starting modules. Having removed all Nvidia files from my system I still cannot login using the X11 desktop.
The only way I can get in (because I am not sufficiently knowledgeable on commands required,) is to set the desktop to X11 at the login screen, when I cannot then login. Then reboot and start init 3, login on cli and then run startx. This gets me into my desktop with X11 running.
So how do I diagnose why my normal desktop login fails and correct the problem? Here is what I have from my last boot check:-
Sep 07 20:01:29 HP-Z640-1 systemd[1850]: Activating special unit Exit the Session...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Start request repeated too quickly.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 6.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Start request repeated too quickly.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 6.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 kwin_x11[3010]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl,>
Sep 07 20:01:28 HP-Z640-1 kwin_x11[3010]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[3009]: This application failed to start because no Qt platform plugin could be initialized. Re>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wa>
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[3009]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was fou>
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting KDE Window Manager...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 5.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting Powerdevil...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 5.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 kwin_x11[3001]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl,>
Sep 07 20:01:28 HP-Z640-1 kwin_x11[3001]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[3000]: This application failed to start because no Qt platform plugin could be initialized. Re>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wa>
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[3000]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was fou>
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting KDE Window Manager...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 4.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting Powerdevil...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 4.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 kwin_x11[2993]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl,>
Sep 07 20:01:28 HP-Z640-1 kwin_x11[2993]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[2994]: This application failed to start because no Qt platform plugin could be initialized. Re>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wa>
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[2994]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was fou>
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting Powerdevil...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting KDE Window Manager...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 3.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 3.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start KDE Window Manager.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 kwin_x11[2986]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl,>
Sep 07 20:01:28 HP-Z640-1 kwin_x11[2986]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Failed to start Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[2987]: This application failed to start because no Qt platform plugin could be initialized. Re>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wa>
Sep 07 20:01:28 HP-Z640-1 org_kde_powerdevil[2987]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was fou>
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Starting Powerdevil...
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: Stopped Powerdevil.
Sep 07 20:01:28 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 2.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Starting KDE Window Manager...
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Stopped KDE Window Manager.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 2.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Failed to start Powerdevil.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 org_kde_powerdevil[2978]: This application failed to start because no Qt platform plugin could be initialized. Re>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wa>
Sep 07 20:01:27 HP-Z640-1 org_kde_powerdevil[2978]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was fou>
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Failed to start KDE Window Manager.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 kwin_x11[2976]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl,>
Sep 07 20:01:27 HP-Z640-1 kwin_x11[2976]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Starting Powerdevil...
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Stopped Powerdevil.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Starting KDE Window Manager...
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Consumed 1.205s CPU time.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Stopped KDE Window Manager.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 1.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: app-pcloud@autostart.service: Consumed 9.268s CPU time.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: app-pcloud@autostart.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kded.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kded.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: app-pcloud@autostart.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 kded5[2004]: kf.notifications: Playing audio notification failed: Destroyed
Sep 07 20:01:27 HP-Z640-1 kded5[2004]: X connection to :0 broken (explicit kill or server shutdown).
Sep 07 20:01:27 HP-Z640-1 kded5[2004]: kf.notifications: Had queued notifications on destruction. Was the eventloop running?
Sep 07 20:01:27 HP-Z640-1 kded5[2004]: The X11 connection broke: I/O error (code 1)
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Consumed 1.205s CPU time.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: app-kaccess@autostart.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: app-kaccess@autostart.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 20:01:27 HP-Z640-1 kwin_x11[2005]: X connection to :0 broken (explicit kill or server shutdown).
Sep 07 20:01:27 HP-Z640-1 kwin_x11[2005]: The X11 connection broke: I/O error (code 1)
Sep 07 20:01:27 HP-Z640-1 pcloud[2259]: fuse: reading device: Bad file descriptor
Sep 07 20:01:27 HP-Z640-1 pcloud[2259]: fuse: writing device: Bad file descriptor
Sep 07 20:01:27 HP-Z640-1 kaccess[2271]: The X11 connection broke (error 1). Did the X11 server die?
Sep 07 20:01:27 HP-Z640-1 at-spi-bus-launcher[2328]: X connection to :0 broken (explicit kill or server shutdown).
Sep 07 20:01:27 HP-Z640-1 kscreen_backend_launcher[2208]: The X11 connection broke (error 1). Did the X11 server die?
Sep 07 20:01:27 HP-Z640-1 xdg-desktop-portal-kde[2125]: The X11 connection broke (error 1). Did the X11 server die?
Sep 07 20:01:27 HP-Z640-1 org_kde_powerdevil[2124]: The X11 connection broke (error 1). Did the X11 server die?
Sep 07 20:01:27 HP-Z640-1 kactivitymanagerd[2090]: The X11 connection broke (error 1). Did the X11 server die?
Sep 07 20:01:27 HP-Z640-1 kded5[2060]: X connection to :0 broken (explicit kill or server shutdown).
Sep 07 20:01:27 HP-Z640-1 kglobalaccel5[2032]: after 8 requests (8 known processed) with 0 events remaining.
Sep 07 20:01:27 HP-Z640-1 kglobalaccel5[2032]: XIO: fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Sep 07 20:01:27 HP-Z640-1 kglobalaccel5[2032]: The X11 connection broke: I/O error (code 1)
Sep 07 20:01:27 HP-Z640-1 kglobalaccel5[2032]: The X11 connection broke (error 1). Did the X11 server die?
Sep 07 20:01:27 HP-Z640-1 dbus-daemon[1930]: [session uid=1000 pid=1930] Activating service name='org.freedesktop.Notifications' requested >
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: app-org.kde.kalendarac@autostart.service: Consumed 9.089s CPU time.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Stopped target Startup of XDG autostart applications.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.>
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is >
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Stopped target KDE Plasma Workspace.
Sep 07 20:01:27 HP-Z640-1 systemd[1850]: Stopped target plasma-workspace-x11.target.
Sep 07 20:01:27 HP-Z640-1 akonadi_control[2431]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
Sep 07 20:01:24 HP-Z640-1 akonadi_control[2431]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_mailfilter_agent' exited normall>
Sep 07 20:01:24 HP-Z640-1 akonadi_control[2431]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_mailmerge_agent' exited normally>
Sep 07 20:01:24 HP-Z640-1 akonadi_control[2431]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_indexing_agent' exited normally.>
Sep 07 20:01:24 HP-Z640-1 akonadi_control[2431]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_ical_resource' exited normally...
Sep 07 20:01:24 HP-Z640-1 akonadi_control[
This is only a part but enough red print to draw attention to a possible problem.
I don’t know if this applies, but i had a similar problem with sddm and autologin. After I switched to lightdm everything worked again.
On reading further I believe the problem is with:-
plasma-kwin_x11.service
I see that others have had a problem and it may be due to the the transition to Plasma (Wayland) and a possible but. Although Wayland does work as required I would prefer to stay with X11 until I learn more about this change. Can anybody please help me fix this?
FYI here is my existing graphics system:-
Graphics:
Device-1: AMD Ellesmere [Radeon Pro WX 7100] vendor: Dell driver: amdgpu
v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20
pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-4
empty: DP-1,DP-2,DP-3 bus-ID: 02:00.0 chip-ID: 1002:67c4 class-ID: 0300
temp: 46.0 C
Display: server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.0
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: radeonsi gpu: amdgpu tty: 140x32
Monitor-1: DP-4 model: Asus PB258 serial: <filter> built: 2015
res: 2560x1440 dpi: 118 gamma: 1.2 size: 553x311mm (21.77x12.24")
diag: 634mm (25") ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL Message: GL data unavailable in console for root.
Should be able to select X11 on the login screen. IMO Wayland is still beta
That’s exactly my opinion. I never consider Wayland. Folks stress to get it running, but for what “advantage”. None, that I can think of.
VSync and VRR out of the box 
… I didn’t have any problems switching to wayland, but I guess it is another story if you’ve used x11 for years. It’s the same story as pulseaudio vs pipewire all over again 
Meaning what? Are you a Gnome user? Gamer? Remote login user?
Hi and yes I can select X11 on the login screen but thanks for reminding me.
My problem is that I cannot log in but get the login box again.
I have not had exactly the same problem before. It appears my system now defaults to Plasma (Wayland) which works without a hitch but until I have learned more about Wayland, you may recall it has only just been available on openSUSE, I would like to be able to choose which desktop.
If I log in at runlevel 3 and then start X11 all is as usual but the login does not work from the login graphics screen.
Since I can log in with Plasma Wayland without any problems I cannot justify ask for help but after some time looking through /var/log/xorg.0.log and cat/var/log/messages I cannot find any obvious error.
As a TW user, not a coder, my problem apart from the huge volume of data to read, is that I am not sure where to look for the problem although the login does seem to be missing some info.
I do draw two conclusions however; TW now defaults to the Plasma (Wayland) desktop and X11 does work, albeit slow at times, if I start X11 after I have logged in.
I have been struggling understanding the differences between window managers and display servers and why I have references to GDM and SDDM and KWin and Wayland and Xorg all appearing in my log files. Too difficult for me but it does appear that what I am using is a hybrid between old and new systems and my login using X11 fails because of a bug and not because I have made an error.
It would be helpful to learn more, if only so I know where to look to solve my problem but hopefully others will have come across this issue and explain in the fullness of time.
Can a virgin user log into a Plasma/X11 session without reproducing the problem? “Is it only happening to me?” is usually the first troubleshooting question that needs answering.
@Budgie2 The SDDM desktop greeter remembers the last DE session, so if you don’t try forcing the selection it will launch the same environment as last login.
Try creating another user while in the Wayland session, then logout, choose Plasma X11 and log in as the new user. Does that result in a working Plasma X11 desktop session?
Hi and thanks for the suggestion. I had tried this before posting anything at the start of this thread but tried again just to be sure. Even with a virgin user I cannot log in using X11. I get the same response but thanks for coming back to me.
I have switched back to my original user to post this.
Anything else unintentionally removed?
Maybe check back via…
sudo cat /var/log/zypp/history | grep -i remove@Budgie2 You have also removed any old xorg.conf file related to Nvidia and installed the relevant amdgpu x86 files?
Hi Dean,
It is quite possible that my enthusiastic house cleaning has removed something I shouldn’t have but I am not sure what I am looking for. It all looks OK to me other than it has probably included some zypper dup activity. Here is part of what I have from date when I put in the new card:-
2023-08-25 02:27:47|remove |ruby2.5|2.5.9-150000.4.26.1|x86_64||
2023-08-25 02:27:47|remove |ruby2.5-stdlib|2.5.9-150000.4.26.1|x86_64||
2023-08-25 02:27:47|remove |libruby2_5-2_5|2.5.9-150000.4.26.1|x86_64||
2023-08-25 02:27:47|remove |libreadline7|7.0-150400.25.22|x86_64||
2023-08-25 02:27:48|remove |libgdbm4|1.12-1.418|x86_64||
2023-08-25 02:27:48|remove |libffi7|3.2.1.git259-10.8|x86_64||
2023-08-25 02:28:06|remove |libfwupdplugin5|1.7.3-150400.2.7|x86_64||
2023-08-25 02:28:11|remove |libidn11|1.34-3.2.2|x86_64||
2023-08-25 02:35:38|rremove|repo-debug|
2023-08-25 02:35:38|rremove|repo-source|
2023-08-25 02:36:20|rremove|repo-debug|
2023-08-25 02:36:20|rremove|repo-source|
# 2023-08-25 01:38:07 kernel-default-5.14.21-150500.55.12.1.x86_64 removed ok
# Option --remove-kernel not available for grub2-efi.
2023-08-25 01:38:07|remove |kernel-default|5.14.21-150500.55.12.1|x86_64|root@HP-Z640-1|
2023-08-25 22:22:53|remove |brave-browser|1.57.53-1|x86_64|root@HP-Z640-1|
2023-08-25 22:22:53|remove |brave-keyring|1.14-1|noarch|root@HP-Z640-1|
# CONFTEST: proc_remove
# CONFTEST: pci_stop_and_remove_bus_device
# CONFTEST: pci_remove_bus_device
# CONFTEST: acpi_op_remove
# CONFTEST: vm_ops_fault_removed_vma_arg
# CONFTEST: kmem_cache_has_kobj_remove_work
2023-08-27 21:17:45|remove |libvpx7|1.11.0-150400.1.5|x86_64||
2023-09-03 10:44:31|remove |mozilla-nss-certs|3.91-1.2|x86_64|root@HP-Z640-1|
2023-09-03 13:16:39|remove |p11-kit-nss-trust|0.24.1-2.4|x86_64|root@HP-Z640-1|
2023-09-03 13:34:23|remove |MozillaFirefox-translations-common|116.0.3-1.1|x86_64|root@HP-Z640-1|
2023-09-03 13:34:25|remove |kmozillahelper|5.0.6-1.18|x86_64|root@HP-Z640-1|
2023-09-03 13:34:30|remove |MozillaFirefox|116.0.3-1.1|x86_64|root@HP-Z640-1|
2023-09-03 13:34:30|remove |MozillaFirefox-branding-openSUSE|68-4.1|x86_64|root@HP-Z640-1|
2023-09-03 14:52:23|remove |mozilla-nss-certs|3.92-1.1|x86_64|root@HP-Z640-1|
2023-09-03 15:52:07|remove |p11-kit-nss-trust|0.24.1-2.4|x86_64|root@HP-Z640-1|
2023-09-03 15:56:40|remove |mozilla-nss-certs|3.92-1.1|x86_64|root@HP-Z640-1|
2023-09-03 18:03:06|remove |p11-kit-nss-trust|0.24.1-2.4|x86_64|root@HP-Z640-1|
2023-09-04 11:26:30|remove |libcamera0_0_4|0.0.4-2.5|x86_64||
2023-09-04 11:26:30|remove |libSPIRV-Tools-2023_3_rc1|2023.3~rc1-1.2|x86_64||
2023-09-04 11:26:30|remove |libcamera-base0_0_4|0.0.4-2.5|x86_64||
# CONFTEST: proc_remove
# CONFTEST: pci_stop_and_remove_bus_device
# CONFTEST: pci_remove_bus_device
# CONFTEST: acpi_op_remove
# CONFTEST: vm_ops_fault_removed_vma_arg
# CONFTEST: kmem_cache_has_kobj_remove_work
2023-09-04 11:29:35|remove |libKF5PimCommonAkonadi5|23.04.3-1.2|x86_64||
2023-09-04 11:29:36|remove |libKF5PimCommon5|23.04.3-1.2|x86_64||
2023-09-04 11:29:36|remove |libKF5TextAutoCorrection1|1.1.0-1.2|x86_64||
2023-09-04 11:29:43|remove |libKPim5MailTransportAkonadi5|23.04.3-1.2|x86_64||
# 2023-09-04 13:07:55 kernel-default-5.14.21-150500.55.19.1.x86_64 removed ok
# Option --remove-kernel not available for grub2-efi.
2023-09-04 13:07:55|remove |kernel-default|5.14.21-150500.55.19.1|x86_64|root@HP-Z640-1|
2023-09-06 09:46:40|remove |nvidia-computeG05-32bit|470.199.02-54.1|x86_64|root@HP-Z640-1|
2023-09-06 09:46:40|remove |nvidia-glG05-32bit|470.199.02-54.1|x86_64|root@HP-Z640-1|
2023-09-06 09:46:41|remove |x11-video-nvidiaG05-32bit|470.199.02-54.1|x86_64|root@HP-Z640-1|
2023-09-06 09:46:42|remove |nvidia-glG05|470.199.02-54.1|x86_64|root@HP-Z640-1|
2023-09-06 09:46:47|remove |x11-video-nvidiaG05|470.199.02-54.1|x86_64|root@HP-Z640-1|
# 2023-09-06 09:46:48 nvidia-computeG05-470.199.02-54.1.x86_64 removed ok
2023-09-06 09:46:48|remove |nvidia-computeG05|470.199.02-54.1|x86_64|root@HP-Z640-1|
# 2023-09-06 09:47:00 nvidia-gfxG05-kmp-default-470.199.02_k6.4.3_1-54.8.x86_64 removed ok
2023-09-06 09:47:00|remove |nvidia-gfxG05-kmp-default|470.199.02_k6.4.3_1-54.8|x86_64|root@HP-Z640-1|
2023-09-06 09:50:53|rremove|NVIDIA:repo-non-free|
2023-09-06 10:01:47|rremove|NVIDIA:repo-non-free|
# 2023-09-06 10:02:10 openSUSE-repos-MicroOS-NVIDIA-20230810.a7534f6-1.1.x86_64 removed ok
# Service 'NVIDIA' has been removed.
2023-09-06 10:02:10|remove |openSUSE-repos-MicroOS-NVIDIA|20230810.a7534f6-1.1|x86_64|root@HP-Z640-1|
2023-09-06 15:08:28|remove |libpsm_infinipath1|3.3-13.16|x86_64||
2023-09-06 15:08:28|remove |libinfinipath4|3.3-13.16|x86_64||
2023-09-06 17:12:19|remove |kdenlive-lang|23.08.0-1.1|noarch|root@HP-Z640-1|
2023-09-06 17:12:21|remove |kdenlive|23.08.0-1.1|x86_64|root@HP-Z640-1|
alastair@HP-Z640-1:~>
Am I missing something?
Hi Malcolm,
I did find there was a file missing based on your reply. In Yast2 I looked for amdgpu and found that a driver
xf86-video-amdgpu
had not been installed. I installed it and rebooted but still no success even with a new virgin user.
I noticed that the AMD Mesa driver had not been installed so added this but it made no difference. The only thing not yet installed are some 32 bit requirements. Should I also add these?