Created attachment 1858605 [details] Journalctl Output Description of problem: After the update of QT-QTwayland 5.15.2-17.fc34 presents a blank screen once login has been processed. Previous to this, i used screen lock, and was presented with the text message creen lock not working and ALT-CTRL-F2 to unlock, which did not work. Had to reboot, and hence the above issue - blank screen. Version-Release number of selected component (if applicable): QT-QTWAyland 5.15.2-17.fc34 How reproducible: Every reboot the same issue. had to login using KDE X11 as opposed to wayland Steps to Reproduce: 1.Select KDE Wayland at login. 2.Login 3.Persistent blank screen Actual results: As above, blank screen after logging in. Expected results: Usual desktop should be presented. Additional info: Last boot journalctl with issue to be uploaded.
Is it just after qt5-qtwayland update? Are you sure there were no other packages updated with it? Can you verify that downgrading to older qt5-qtwayland build makes the issue go away? You can find previous build here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1879102
Hi, There were no problems booting this morning with KDE Wayland. I will attach my linux update this morning. The only change with QT-Wayland is the single update : qt5-qtwayland x86_64 5.15.2-17.fc34 updates 1.1 M There were no other QT updates. The lock screen worked yesterday no issues. I did not want to change my system as i do not have a spare machine to test. Not too sure how to downgrade QT Wayland if the sole update was a single file/update ? Regards, Shadders.
Created attachment 1858625 [details] System Update Indicating Single QT5-QTWayland update
Hi, Used the command : dnf downgrade qt5-qtwayland The version now running/installed is : qt5-qtwayland-5.15.2-4.fc34.x86_64 Logged out and logged back in using KDE Wayland and functions as expected. Regards, Shadders.
Can you update one more time and install debug symbols as well with "sudo dnf debuginfoinstall qt5-qtwayland"? And attach one more time the journal log?
Same happened on my machine. Downgrading qt5-qtwayland allowed KDE to start properly. journalctl contained the following: --------------------------------------------------------------------------------------------------- Feb 03 11:16:25 localhost systemd[3330]: app-org.kde.kgpg: Main process exited, code=dumped, status=11/SEGV Feb 03 11:16:25 localhost systemd-coredump[3675]: Process 3635 (kgpg) of user 1000 dumped core. Stack trace of thread 3635: #0 0x00007f3192ff4fac _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x82fac) #1 0x00007f3192ff50a5 _ZN15QtWaylandClient15QWaylandDisplay14forceRoundTripEv (libQt5WaylandClient.so.5 + 0x830a5) #2 0x00007f3192ffacb9 _ZN15QtWaylandClient15QWaylandDisplay15registry_globalEjRK7QStringj (libQt5WaylandClient.so.5 + 0x88cb9) #3 0x00007f3193017653 _ZN9QtWayland11wl_registry13handle_globalEPvP11wl_registryjPKcj (libQt5WaylandClient.so.5 + 0xa5653) #4 0x00007f3190511c04 ffi_call_unix64 (libffi.so.6 + 0x6c04) #5 0x00007f3190511107 ffi_call (libffi.so.6 + 0x6107) #6 0x00007f3192f67d10 wl_closure_invoke.constprop.0 (libwayland-client.so.0 + 0x6d10) #7 0x00007f3192f6842b dispatch_event.isra.0 (libwayland-client.so.0 + 0x742b) #8 0x00007f3192f6861c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x761c) #9 0x00007f3192f6aaff wl_display_roundtrip_queue (libwayland-client.so.0 + 0x9aff) #10 0x00007f3182ba7719 _ZN22KdePlatformThemePlugin6createERK7QStringRK11QStringList (KDEPlasmaPlatformTheme.so + 0x38719) #11 0x00007f3195c60c3e _ZN21QPlatformThemeFactory6createERK7QStringS2_ (libQt5Gui.so.5 + 0x158c3e) #12 0x00007f3195c6a658 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x162658) #13 0x00007f3195c6b8a8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x1638a8) #14 0x00007f319582b493 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2ad493) #15 0x00007f3195c6dca0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x165ca0) #16 0x00007f31962fb9fd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1b39fd) #17 0x000055ad42f16452 main (kgpg + 0x51452) #18 0x00007f319519ab75 __libc_start_main (libc.so.6 + 0x27b75) #19 0x000055ad42f17b6e _start (kgpg + 0x52b6e) ----------------------------------------------------------------------------------------------------------------- Installing debug symbols seemed to make no difference, I tried both with and without (maybe there's a better way and I don't know how to get the logs with debug symbols).
The stack trace above is for KGPG. For Plasma, it's very similar: --------------------------------------------------------------------------------------------- Feb 03 11:16:25 localhost systemd[3330]: Failed to start KDE Plasma Workspace. Feb 03 11:16:25 localhost systemd[3330]: plasma-plasmashell.service: Failed with result 'core-dump'. Feb 03 11:16:25 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@9-3689-0 comm="systemd" exe="/usr/lib/sy> Feb 03 11:16:25 localhost systemd[3330]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV Feb 03 11:16:25 localhost systemd-coredump[3690]: [🡕] Process 3683 (plasmashell) of user 1000 dumped core. Stack trace of thread 3683: #0 0x00007f14ec9f9fac _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x82fac) #1 0x00007f14ec9fa0a5 _ZN15QtWaylandClient15QWaylandDisplay14forceRoundTripEv (libQt5WaylandClient.so.5 + 0x830a5) #2 0x00007f14ec9ffcb9 _ZN15QtWaylandClient15QWaylandDisplay15registry_globalEjRK7QStringj (libQt5WaylandClient.so.5 + 0x88cb9) #3 0x00007f14eca1c653 _ZN9QtWayland11wl_registry13handle_globalEPvP11wl_registryjPKcj (libQt5WaylandClient.so.5 + 0xa5653) #4 0x00007f14ed10bc04 ffi_call_unix64 (libffi.so.6 + 0x6c04) #5 0x00007f14ed10b107 ffi_call (libffi.so.6 + 0x6107) #6 0x00007f14ee5f1d10 wl_closure_invoke.constprop.0 (libwayland-client.so.0 + 0x6d10) #7 0x00007f14ee5f242b dispatch_event.isra.0 (libwayland-client.so.0 + 0x742b) #8 0x00007f14ee5f261c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x761c) #9 0x00007f14ee5f4aff wl_display_roundtrip_queue (libwayland-client.so.0 + 0x9aff) #10 0x00007f14dced7719 _ZN22KdePlatformThemePlugin6createERK7QStringRK11QStringList (KDEPlasmaPlatformTheme.so + 0x38719) #11 0x00007f14ef112c3e _ZN21QPlatformThemeFactory6createERK7QStringS2_ (libQt5Gui.so.5 + 0x158c3e) #12 0x00007f14ef11c658 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x162658) #13 0x00007f14ef11d8a8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x1638a8) #14 0x00007f14eecdd493 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2ad493) #15 0x00007f14ef11fca0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x165ca0) #16 0x00007f14ef99b9fd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1b39fd) #17 0x000056307e03101f main (plasmashell + 0x2401f) #18 0x00007f14ee667b75 __libc_start_main (libc.so.6 + 0x27b75) #19 0x000056307e0343fe _start (plasmashell + 0x273fe)
There is now qtwayland-5.15.2-18.fc34 in updates-testing, does this one make a difference or does it still crash?
Tried qtwayland-5.15.2-18.fc34 from updates-testing and it's the same crash, same journalctl stack trace, unfortunately.
Hi Camil, Thanks for the testing. Hi Jan, i assume the testing by Camil is sufficient as he has copied your instructions regarding the debug aspect of wayland ? Regards, Shadders.
Can you please try to download builds from here https://koji.fedoraproject.org/koji/taskinfo?taskID=82331685 and update/reinstall qt5-qtwayland using these?
Hi, I assume i have to download the rpm and install using the rpm command ? Is it just the one rpm, or the debug also ? Thanks and regards, Shadders.
You just download the qt5-qtwayland package and either run "sudo dnf reinstall package_name" in case you have same version or "sudo dnf update package_name" in case you already reverted to the version that works for you.
Hi, Apologies for the delay. Yes, that works. Installed the rpm, rebooted the PC and logged in using Plasma Wayland, and is working as expected. Regards, Shadders.
Created attachment 1858863 [details] Journalctl Output after QT5-QTWayland rpm update
FEDORA-2022-b8782ad7f2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8782ad7f2
FEDORA-2022-b8782ad7f2 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b8782ad7f2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8782ad7f2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b8782ad7f2 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2050764 has been marked as a duplicate of this bug. ***