Unlock Gnome shell takes a long time
I lock my GNOME Shell 3.6.3.1 by Ctrl+Alt+L as usual but when I try to unlock it takes up to a minute before I get my desktop back.
While waiting I get a black background and a mouse pointer.
Any ideas what takes so long?
gnome-shell screen-lock
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
asked Sep 26 '13 at 6:53
heldt
1163
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I lock my GNOME Shell 3.6.3.1 by Ctrl+Alt+L as usual but when I try to unlock it takes up to a minute before I get my desktop back.
While waiting I get a black background and a mouse pointer.
Any ideas what takes so long?
gnome-shell screen-lock
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
asked Sep 26 '13 at 6:53
heldt
1163
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I am also using the same shell version (Ubuntu-13.04) but do not have such issue. Have you modified any key-combination by chance ?
– SHW
Sep 26 '13 at 9:29
I use the default shortcuts. Don't think the problem lies with the shortcut. Somethings wrong while unlocking.
– heldt
Sep 26 '13 at 9:34
See for traces insyslogordmesg
– SHW
Sep 26 '13 at 9:39
@SHW nothing odd in syslog and dmesg since boot
– heldt
Sep 26 '13 at 9:58
I'm not sure what the cause is, but I remember having similar problems, too. The good news whatever bug was slowing down Gnome 3.6 was fixed in 3.8. Take a look at this question, which addresses something similar: askubuntu.com/q/159428/13755
– bntser
Sep 27 '13 at 17:36
add a comment |
I lock my GNOME Shell 3.6.3.1 by Ctrl+Alt+L as usual but when I try to unlock it takes up to a minute before I get my desktop back.
While waiting I get a black background and a mouse pointer.
Any ideas what takes so long?
gnome-shell screen-lock
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
asked Sep 26 '13 at 6:53
heldt
1163
I lock my GNOME Shell 3.6.3.1 by Ctrl+Alt+L as usual but when I try to unlock it takes up to a minute before I get my desktop back.
While waiting I get a black background and a mouse pointer.
Any ideas what takes so long?
gnome-shell screen-lock
gnome-shell screen-lock
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
asked Sep 26 '13 at 6:53
heldt
1163
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
asked Sep 26 '13 at 6:53
heldt
1163
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
edited Sep 26 '13 at 7:14
Anthon
60.3k17102163
60.3k17102163
asked Sep 26 '13 at 6:53
heldt
1163
asked Sep 26 '13 at 6:53
heldt
1163
asked Sep 26 '13 at 6:53
heldt
1163
1163
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I am also using the same shell version (Ubuntu-13.04) but do not have such issue. Have you modified any key-combination by chance ?
– SHW
Sep 26 '13 at 9:29
I use the default shortcuts. Don't think the problem lies with the shortcut. Somethings wrong while unlocking.
– heldt
Sep 26 '13 at 9:34
See for traces insyslogordmesg
– SHW
Sep 26 '13 at 9:39
@SHW nothing odd in syslog and dmesg since boot
– heldt
Sep 26 '13 at 9:58
I'm not sure what the cause is, but I remember having similar problems, too. The good news whatever bug was slowing down Gnome 3.6 was fixed in 3.8. Take a look at this question, which addresses something similar: askubuntu.com/q/159428/13755
– bntser
Sep 27 '13 at 17:36
add a comment |
I am also using the same shell version (Ubuntu-13.04) but do not have such issue. Have you modified any key-combination by chance ?
– SHW
Sep 26 '13 at 9:29
I use the default shortcuts. Don't think the problem lies with the shortcut. Somethings wrong while unlocking.
– heldt
Sep 26 '13 at 9:34
See for traces insyslogordmesg
– SHW
Sep 26 '13 at 9:39
@SHW nothing odd in syslog and dmesg since boot
– heldt
Sep 26 '13 at 9:58
I'm not sure what the cause is, but I remember having similar problems, too. The good news whatever bug was slowing down Gnome 3.6 was fixed in 3.8. Take a look at this question, which addresses something similar: askubuntu.com/q/159428/13755
– bntser
Sep 27 '13 at 17:36
I am also using the same shell version (Ubuntu-13.04) but do not have such issue. Have you modified any key-combination by chance ?
– SHW
Sep 26 '13 at 9:29
I am also using the same shell version (Ubuntu-13.04) but do not have such issue. Have you modified any key-combination by chance ?
– SHW
Sep 26 '13 at 9:29
I use the default shortcuts. Don't think the problem lies with the shortcut. Somethings wrong while unlocking.
– heldt
Sep 26 '13 at 9:34
I use the default shortcuts. Don't think the problem lies with the shortcut. Somethings wrong while unlocking.
– heldt
Sep 26 '13 at 9:34
See for traces in
syslog or dmesg– SHW
Sep 26 '13 at 9:39
See for traces in
syslog or dmesg– SHW
Sep 26 '13 at 9:39
@SHW nothing odd in syslog and dmesg since boot
– heldt
Sep 26 '13 at 9:58
@SHW nothing odd in syslog and dmesg since boot
– heldt
Sep 26 '13 at 9:58
I'm not sure what the cause is, but I remember having similar problems, too. The good news whatever bug was slowing down Gnome 3.6 was fixed in 3.8. Take a look at this question, which addresses something similar: askubuntu.com/q/159428/13755
– bntser
Sep 27 '13 at 17:36
I'm not sure what the cause is, but I remember having similar problems, too. The good news whatever bug was slowing down Gnome 3.6 was fixed in 3.8. Take a look at this question, which addresses something similar: askubuntu.com/q/159428/13755
– bntser
Sep 27 '13 at 17:36
add a comment |
2 Answers
2
active
oldest
votes
I had same problem and didn't know how to debug. But I deactivated all gnome shell extensions and then it worked perfectly.
You can deactivate one by one to find out which extension creates the problem—or you deactivate all and activate one by one again ;)
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
answered Mar 12 '14 at 8:47
mgafner
1
add a comment |
I had the same issue with Gnome 3.14.0 running under Debian Jessie. The previous answer sent me in the right direction and I discovered that the issue was down to the Pidgin IM integraton plugin by muffinmad. After disabling this plugin the unlock timeout reverted to normal behaviour.
answered Jun 2 '16 at 14:23
user173258
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f92435%2funlock-gnome-shell-takes-a-long-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had same problem and didn't know how to debug. But I deactivated all gnome shell extensions and then it worked perfectly.
You can deactivate one by one to find out which extension creates the problem—or you deactivate all and activate one by one again ;)
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
answered Mar 12 '14 at 8:47
mgafner
1
add a comment |
I had same problem and didn't know how to debug. But I deactivated all gnome shell extensions and then it worked perfectly.
You can deactivate one by one to find out which extension creates the problem—or you deactivate all and activate one by one again ;)
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
answered Mar 12 '14 at 8:47
mgafner
1
add a comment |
I had same problem and didn't know how to debug. But I deactivated all gnome shell extensions and then it worked perfectly.
You can deactivate one by one to find out which extension creates the problem—or you deactivate all and activate one by one again ;)
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
answered Mar 12 '14 at 8:47
mgafner
1
I had same problem and didn't know how to debug. But I deactivated all gnome shell extensions and then it worked perfectly.
You can deactivate one by one to find out which extension creates the problem—or you deactivate all and activate one by one again ;)
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
answered Mar 12 '14 at 8:47
mgafner
1
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
edited Mar 12 '14 at 9:08
Anthon
60.3k17102163
60.3k17102163
answered Mar 12 '14 at 8:47
mgafner
1
answered Mar 12 '14 at 8:47
mgafner
1
answered Mar 12 '14 at 8:47
mgafner
1
1
add a comment |
add a comment |
I had the same issue with Gnome 3.14.0 running under Debian Jessie. The previous answer sent me in the right direction and I discovered that the issue was down to the Pidgin IM integraton plugin by muffinmad. After disabling this plugin the unlock timeout reverted to normal behaviour.
answered Jun 2 '16 at 14:23
user173258
1
add a comment |
I had the same issue with Gnome 3.14.0 running under Debian Jessie. The previous answer sent me in the right direction and I discovered that the issue was down to the Pidgin IM integraton plugin by muffinmad. After disabling this plugin the unlock timeout reverted to normal behaviour.
answered Jun 2 '16 at 14:23
user173258
1
add a comment |
I had the same issue with Gnome 3.14.0 running under Debian Jessie. The previous answer sent me in the right direction and I discovered that the issue was down to the Pidgin IM integraton plugin by muffinmad. After disabling this plugin the unlock timeout reverted to normal behaviour.
answered Jun 2 '16 at 14:23
user173258
1
I had the same issue with Gnome 3.14.0 running under Debian Jessie. The previous answer sent me in the right direction and I discovered that the issue was down to the Pidgin IM integraton plugin by muffinmad. After disabling this plugin the unlock timeout reverted to normal behaviour.
answered Jun 2 '16 at 14:23
user173258
1
answered Jun 2 '16 at 14:23
user173258
1
answered Jun 2 '16 at 14:23
user173258
1
answered Jun 2 '16 at 14:23
user173258
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f92435%2funlock-gnome-shell-takes-a-long-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I am also using the same shell version (Ubuntu-13.04) but do not have such issue. Have you modified any key-combination by chance ?
– SHW
Sep 26 '13 at 9:29
I use the default shortcuts. Don't think the problem lies with the shortcut. Somethings wrong while unlocking.
– heldt
Sep 26 '13 at 9:34
See for traces in
syslogordmesg– SHW
Sep 26 '13 at 9:39
@SHW nothing odd in syslog and dmesg since boot
– heldt
Sep 26 '13 at 9:58
I'm not sure what the cause is, but I remember having similar problems, too. The good news whatever bug was slowing down Gnome 3.6 was fixed in 3.8. Take a look at this question, which addresses something similar: askubuntu.com/q/159428/13755
– bntser
Sep 27 '13 at 17:36