By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2234 - Yakuake doesn't retract on screen lock
Summary: Yakuake doesn't retract on screen lock
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: non-core programs (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2014-12-04 14:59 CST by Kristopher
Modified: 2014-12-08 09:32 CST (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2014-12-04 14:59:33 CST 
If I summon Yakuake then leave my computer idle, Yakuake will still be displayed when I awaken my screen. Nothing will respond save for the arrow: I cannot type within Yakuake, nor can I make it retract. My only option is to switch to a VT and either kill the desktop, or execute a reboot/shutdown.

My guess is that the desktop locker is hidden behind Yakuake and preventing Yakuake from responding, and Yakuake itself is preventing me from accessing the desktop locker so I can unlock my desktop and resume working normally.
Comment 1 Timothy Pearson 2014-12-04 18:37:41 CST 
Slavek, do you mind taking a look at this?  IIRC kdesktop_lock emits some kind of activated signal over DCOP so it should be easy enough to hook in and have Yakuake retract itself upon screen locking.
Comment 2 Slávek Banko 2014-12-06 12:19:05 CST 
I tried to simulate the problem now, but everything works as it should. I suspect that it was a problem fixed in commit aaa719d2 (tdebase).

Please can you test this with the updated tdebase?
Comment 3 Kristopher 2014-12-08 09:32:31 CST 
It seems to be fixed now.