https://bugs.kde.org/show_bug.cgi?id=314905
Not really a blocker. It works, although it does not look nice.
Created attachment 343628 [details] "confirm suspend" with Air theme Yeah, it does not look nice. You simply can't read the text on the buttons and need to guess what to do. The dialog is not resizable. <Esc> does not work (does not close the dialog). If you don't know that those small stripes on the bottom are buttons you are lost. If you don't know that the left button is "OK, Suspend" and the right one is "Cancel" you are lost. And quoting https://bugs.gentoo.org/show_bug.cgi?id=462922#c3 "If we decide to stabilize a new version, certainly it does not work worse than the actual stable, otherwise this should be a non-sense." That's the reason why I reported all those things that actually bugged me after the update of 4.9.5 to 4.10.
Created attachment 343642 [details, diff] related upstream commit Franz, could you please test if adding this patch to ksmserver helps?
The patch did not fix that dialog. I think that is a patch for a different dialog, the one you get when you press the big red button ("leave") with options to logout, shutdown and reboot. (and it is nice to have it fixed - some themes don't show graphics on the left leading to the same issue as described in the review) The one I am talking about is when you hit "suspend". But now I see that this dialog only pops up when using the "lock/logout" widget. Neither the actions in the "leave" menu in kickoff nor the shutdown options from the "leave"-dialog trigger that (though I selected "confirm logout" - no idea if that is another bug). As I am only using that logout-widget (navigating through the menu is too much clicks for me ;)) I thought it is a general issue. I will have a look, if I can find a similar patch to this issue.
Seems to be a regression in the new Air theme. Copied over the "default" plasma-theme from a 4.9.5-installation and the problem is fixed now.
There are reports on the upstream bug that this is fixed in 4.11 Can anyone confirm?
(In reply to Michael Palimaka (kensington) from comment #6) > There are reports on the upstream bug that this is fixed in 4.11 > Can anyone confirm?