kmail with gpg-agent and compiz pops up 'not responding' dialogue

Bug #120124 reported by Robin Sheat
2
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kmail

If you have compiz enabled, and you use gpg-agent to sign messages with, when kmail uses it to ask for your password, it blocks. This causes comiz to grey it out after a few moments as 'not responding'. This is OK, however there is some quirk of kmail that means that after a moment of this, compiz pops up 'this application is not responding'. This message steals focus from the gpg-agent box, which means that part of the passphrase sometimes ends up going to kmail, and also that you have to start typing it over again in gpg-agent.

Revision history for this message
Rich Johnson (nixternal) wrote :

Do you know if this occurs only with KMail or does this also happen with other clients using the gpg-agent?

Another quick question, prior to enabling compiz, was KMail and gpg-agent working correctly for you?

Changed in kdepim:
status: Unconfirmed → Needs Info
Revision history for this message
Rich Johnson (nixternal) wrote :

This does work w/o compiz enabled is what I was trying to ask you. sorry about beating around the bush there :)

Revision history for this message
Robin Sheat (eythian) wrote :

Without compiz, kmail still blocks, but the window manager doesn't say 'not responding'. kmail is the only app I use that uses gpg-agent, but with other apps, when they block (because they're busy or something), compiz only asks when you try to close them.

Oh, another data point, if kmail is taking its time processing a GPG signature, it'll block and compiz will pop up the 'not responding' box. This goes away, as you'd expect, when the gpg process is done and control returns to kmail. This one is less of an issue, but it seems like the same symptom. My guess is there's a strange interaction between kmail and compiz causing it.

Revision history for this message
Scott Kitterman (kitterman) wrote :

pinentry-qt is the other player in the mix here. You might try signing something on the command line and see if the problem persists. I'm inclined to blame compiz here as it's the new program that should accomodate existing applications.

Revision history for this message
Robin Sheat (eythian) wrote :

pinentry-gtk-2 I think in my case. However, signing from the command line won't help, as kmail won't be blocking anyway. It's become less of an issue for me now anyway, I don't run compiz any more because it was causing issues with a number of other things.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I'm going to move this over to compiz then as it's more likely related to something there.

Revision history for this message
Travis Watkins (amaranth) wrote :

Compiz does not automatically pop up the 'Not Responding' dialog, it only does it when you try to close a window that isn't responding. Is that what you tried to do?

Revision history for this message
Robin Sheat (eythian) wrote :

No, it pops up completely automatically, there was no attempt to close the window. The kmail window doesn't have any sort of focus, and I'm usually busily typing into the GPG password box when it happens (although if I'm not typing, I think it happens also).

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
Robin Sheat (eythian) wrote :

I've just upgraded to gutsy and this still occurs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.