Workplace switcher frozen can't select workspace
Clash Royale CLAN TAG#URR8PPP
After clicking the Workplace Switcher the screen froze and no desktop could be selected. I could still type commands in a terminal window even though the workspace could not be selected. No key combination worked to select a desktop. Alt-F4, Ctrl-alt left/right, etc.
This is a 2x2 workspace, usually with lots of windows open. Clicking on the icon on the taskbar then selecting the workspace to go to (because alt-tab / ctrl-alt-tab is annoying and unpredictable) usually works well.
Other than Raising the Elephant, a soft boot, or a hard boot, is there another way out of this when the workplace switcher is frozen on Ubuntu 16.04? A key combination or other method perhaps?
There was nothing in journalctl that seemed to be related to this freezing event.
workspaces
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
add a comment |
After clicking the Workplace Switcher the screen froze and no desktop could be selected. I could still type commands in a terminal window even though the workspace could not be selected. No key combination worked to select a desktop. Alt-F4, Ctrl-alt left/right, etc.
This is a 2x2 workspace, usually with lots of windows open. Clicking on the icon on the taskbar then selecting the workspace to go to (because alt-tab / ctrl-alt-tab is annoying and unpredictable) usually works well.
Other than Raising the Elephant, a soft boot, or a hard boot, is there another way out of this when the workplace switcher is frozen on Ubuntu 16.04? A key combination or other method perhaps?
There was nothing in journalctl that seemed to be related to this freezing event.
workspaces
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
1
Since you have to ask, you will most likely encounter other issues if you proceed. Considering that you have shell access, you could always kill X and restart it, but restarting the system would be the best solution. I suggest you take a look at your system logs for indications of a problem which would concur with the freeze to hopefully correct the cause.
– Julie Pelletier
Feb 26 '17 at 6:26
1
Did you try killing Compiz? In my experience, it's what causes Ubuntu's default interface to freeze and killing it often resolves the freeze. To do that, log in on a text console (pressCtrl+Alt+F1) or over the network, and runpkill compiz.
– Gilles
Feb 26 '17 at 21:33
Yes, Ctrl-Alt-F1 certainly fixes it. I suspect it will fix just about anything, in the same way a screwdriver can fix just about anything. In this scenario it is an acceptable answer. It at least gets you to a prompt. I'd like to kill Compiz..
– Underverse
Feb 27 '17 at 13:52
add a comment |
After clicking the Workplace Switcher the screen froze and no desktop could be selected. I could still type commands in a terminal window even though the workspace could not be selected. No key combination worked to select a desktop. Alt-F4, Ctrl-alt left/right, etc.
This is a 2x2 workspace, usually with lots of windows open. Clicking on the icon on the taskbar then selecting the workspace to go to (because alt-tab / ctrl-alt-tab is annoying and unpredictable) usually works well.
Other than Raising the Elephant, a soft boot, or a hard boot, is there another way out of this when the workplace switcher is frozen on Ubuntu 16.04? A key combination or other method perhaps?
There was nothing in journalctl that seemed to be related to this freezing event.
workspaces
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
After clicking the Workplace Switcher the screen froze and no desktop could be selected. I could still type commands in a terminal window even though the workspace could not be selected. No key combination worked to select a desktop. Alt-F4, Ctrl-alt left/right, etc.
This is a 2x2 workspace, usually with lots of windows open. Clicking on the icon on the taskbar then selecting the workspace to go to (because alt-tab / ctrl-alt-tab is annoying and unpredictable) usually works well.
Other than Raising the Elephant, a soft boot, or a hard boot, is there another way out of this when the workplace switcher is frozen on Ubuntu 16.04? A key combination or other method perhaps?
There was nothing in journalctl that seemed to be related to this freezing event.
workspaces
workspaces
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
edited Feb 26 '17 at 6:59
Underverse
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
asked Feb 26 '17 at 5:53
UnderverseUnderverse
167210
167210
1
Since you have to ask, you will most likely encounter other issues if you proceed. Considering that you have shell access, you could always kill X and restart it, but restarting the system would be the best solution. I suggest you take a look at your system logs for indications of a problem which would concur with the freeze to hopefully correct the cause.
– Julie Pelletier
Feb 26 '17 at 6:26
1
Did you try killing Compiz? In my experience, it's what causes Ubuntu's default interface to freeze and killing it often resolves the freeze. To do that, log in on a text console (pressCtrl+Alt+F1) or over the network, and runpkill compiz.
– Gilles
Feb 26 '17 at 21:33
Yes, Ctrl-Alt-F1 certainly fixes it. I suspect it will fix just about anything, in the same way a screwdriver can fix just about anything. In this scenario it is an acceptable answer. It at least gets you to a prompt. I'd like to kill Compiz..
– Underverse
Feb 27 '17 at 13:52
add a comment |
1
Since you have to ask, you will most likely encounter other issues if you proceed. Considering that you have shell access, you could always kill X and restart it, but restarting the system would be the best solution. I suggest you take a look at your system logs for indications of a problem which would concur with the freeze to hopefully correct the cause.
– Julie Pelletier
Feb 26 '17 at 6:26
1
Did you try killing Compiz? In my experience, it's what causes Ubuntu's default interface to freeze and killing it often resolves the freeze. To do that, log in on a text console (pressCtrl+Alt+F1) or over the network, and runpkill compiz.
– Gilles
Feb 26 '17 at 21:33
Yes, Ctrl-Alt-F1 certainly fixes it. I suspect it will fix just about anything, in the same way a screwdriver can fix just about anything. In this scenario it is an acceptable answer. It at least gets you to a prompt. I'd like to kill Compiz..
– Underverse
Feb 27 '17 at 13:52
1
1
Since you have to ask, you will most likely encounter other issues if you proceed. Considering that you have shell access, you could always kill X and restart it, but restarting the system would be the best solution. I suggest you take a look at your system logs for indications of a problem which would concur with the freeze to hopefully correct the cause.
– Julie Pelletier
Feb 26 '17 at 6:26
Since you have to ask, you will most likely encounter other issues if you proceed. Considering that you have shell access, you could always kill X and restart it, but restarting the system would be the best solution. I suggest you take a look at your system logs for indications of a problem which would concur with the freeze to hopefully correct the cause.
– Julie Pelletier
Feb 26 '17 at 6:26
1
1
Did you try killing Compiz? In my experience, it's what causes Ubuntu's default interface to freeze and killing it often resolves the freeze. To do that, log in on a text console (press
Ctrl+Alt+F1) or over the network, and run pkill compiz.– Gilles
Feb 26 '17 at 21:33
Did you try killing Compiz? In my experience, it's what causes Ubuntu's default interface to freeze and killing it often resolves the freeze. To do that, log in on a text console (press
Ctrl+Alt+F1) or over the network, and run pkill compiz.– Gilles
Feb 26 '17 at 21:33
Yes, Ctrl-Alt-F1 certainly fixes it. I suspect it will fix just about anything, in the same way a screwdriver can fix just about anything. In this scenario it is an acceptable answer. It at least gets you to a prompt. I'd like to kill Compiz..
– Underverse
Feb 27 '17 at 13:52
Yes, Ctrl-Alt-F1 certainly fixes it. I suspect it will fix just about anything, in the same way a screwdriver can fix just about anything. In this scenario it is an acceptable answer. It at least gets you to a prompt. I'd like to kill Compiz..
– Underverse
Feb 27 '17 at 13:52
add a comment |
1 Answer
1
active
oldest
votes
When this happens the Ctrl+Alt+F7 or F8 may not work. Opening a Ctrl+Alt+F1 and using the following command fixes the problem:
unity &> /dev/null & disown
This also works well if it is possible to type in a terminal window.
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
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%2f347615%2fworkplace-switcher-frozen-cant-select-workspace%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When this happens the Ctrl+Alt+F7 or F8 may not work. Opening a Ctrl+Alt+F1 and using the following command fixes the problem:
unity &> /dev/null & disown
This also works well if it is possible to type in a terminal window.
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
add a comment |
When this happens the Ctrl+Alt+F7 or F8 may not work. Opening a Ctrl+Alt+F1 and using the following command fixes the problem:
unity &> /dev/null & disown
This also works well if it is possible to type in a terminal window.
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
add a comment |
When this happens the Ctrl+Alt+F7 or F8 may not work. Opening a Ctrl+Alt+F1 and using the following command fixes the problem:
unity &> /dev/null & disown
This also works well if it is possible to type in a terminal window.
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
When this happens the Ctrl+Alt+F7 or F8 may not work. Opening a Ctrl+Alt+F1 and using the following command fixes the problem:
unity &> /dev/null & disown
This also works well if it is possible to type in a terminal window.
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
answered Jul 24 '17 at 14:49
UnderverseUnderverse
167210
167210
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.
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%2f347615%2fworkplace-switcher-frozen-cant-select-workspace%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
1
Since you have to ask, you will most likely encounter other issues if you proceed. Considering that you have shell access, you could always kill X and restart it, but restarting the system would be the best solution. I suggest you take a look at your system logs for indications of a problem which would concur with the freeze to hopefully correct the cause.
– Julie Pelletier
Feb 26 '17 at 6:26
1
Did you try killing Compiz? In my experience, it's what causes Ubuntu's default interface to freeze and killing it often resolves the freeze. To do that, log in on a text console (press
Ctrl+Alt+F1) or over the network, and runpkill compiz.– Gilles
Feb 26 '17 at 21:33
Yes, Ctrl-Alt-F1 certainly fixes it. I suspect it will fix just about anything, in the same way a screwdriver can fix just about anything. In this scenario it is an acceptable answer. It at least gets you to a prompt. I'd like to kill Compiz..
– Underverse
Feb 27 '17 at 13:52