After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 559097 - Evolution is blocked when password for keyring is being asked for
Evolution is blocked when password for keyring is being asked for
Status: RESOLVED DUPLICATE of bug 350838
Product: evolution-data-server
Classification: Platform
Component: general
2.24.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[passwords]
Depends on:
Blocks:
 
 
Reported: 2008-11-03 13:06 UTC by Marc Nieper-Wißkirchen
Modified: 2012-06-10 15:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Marc Nieper-Wißkirchen 2008-11-03 13:06:09 UTC 
Please describe the problem:
When Evolution starts, it needs the keyring so I am being asked for the corresponding passphrase. During this time, however, the Evolution thread is blocked. This means, for example, that Evolution turns gray when I have Compiz effects enabled.

The desired behaviour should be that Evolution waits patiently with the UI thread still running during the time I enter the passphrase.

Marc

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 André Klapper 2008-11-03 20:16:52 UTC 
Why is this a bug?
Comment 2 Marc Nieper-Wißkirchen 2008-11-03 21:15:23 UTC 
(In reply to comment #1)
> Why is this a bug?
> 

The UI thread of a GUI program shouldn't be blocked while the program is waiting for input.

If it is blocked (as it is with Evolution), the window system thinks the program is not responsive anymore. With Compiz, e.g., this means that the Evolution GUI turns gray. For the user, it seems as if the program has crashed.
Comment 3 André Klapper 2008-11-03 21:49:26 UTC 
(In reply to comment #2)
> For the user, it seems as if the program has crashed.

Not to me - e.g. if I manually delete the history in Firefox 3 it may also take some time and Firefox becomes gray in compiz here. It just means that the window is unresponsive.
Comment 4 Matthew Barnes 2008-11-03 21:50:52 UTC 
It's true.  All gnome-keyring calls occur in idle callbacks on the main thread.  That's usually not a problem unless the keyring is locked, which we can't determine ahead of time.

It's gonna take a major redesign of e-passwords.c to address this.  I tried a couple years ago but failed to get it working well.
Comment 5 André Klapper 2008-11-05 21:40:32 UTC 
Please do mention the downstream ticket:
https://bugs.launchpad.net/evolution/+bug/292730 . Thanks.
Comment 6 Matthew Barnes 2012-06-10 15:07:51 UTC 

*** This bug has been marked as a duplicate of bug 350838 ***