Created attachment 53975 [details] btw. why there are black corners? i have these on two different machines one on xf86-video-ati second on nvidia, and this glitch appears since kde4 Version: unspecified (using KDE 4.5.80) OS: Linux Shutdown/logout pop-up dialog doesn't co-operate with keyboard. Reproducible: Always Steps to Reproduce: kmenu -> leave -> shutdown or logout -> popup will be launched, there is no way to cofirm with enter or cancel with escape key Expected Results: It suposed to be confirmed with enter and canceled with escape, doesn't it? Clean kde sc 4.6 beta1 on archlinux x86_64
I am running Kubuntu 10.4 LTS fully updated. For the past couple of weeks the Lock/Logout plasmoid has not worked properly. It will work right after I log in, but after a short while it refuses to react to a click so I can log out or shut down. Currently I have ctrl+alt+del set to kill the xserver, which throws be back to the login screen. The button on that screen does work. IF I log back in the Lock/Logout button refuses to work after I have used a few applications. I am not able to pin it down to a specific application which causes the problem.
escape works here.. can't try enter, unfortunately as i can't exit my session at the moment.. can you confirm that this still affects you? (also: comment #1 is a distribution issue and unrelated to this report)
Right now I can test only my virtual machine Archlinux x86_64 with KDE 4.7.3 and it still doesn't react on escape or enter BTW I just realized: canceling restart dialog is giving me an error: Executable: kdeinit4 PID: 2817 Signal: Segmentation fault (11)
I can confirm that there isn't focus on that widget.
I've just tried 4.8 beta 1 (4.7.80) and pop-ups dialogs seems to work with escape and enter :)
so in that case this can be marked as fixed/worksforme?
I don't know, it was broken since 4.0 and now in 4.8 beta 1 is fixed but I can't tell if it's intentional or just coincidence and with final release it'll stop working again?
if it works now in 4.8 then its fixed. if it breaks again, then a new bugreport should be opened.