Wayland locking up my system?

[oshunluvr]

I went ahead and logged into Wayland as my user again and got the extra splash thing:

Jan 23 17:24:28 office systemd[1471]: Starting Splash screen shown during boot...
Jan 23 17:24:28 office ksplashqml[6072]: QSocketNotifier: Can only be used with threads started with QThread
Jan 23 17:24:28 office dbus-daemon[1483]: [session uid=1000 pid=1483] Successfully activated service 'org.kde.KSplash'
Jan 23 17:24:28 office systemd[1471]: Finished KSplash "ready" Stage.
Jan 23 17:24:42 office systemd[1]: systemd-localed.service: Deactivated successfully.
Jan 23 17:24:52 office kdeconnectd[5308]: new capabilities for  "Pixel 6A"
Jan 23 17:24:52 office kdeconnectd[5308]: kdeconnect.plugin.battery: No Primary Battery detected on this system. This may be a bug.
Jan 23 17:24:52 office kdeconnectd[5308]: kdeconnect.plugin.battery: Total quantity of batteries found:  2
Jan 23 17:24:52 office kdeconnectd[5308]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Jan 23 17:24:53 office kdeconnectd[5308]: DataControlOffer: timeout reading from pipe
Jan 23 17:24:54 office kdeconnectd[5308]: DataControlOffer: timeout reading from pipe
Jan 23 17:24:58 office ksplashqml[6072]: KCrash: crashing... crashRecursionCounter = 2
Jan 23 17:24:58 office ksplashqml[6072]: KCrash: Application Name = ksplashqml path = /usr/bin pid = 6072
Jan 23 17:24:58 office ksplashqml[6072]: KCrash: Arguments: /usr/bin/ksplashqml
Jan 23 17:24:58 office systemd[1471]: plasma-ksplash.service: Main process exited, code=exited, status=1/FAILURE
Jan 23 17:24:58 office systemd[1471]: plasma-ksplash.service: Failed with result 'exit-code'.
Jan 23 17:24:58 office systemd[1471]: Failed to start Splash screen shown during boot.
Jan 23 17:24:58 office systemd[1471]: plasma-ksplash.service: Consumed 1.147s CPU time.

​

You can see it took 30 seconds to clear up. So, OK my user profile has something causing that part, but the monitor part is in the updates?

Nothing more fun to trouble-shoot than multiple over-lapping issues.

To be fair, I haven't started a new user account for myself since the initial KDEneon 20.04. Probably a good idea to start anew when 24.04 comes out.

[MoonRise]

Wow! A lot of work there. I tried Wayland a few weeks ago up until now. I even forgot I was using Wayland until I had an odd issue with KRDC. Then it hit me and I switched back to X11 and all OK. So I kind of agree Snowhog; not quite ready.

[Snowhog]

Jan 23 17:24:58 office ksplashqml[6072]: KCrash: crashing... crashRecursionCounter = 2 Jan 23 17:24:58 office ksplashqml[6072]: KCrash: Application Name = ksplashqml path = /usr/bin pid = 6072 Jan 23 17:24:58 office ksplashqml[6072]: KCrash: Arguments: /usr/bin/ksplashqml Jan 23 17:24:58 office systemd[1471]: plasma-ksplash.service: Main process exited, code=exited, status=1/FAILURE Jan 23 17:24:58 office systemd[1471]: plasma-ksplash.service: Failed with result 'exit-code'. Jan 23 17:24:58 office systemd[1471]: Failed to start Splash screen shown during boot. Jan 23 17:24:58 office systemd[1471]: plasma-ksplash.service: Consumed 1.147s CPU time.

Something wicked this way comes.

[claydoh]

Anybody want to guess which package(s) are the issue? LOL

The oibaf PPA mesa drivers?
But really, that might be a contributor here.
I switched from that one ages ago, because of the constant update frequency, since it builds new stuff nearly every day, or when someone farts a code change on Mesa's git
Constant rebooting/reloading the new video drivers was a pain for me. Plus some bugs here and there.

Been using the Kisak "fresh" PPA for a number of years.
The Mesa RC PPA from Ernstp- is somewhere in between Kisak and Oibaf, it has RC versions of Mesa 24 at the moment. It still releases quite often, though.

[oshunluvr]

FYI, after roll-back I can no log into a Wayland session again with my user, but I'm still getting the second login splash

Jan 24 11:21:28 office pipewire[2566]: mod.adapter: 0x55dd9995c230: can't get format: Device or resource busy
Jan 24 11:21:28 office pipewire-media-session[2567]: ms.core: error id:80 seq:574 res:-16 (Device or resource busy): can't create node: Device or resource busy
Jan 24 11:21:31 office plasmashell[2431]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55708a2f63b0) QQmlContext(0x55708adc2650) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Gl
obals.qml")
Jan 24 11:21:31 office plasmashell[2431]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55708a2f63b0) QQmlContext(0x55708adc2650) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Gl
obals.qml")
Jan 24 11:21:32 office plasmashell[2935]: [2984:2984:0124/112132.671407:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
Jan 24 11:21:38 office plasmashell[2935]: [2984:2984:0124/112138.017350:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
Jan 24 11:21:43 office plasmashell[2935]: [2984:2984:0124/112143.016491:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
Jan 24 11:21:48 office systemd[1]: systemd-localed.service: Deactivated successfully.
Jan 24 11:21:55 office systemd[2197]: Finished Splash screen shown during boot.
Jan 24 11:21:55 office systemd[2197]: plasma-ksplash.service: Consumed 1.123s CPU time.

[oshunluvr]

So today I'm still rolled back to the Monday version. I'm logged into a Wayland session and the monitors are not locking up. The second instance of the log in splash still occurs on my log in, but not the power/sleep issues with the screens.

At this point I suspect the update screwed the video card behavior but the double splash seems like a Wayland-against-my user settings somewhere.