Multiple Issues When PC Wakes From Sleep - Kubuntu 22.04

Every time my computer is awoken from sleep, it has one or multiple weird issues. I am not completely new to Linux, but I still have a lot to learn. My goal was to switch back to daily driving Linux and only running Windows on rare occasion. Searching has not yielded anything definitive, so I thought that I would ask for advice before trying random things and introducing a lot more variables. I am really liking KDE Plasma besides these issues. Thank you for your time.

Here are some of the observed issues:

  • Title bar is missing from windows: file manager, settings, and Firefox (snap) It is sometimes only missing from one window and sometimes more or all. Sometimes I can see the desktop at the top of the window where the title bar should be and sometimes the window shifts up and I see the desktop at the bottom of the screen.
  • Sometimes the taskbar is gone as well
  • Sometimes the Wallpaper is gone
  • The wallpaper resets to the default on every reboot
  • The login window is only on one screen and will not let me type into it. (choosing “Switch user” has gotten around this issue at least once)

I have done very little beyond a vanilla install:

  • It is a multi boot setup. (separate drives and I have had an old version of Ubuntu as an option for over a year.)
  • I did run apt-get update and apt upgrade
  • I switched to Breeze Dark
  • I increased the height of the taskbar
  • I installed Bismuth for tiling windows, but have now disabled it

Here are some of the things that I have considered for a next step:

  • Try to completely uninstall Bismuth instead of just not enabling tiling windows.
  • Try Wayland instead of X11
  • Reinstall Kubuntu
  • Upgrade KDE Version

Here are OS Version and Hardware details:

Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-60-generic (64-bit)
Graphics Platform: X11

Hardware
Ryzen 7 3800X
32 GB Ram
RX 6700XT
Dual Monitors

(This is also posted on the /kubuntu subreddit, but there have been no responses)

I can’t say I’ve had any of these problems with Kubuntu. Are you using a PPA for updated graphics drivers? The graphics card is much newer than anything I’ve used. The graphics in my 5600G is Vega based, so it works out of the box. I don’t know what minimum kernel and Mesa versions would be needed for your card. I also don’t run multiple monitors so it could be a combination of factors like that giving you problems.

2 Likes

I have not installed any additional graphics drivers. It was something that I was going to look into, but I ran into these stability issues before I could look further. I have read several places that I should be good with kernel versions 5.11+. I never have time to game anyway, even running Windows, so it has not been a priority getting this OS set up. Do you think that it is likely that the GPU drivers could be causing these type of issues?

I had these same two LG 27" 4K monitors on my old computer running Ubuntu 16.10 with an i7-3770K and a RX 580 with no problems at all. The RX 6700XT was released 2 years ago next month, so I would think there would be decent support by now.

Check to see also what version of Mesa you are running as that may be the issue as well. Here the command for checking the mesa version.
glxinfo | grep Mesa

1 Like

Thank you for including the command to run from the terminal.

client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.5
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.5
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.5

I found an article on phoronix.com comparing Mesa 22.0.5 to 22.2-rc1 on the RX6700xt, so it appears this version should support it without any issues.

Here is a ppa for latest Mesa:
sudo add-apt-repository ppa:kisak/kisak-mesa
sudo apt update

after you update, I recommend a restart.

Thanks for the suggestion, but it still did not resolve the issue. I am now on Mesa 22.3.6 - kisak-mesa PPA. It seemed odd that a GPU driver update would fix all of those issues, but I was definitely willing to give it a shot. Do you have any other ideas?

you have tried lots of stuff already & even tho a drive shouldn’t be the cause, when i troubleshoot i like to cover all options, even the ones that don’t make sense :stuck_out_tongue: do you have a spare you can try with?

it sounds like something isn’t wanting to go to sleeps or isn’t going sleeps properly & then wants to stay in bed when wakeup.

1 Like

this is more of a bandaid than a solution but have you tried restarting the plasma desktop after your desktop wakes from sleep? it can be done with these commands.
killall plasmashell
kstart plasmashell

depending on your kde version you may also try

killall plasma-desktop
kstart plasma-desktop

i have had some weird issues with kde and ive been using it for about 2 years on multiple distros. sadly they all have there own little quirks. when the desktop starts having any serious problems i restart the desktop. its a good way to temporarily fix some issues and not have to do a reboot.

1 Like

About 30 minutes before trying this. I had restarted my computer and restored my Firefox with 2 windows without title bar and 2 windows with the title bar. One screen retained the new wallpaper and one reverted. It was one of each on each screen and one of each was maximized vs floating. But when I restarted the plasma desktop, I lost all of the title bars. I restarted the computer again, to the same wallpaper situation. Restarted and restored the browser to 3 windows with title bar and 1 without. I think the next logical step is a reinstall then wait to confirm stability before installing bismuth. I might try switching from X11 to Wayland before I do though.

I checked the SMART info and the ssd seems healthy. I know that SMART does not tell the whole story. Like I mentioned to Figman above, I plan on a reinstall. I will reinstall on a different (also newer) ssd to rule out this potential as well. With all of these variables, I will not be able to come to any scientific conclusions. But as long as it works, I will be happy.

2 Likes

I know this can be frustrating at times, the not knowing how or why but i guess sometimes we just need to be happy if we can find a fix. I hope you get to (though i hope more you get to and find out the ‘why’ : )

1 Like

Once I slowed down for a minute and looked at the output after starting the shell, I spotted some errors that can point me toward more things to look into before full re-installation.

qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.

Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:165:9: QML HiddenItemsView: Binding loop detected for property "implicitHeight"

more 

QML Loader: Binding loop detected for property   errors

and a 

QML ScrollView: Binding loop detected for property "bottomPadding"

and a series of XCB error 2 and error 9

qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2884, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2885, resource id: 33554556, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2886, resource id: 33554556, major code: 72 (PutImage), minor code: 0

At least now I have some error info that I can compare to after changes and/or a reinstall.

1 Like

Ah good you got some useful data. Now google and linux forums will be your best friend to determine each error message and the best way to solve them. I wish i was more knowledgable about solving problems more in depth like that but good luck!

Also just a side note. Ive tried a bunch of different distros with kde and ive landed myself on manjaro for now. I definately will still have some weird issues sometimes but they seem to work themselves out more often than me having to intervene and do something to fix it.
I also am just transitioning from nobaro linux which is based on fedora and designed for gaming. I ended up having to switch because of issues with steam (ironic i only had issues with steam on a gaming distro lol) but other than that it was a good experience on fedora. I run regular fedora with kde on my laptop and my media center pc and they both run awesome. I dont use them nearly as often or for as many things but they have been a great experience.
Kubuntu was my worst experience. I was on kubuntu for the longest (about a year or so) and i only stuck with it because i still felt like a newb to linux and was scared to switch to something more complicated. Ive found that having the newer kernal and that newer version of KDE really seem to help with stability. (Sometimes i guess ive seen weird stuff on newer kernals and stuff too but it feels less often and easier to fix).
So if your feeling up to learning a new package manager and stuff id recommend trying out fedora KDE or manjaro. They are both solid and i really like both distros. Plus you get the newer kernal and baked in offline updates.

I can confirm that Wayland was not the solution. It fixed the wallpaper issues but at a great cost. It did not fix the missing title bars, but seemed slightly better. The multiple crashes of the shell were frustrating, but constant waking to a black screen with just a cursor made it unusable.

I have been seeing more reports of KDE not handling multiple monitors well and causing issues like I have been experiencing. I will be researching what distros (preferably KDE based) can handle dual monitors without issues. I ran Ubuntu for a bout a year a few years ago without issues, but I don’t want to go back to Gnome.

While looking at the problem through the dual monitor causation lens, I found more info and hope. My first attempt of fixes from this angle were to statically add my monitors through a xorg.conf file. At first I was hopeful, but I already was stuck at the login-screen, and then came back into a missing wallpaper and have had a crash. This may work for some people, but it did not work in this occasion.

# /etc/X11/xorg.conf.d/10-monitor.conf
Section "Monitor"
    Identifier    "DisplayPort-0" 
    Option        "PreferredMode" "3840x2160"
    Option        "TargetRefresh" "60"
    Option        "Primary" "true"
Endsection

Section "Monitor"
    Identifier    "DisplayPort-1 
    Option        "PreferredMode" "3840x2160"
    Option        "TargetRefresh" "60"
    Option        "RightOf" "DisplayPort-0"    
EndSection 

Yes, I made sure that I was loading X11 and not Wayland. And yes, I deleted the Kscreen files before rebooting.

Just a heads up too the newest release of KDE (KDE 5.27) is supposed to work much better with dual monitors and also has a bunch of other bug fixes and updates. It is there new LTS release of KDE and could solve a lot of your problems. (Although ive never tried updating KDE to beyond what kubuntu ships with)
fedora and manjaro should be shipping with KDE 5.27 now.

1 Like

As a followup, I have sidelined this situation while studying for a certification. THe computer has had sleep issues, even with Windows. I am currently waiting on RAM from the QVL to arrive and am hoping that fixes the problem.