-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long delay when unlocking screensaver with plugin enabled. #36
Comments
On extension enabling after screensaver there are two tasks depending on settings:
If you have a lot of opened conversations in Pidgin, then it may be the reason. Try to disable this options in extension settings to find out wich of them causes trouble. |
I have disabled #2. We'll see if I still get this extension blocking the shell for long periods of time... |
I can reproduce this at will. It's #1. If I disable a Pidgin account with a lot of contacts and then enable it, the shell (indeed, the whole UI) goes unresponsive until that account has finished logging in and all of the buddies in it are updated. So whatever is going on in that functionality, it needs to happen outside of the main thread so that it doesn't block the shell. What exactly is "Message tray integration" anyway? What functionality is it providing? |
It displays conversations in the notification area. |
I am seeing an issue with this plugin when it is enabled with GNOME Shell 3.14.4 screensaver running under Debian Jessie. After a number of days, and only after my laptop has been suspended/resumed a few times, a long delay of between 40 secs to 3/4 minutes ensues between entering the password and the screen unlocking.
I disabled all of the gnome shell extensions and the delay disappeared. After that, I re-enabled them one at a time until I got the delay issue to occur again. The only plugin that I experienced the issue with was this one.
Please let me know of any additional information that would help you reproduce and resolve this issue.
The text was updated successfully, but these errors were encountered: