openQA is consistently failing on the desktop_login test, across multiple tries, on both x86_64 and aarch64. After some preparation steps - blanking out the background and adding a couple of test user accounts, 'jim' and 'jack' - the test reboots the system, logs in as 'jack', and logs out. At that point, it seems that plasma-login-greeter crashes and we end up at a text console instead of the login screen.
The backtrace of the crash shows it running through QMessageLogger::fatal (meaning it's a kind of "intentional crash" on a known fatal condition), with the log message "This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem." In the system logs, we see this:
Jul 14 18:45:25 fedora kwin_wayland[2358]: No backend specified, automatically choosing drm
Jul 14 18:45:25 fedora kwin_wayland[2358]: Accepting client connections on sockets: QList("wayland-0")
Jul 14 18:45:25 fedora kwin_wayland[2358]: Failed to open /dev/dri/card1 device (Device or resource busy)
<same error repeats 30 times or so>
Jul 14 18:45:30 fedora kwin_wayland[2358]: Failed to open drm device /dev/dri/card1
Jul 14 18:45:30 fedora kwin_wayland[2358]: No suitable DRM devices have been found
Jul 14 18:45:30 fedora systemd[2297]: plasma-login-kwin_wayland.service: Main process exited, code=exited, status=1/FAILURE
Jul 14 18:45:30 fedora systemd[2297]: plasma-login-kwin_wayland.service: Failed with result 'exit-code'.
Jul 14 18:45:30 fedora systemd[2297]: Failed to start plasma-login-kwin_wayland.service - KDE Window Manager (Login Manager Version).
Jul 14 18:45:30 fedora systemd[2297]: Dependency failed for plasma-login-wayland.target.
Jul 14 18:45:30 fedora systemd[2297]: plasma-login-wayland.target: Job plasma-login-wayland.target/start failed with result 'dependency'.
Jul 14 18:45:30 fedora systemd[2297]: Started plasma-login.service - Plasma Login.
Jul 14 18:45:30 fedora systemd[2297]: Started plasma-wallpaper.service - Plasma Wallpaper on Login screen.
Jul 14 18:45:30 fedora plasma-login-greeter[2361]: Failed to create wl_display (Connection refused)
Jul 14 18:45:30 fedora plasma-login-wallpaper[2362]: Failed to create wl_display (Connection refused)
Jul 14 18:45:30 fedora plasma-login-wallpaper[2362]: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Jul 14 18:45:30 fedora plasma-login-greeter[2361]: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Jul 14 18:45:30 fedora plasma-login-greeter[2361]: could not connect to display
Jul 14 18:45:30 fedora plasma-login-wallpaper[2362]: could not connect to display
Jul 14 18:45:30 fedora plasma-login-wallpaper[2362]: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Jul 14 18:45:30 fedora plasma-login-wallpaper[2362]: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Jul 14 18:45:30 fedora plasma-login-wallpaper[2362]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
As I said, this seems reliable within openQA. It failed the same way three times each on x86_64 and aarch64, on both prod and staging - so 12 identical failures in total. The same test does not fail on previous or subsequent updates, so it really does appear to be caused by this update.
On the difference between F44 and Rawhide (the same test fails on F44 but much later, so the logout crash doesn't happen there) - Rawhide has kernel 7.2, F44 has 7.1. I can probably hack things up to test F44 with F45's kernel and see if that makes the logout crash happen.
This update's test gating status has been changed to 'waiting'.
It seems like reverting b49a7c471e05f7c5f098c0e16461ca5133380d08 - the backport of https://invent.kde.org/plasma/plasma-login-manager/-/merge_requests/151/ - avoids the crash. That was a shot in the dark, but it seems to have hit. I've tried three runs with the revert and they all got past the crash, and two additional runs without the revert which both crashed.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
openQA is consistently failing on the desktop_login test, across multiple tries, on both x86_64 and aarch64. After some preparation steps - blanking out the background and adding a couple of test user accounts, 'jim' and 'jack' - the test reboots the system, logs in as 'jack', and logs out. At that point, it seems that plasma-login-greeter crashes and we end up at a text console instead of the login screen.
The backtrace of the crash shows it running through
QMessageLogger::fatal(meaning it's a kind of "intentional crash" on a known fatal condition), with the log message "This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem." In the system logs, we see this:As I said, this seems reliable within openQA. It failed the same way three times each on x86_64 and aarch64, on both prod and staging - so 12 identical failures in total. The same test does not fail on previous or subsequent updates, so it really does appear to be caused by this update.
On the difference between F44 and Rawhide (the same test fails on F44 but much later, so the logout crash doesn't happen there) - Rawhide has kernel 7.2, F44 has 7.1. I can probably hack things up to test F44 with F45's kernel and see if that makes the logout crash happen.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
It seems like reverting b49a7c471e05f7c5f098c0e16461ca5133380d08 - the backport of https://invent.kde.org/plasma/plasma-login-manager/-/merge_requests/151/ - avoids the crash. That was a shot in the dark, but it seems to have hit. I've tried three runs with the revert and they all got past the crash, and two additional runs without the revert which both crashed.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
farchord edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update cannot be pushed to stable. These builds plasma-integration-6.7.3-1.fc45 have a more recent build in koji's f45 tag.
This update's test gating status has been changed to 'failed'.
farchord edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
farchord edited this update.
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been submitted for stable by bodhi