SUMMARY When I left my monitor turned off for a while - 10-15 min. and I turn it on, every time I find a black screen with a tiny start menu in upper left corner and no other UI elements. https://i.imgur.com/risrXn2.png When I click on Kickoff it actuall works. Alt+F2 is also working. https://i.imgur.com/DMl14Pw.png When I change resolution to some different than the current resolution, the problem disappears and everything is fine. I can use my PC normally till I turn off my monitor and turn it on after a certain amount of time and then it's starting again - black screen with with a tiny start menu in upper left corner. This happens with the last updates in a few days. I thought it can be the new Plasma Framework version. I downgraded to 5.73 but this doesn't help. All energy saving options are tuned off. This doesn't help either. STEPS TO REPRODUCE 1. Turn off monitor and leave it turned off for 10-15 min. OBSERVED RESULT Black screen with a tiny start menu in upper left corner. EXPECTED RESULT Normal desktop. SOFTWARE/OS VERSIONS Arch Linu KDE Plasma KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74 Qt Version: 5.15.1
I can confirm - the problem seems to be with Qt 5.15.1. I downgraded all Qt packages to 5.15 and the problem dissapeared.
How strange. If it's a Qt 5.15.1 regression, can you report it at https://bugreports.qt.io/? Thanks!
Yes, it's a 5.15.1 regression. I downgraded to 5.15.0 and the problem is gone. Nate, I have more problems but it seems nobody look at them. Can you take a look? https://bugs.kde.org/show_bug.cgi?id=426206 https://bugs.kde.org/show_bug.cgi?id=426591 Regarding the second problem, downgrading to 5.15.0 resolves the problem but the splash screen is still in native resolution and then the system switches to desired resolution which I thinh isn't right. Thank you!
I reported the current problem: https://bugreports.qt.io/browse/QTBUG-86770
Thanks. I'm going to close this now and we'll keep tracking the issue upstream. I'll alert other KDE devs about it and hopefully something will happen there. I'll take a look at those other two bugs you mentioned.
Thank you, best regards!
I'm sorry Nate, but they refuse to accept my bug so I return here :(
Thiago's comments are perfectly reasnoble. We should write Qt bug reports when the time comes, but they do have to be in a format that is actionable without expecting them to run anything Plasma.
And what should I do?
They closed my bug, I'm lost...
While Thiago's comments are reasonable if Nick was a developer, he's not, so it's also reasonable that has has no idea what to do now. :) However I don't know either. I generally don't have a lot of contact with the Qt people, which maybe should change, but that's a discussion for another time. David, how should we proceed?
IIRC something like this got fixed in a recent Qt version. Is it still happening to you with the latest released versions of Qt and Plasma?
I'm sorry but I forgot about this issue. It's resolved somehow and I don't have this problem anymore :) However I have this problem now: https://bugs.kde.org/show_bug.cgi?id=439182