Since installing 15.3 (new installation, not upgrade) with kde a few weeks back I have experienced the following:
On several occasions, immediately after booting, no GUI’s will open (tried dolphin, firefox, okular, Kate etc). The only window available is a Konsole, which I always leave open when closing down - that works as expected. Even the shutdown dialogue does not work and I have to shutdown by pressing and holding the power button. Normally, on reboot, things are back to normal but on one occasion I had to reboot twice before I got a working session. The following is a snippet from /var/log/warn during such an episode.
2021-07-26T08:07:11.832957+01:00 localhost dolphin[2407]: qt.qpa.xcb: could not connect to display :0
2021-07-26T08:07:11.833180+01:00 localhost dolphin[2407]: qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
2021-07-26T08:07:11.837518+01:00 localhost dolphin[2407]: Failed to create wl_display (No such file or directory)
2021-07-26T08:07:11.837790+01:00 localhost dolphin[2407]: qt.qpa.plugin: Could not load the Qt platform plugin “wayland” in “” even though it was found.
2021-07-26T08:07:11.837951+01:00 localhost dolphin[2407]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.#012#012Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
2021-07-26T08:07:11.867360+01:00 localhost kwin_x11[1755]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 15422, resource id: 31457670, major code: 18 (ChangeProperty), minor code: 0
2021-07-26T08:07:42.416949+01:00 localhost dbus-daemon[1661]: [session uid=1000 pid=1661] Activating service name=‘org.kde.LogoutPrompt’ requested by ‘:1.13’ (uid=1000 pid=1741 comm="/usr/bin/ksmserver ")
2021-07-26T08:07:42.503465+01:00 localhost org.kde.LogoutPrompt[2412]: No protocol specified
2021-07-26T08:07:42.503694+01:00 localhost ksmserver-logout-greeter[2412]: qt.qpa.xcb: could not connect to display :0
2021-07-26T08:07:42.503884+01:00 localhost ksmserver-logout-greeter[2412]: qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
2021-07-26T08:07:42.504028+01:00 localhost ksmserver-logout-greeter[2412]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.#012#012Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
2021-07-26T08:07:42.508538+01:00 localhost org.kde.LogoutPrompt[2412]: Invalid MIT-MAGIC-COOKIE-1 key
2021-07-26T08:07:42.509898+01:00 localhost dbus-daemon[1661]: [session uid=1000 pid=1661] Activated service ‘org.kde.LogoutPrompt’ failed: Process org.kde.LogoutPrompt received signal 6
2 Maybe this indicates that the problem has something to with Qt. Even when the system is running apparently normally, I have noticed lots of these BadWindow entries in /var/log/warn - currently 3477 since July 4. These entries also appear to be associated with the following behaviour: clicking on a file to open it in its associated application (say Kate) does not succeed but opening the application first then using the “Open” dialogue does work. This behaviour is transient and may not be present earlier or later in the session.
I have been using the same Toshiba Satellite laptop for quite a few years, with different releases (not 15.2 but certainly 15.1 and 42.3) but have only seen these problems with 15.3
I can’t test it right now, but I think in the login screen you can choose which session you want to start. If you don’t *want *to use Wayland you can try and make sure to open a fresh X.Org session. Same issue there?
When you performed the installation, did you choose “Automatic login” for the user you configured?
If you did, you’ll need to use a Virtual Terminal (VT) to reconfigure the system –
After the system has booted, press the following 3 keys simultaneously – <Ctrl-Alt-F1>.
You’ll be presented with a blank screen – upper left a login prompt.
Login as the user “root” – you set the password at installation time.
A the command line prompt, type “yast2”.
You’ll be presented with a graphical interface which you navigate by means of the <Tab> key, the <Arrow> keys and, the Function keys <F1 … F12>. Yet another navigation is by means of the <Alt> key plus a letter key – <A … Z>.
With the <Arrow-Down> key (↓) navigate to “Security and Users”.
Change your user such that, automatic login doesn’t happen.
Can confirm that I did indeed mean after booting and logging-in and am using KDE. I haven’t configured automatic login and I see now that there are 3 options for the desktop : Plasma, Plasma (Full Wayland) and Plasma (Wayland). Since I didn’t even realize that there were options, I must have been going with the default, which I guess is Plasma. I suppose that I could try the other options to see if they behave in the same way.
With regard to trying a new clean user, the difficulty is that the problem doesn’t happen every day - I can go more than a week with no problem or it can happen 2 days running. Once it does happen, I would need to be able to switch user from the keyboard, since the Leave dialogue, which includes Switch User, doesn’t work in that situation. Using su I can switch user in the Konsole window, which is the only thing that works but what I would need is to start a whole new session from the keyboard and I don’t know if that is even possible.
As luck would have it, the first time I booted and logged in this morning, the problem was there. This time I tried launching applications (I used kate and okular) from the Konsole command line. They failed with basically the same error messages as when launched by clicking on the desktop icon, although now of course explicitly linked to the commands that generated them. Unfortunately, I was so rusty on using linux from the command line that I could not remember “script” for recording the session. I also tried using strace with these applications, directing stderr to files, so I do have that output. To the untrained eye, I couldn’t see anything enlightening in the output but maybe someone else would be able to spot something. However, I haven’t spotted any option for attaching files to the post.
Finally, I went to the Leave dialogue on the desktop and selected Switch User. I had expected nothing to happen, as when I select Shutdown, but was instead confronted with a new black screen with the following in bold letters:
The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a virtual terminal (Ctrl+Alt+F2), login and execute the command loginctl unlock-session 2
Afterwards switch back to the running session (Ctrl+Alt+F7)
I tried these keystrokes to no effect and ended up resorting to the power button as normal. On reboot, everything was fine again.
There is an important, but not easy to find feature on the forums.
Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
For very long text and screen shots, there is https://susepaste.org/
For text to susepaste you do not need copy/paste, you can pipe output to the sustepaste tool
write(2, "Failed to create wl_display (No "..., 56Failed to create wl_display (No such file or directory)
) = 56
write(2, "qt.qpa.plugin: Could not load th"..., 95qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
) = 95
write(2, "This application failed to start"..., 324This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
The strange thing is that, as far as I know, I’m not CHOOSING to use Wayland. The three desktop options presented at login are Plasma, Plasma(Full Wayland) and Plasma(Wayland) and I’m not explicitly choosing, so going with default, which seems to be Plasma. Both applications (kate and okular) do appear to be trying to use it though and failing but if wayland is the key to the problem why does everything work fine after rebooting? Also, when the problem is there, it’s not just kate and okular which won’t open - it’s everything I’ve tried (Firefox, Chrome, dolphin and more) and even the shutdown dialogue doesn’t work.
Digging into this Leap 15.3 system I’m finding the following – please use “journalctl -b 0 --output=short-monotonic --no-hostname” to find this issue –
6272.515589] kglobalaccel5[11217]: qt.qpa.xcb: could not connect to display :0
6272.516196] kglobalaccel5[11217]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
6272.519947] kglobalaccel5[11217]: Failed to create wl_display (No such file or directory)
6272.520556] kglobalaccel5[11217]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
6272.921538] kglobalaccel5[11217]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
6273.434846] systemd-coredump[11222]: Process 11217 (kglobalaccel5) of user 1000 dumped core.
Stack trace of thread 11217:
#0 0x00007f2d1671918b raise (libc.so.6 + 0x3a18b)
#1 0x00007f2d1671a585 abort (libc.so.6 + 0x3b585)
#2 0x00007f2d16f3987b qt_message_fatal (libQt5Core.so.5 + 0xaa87b)
#3 0x00007f2d1773936b init_platform (libQt5Gui.so.5 + 0x14536b)
#4 0x00007f2d1773982d _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x14582d)
#5 0x00007f2d1713f605 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b0605)
#6 0x00007f2d1773abef _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x146bef)
#7 0x00007f2d1773b8c4 _ZN15QGuiApplicationC2ERiPPci (libQt5Gui.so.5 + 0x1478c4)
#8 0x00005580938ad605 n/a (kglobalaccel5 + 0x1605)
#9 0x00007f2d1670434d __libc_start_main (libc.so.6 + 0x2534d)
#10 0x00005580938ad95a n/a (kglobalaccel5 + 0x195a)
6273.762253] dbus-daemon[7771]: [session uid=1000 pid=7771] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
6282.544871] systemd[7746]: Stopped target Main User Target.
Use “journalctl -b -??” to take a look at previous boots – omit “-b -??” to view the entire systemd Journal over all boots in the Journal.
> coredumpctl
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.
TIME PID UID GID SIG COREFILE EXE
Fri 2021-05-07 15:27:52 CEST 30986 1000 100 11 missing /usr/bin/gwenview
Fri 2021-05-07 15:30:23 CEST 31336 1000 100 11 missing /usr/bin/gwenview
Fri 2021-05-07 16:01:00 CEST 3531 1000 100 6 missing /usr/bin/kglobalaccel5
Sun 2021-05-16 17:02:56 CEST 9962 1000 100 11 missing /usr/bin/kontact
Mon 2021-05-31 10:44:22 CEST 4194 1000 100 11 missing /usr/bin/plasmashell
Mon 2021-05-31 10:44:40 CEST 4190 1000 100 11 missing /usr/bin/kwin_x11
Tue 2021-06-01 19:00:40 CEST 26868 1000 100 11 missing /usr/bin/kontact
Wed 2021-06-02 18:33:50 CEST 31338 1000 100 6 missing /usr/bin/plasma_session
Wed 2021-06-02 18:33:50 CEST 31486 1000 100 11 missing /usr/sbin/mysqld
Wed 2021-06-02 18:33:53 CEST 31351 1000 100 11 missing /usr/bin/kwin_x11
Fri 2021-06-04 17:56:28 CEST 1052 1000 100 11 missing /usr/bin/kwin_x11
Wed 2021-06-09 15:36:31 CEST 3033 1000 100 11 missing /usr/bin/kwin_x11
Thu 2021-06-10 10:29:46 CEST 4153 1000 100 6 missing /usr/bin/kontact
Tue 2021-06-15 17:08:31 CEST 30157 1000 100 7 missing /app/Signal/signal-desktop
Wed 2021-06-23 18:15:06 CEST 2229 1000 100 6 missing /usr/bin/kglobalaccel5
Fri 2021-07-02 11:56:36 CEST 9765 1000 100 11 missing /usr/lib/mozilla/kmozillahelper
Sat 2021-07-03 20:48:46 CEST 5060 1000 100 6 missing /usr/bin/kglobalaccel5
Sat 2021-07-03 20:48:47 CEST 5121 1000 100 6 missing /usr/lib64/libexec/drkonqi
Sat 2021-07-03 20:48:51 CEST 1198 1000 100 11 missing /usr/bin/kwin_x11
Fri 2021-07-16 19:39:38 CEST 12612 1000 100 11 missing /usr/bin/showfoto
Fri 2021-07-16 19:40:11 CEST 15063 1000 100 11 missing /usr/bin/showfoto
Fri 2021-07-16 19:41:14 CEST 15097 1000 100 11 missing /usr/bin/showfoto
Wed 2021-07-21 13:07:44 CEST 14371 1000 100 6 missing /usr/bin/kglobalaccel5
Wed 2021-07-21 15:37:12 CEST 31154 1000 100 6 missing /usr/bin/kglobalaccel5
Thu 2021-07-22 12:22:09 CEST 15320 1000 100 6 missing /usr/bin/kglobalaccel5
Fri 2021-07-23 10:32:08 CEST 8945 1000 100 6 missing /usr/bin/kglobalaccel5
Fri 2021-07-23 14:47:21 CEST 22636 1000 100 6 missing /usr/bin/kglobalaccel5
Fri 2021-07-23 17:35:51 CEST 29704 1000 100 6 missing /usr/bin/kglobalaccel5
Mon 2021-07-26 13:18:02 CEST 28958 1000 100 6 present /usr/bin/kglobalaccel5
Mon 2021-07-26 16:27:20 CEST 7630 1000 100 6 present /usr/bin/kglobalaccel5
Tue 2021-07-27 12:28:28 CEST 16219 1000 100 6 present /usr/bin/kglobalaccel5
Wed 2021-07-28 10:41:25 CEST 11217 1000 100 6 present /usr/bin/kglobalaccel5
>
Hmmm – looking at the newest core dump –
> coredumpctl info 11217
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.
PID: 11217 (kglobalaccel5)
UID: 1000 (xxx)
GID: 100 (users)
Signal: 6 (ABRT)
Timestamp: Wed 2021-07-28 10:41:24 CEST (4h 31min ago)
Command Line: /usr/bin/kglobalaccel5
Executable: /usr/bin/kglobalaccel5
Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service
Unit: user@1000.service
User Unit: dbus.service
Slice: user-1000.slice
Owner UID: 1000 (xxx)
Boot ID: dcd18979490f4626884ccc8bc420db1a
Machine ID: 02d4bd6562f443dc87a4204963c403f6
Hostname: eck001
Storage: /var/lib/systemd/coredump/core.kglobalaccel5.1000.dcd18979490f4626884ccc8bc420db1a.11217.1627461684000000.zst
Message: Process 11217 (kglobalaccel5) of user 1000 dumped core.
Stack trace of thread 11217:
#0 0x00007f2d1671918b raise (libc.so.6 + 0x3a18b)
#1 0x00007f2d1671a585 abort (libc.so.6 + 0x3b585)
#2 0x00007f2d16f3987b qt_message_fatal (libQt5Core.so.5 + 0xaa87b)
#3 0x00007f2d1773936b init_platform (libQt5Gui.so.5 + 0x14536b)
#4 0x00007f2d1773982d _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x14582d)
#5 0x00007f2d1713f605 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b0605)
#6 0x00007f2d1773abef _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x146bef)
#7 0x00007f2d1773b8c4 _ZN15QGuiApplicationC2ERiPPci (libQt5Gui.so.5 + 0x1478c4)
#8 0x00005580938ad605 n/a (kglobalaccel5 + 0x1605)
#9 0x00007f2d1670434d __libc_start_main (libc.so.6 + 0x2534d)
#10 0x00005580938ad95a n/a (kglobalaccel5 + 0x195a)
>
At least the KGlobalAccel is indicating an issue or two –
> kglobalaccel5 -v
kglobalaccel 0.2
>
> LANG=C zypper info kglobalaccel5
Loading repository data...
Reading installed packages...
Information for package kglobalaccel5:
--------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : kglobalaccel5
Version : 5.76.0-3.3.1
Arch : x86_64
Vendor : SUSE LLC <https://www.suse.com/>
Installed Size : 123.6 KiB
Installed : Yes
Status : up-to-date
Source package : kglobalaccel-5.76.0-3.3.1.src
Summary : Configurable global shortcut support
Description :
KGlobalAccel allows you to have global accelerators that are independent
of the focused window. Unlike regular shortcuts, the application's window
does not need focus for them to be activated.
>
I’ll see about raising a Bug Report either later today or, tomorrow …
Looking at the systemd User Journal, there seems to be some rather strange things going on …
There are no wl_display errors and no coredumps in my current session, which is working normally so, following your lead, I wanted to look back at the previous problematic session with journalctl but saw the following:
UNKNOWN:/home/malcolm # journalctl -b -1
Specifying boot ID or boot offset has no effect, no persistent journal was found.
UNKNOWN:/home/malcolm #
I have users on this system who do not experience the kglobalaccel5 crash at all …
There is one user where, kglobalaccel5
dumped core only once and, that was on the 11th of June this year. - The primary user on the system experiences regular kglobalaccel5
core dumps since the 21st of July this year …Curiously, not today – the 29th of July 2021 – last kglobalaccel5 core dump yesterday evening – when logging out …
Looking at the user’s systemd Journal, it seems that, with Leap 15.3 some users will notice that, kglobalaccel5
dumps core when they log out …
