KDE taskbar missing
I'm not sure what I pressed or clicked but I can no longer see the taskbar in KDE. I'm not finding any desktop switching keys though ALT+Tab still switches to already opened windows. Right-clicking on the blank empty black background does nothing. On Windows 7 I'd just CTRL+ALT+Delete, kill explorer.exe and start explorer again.
How do I show the missing taskbar in KDE?
kde
asked Oct 5 '16 at 13:50
JohnJohn
97621136
add a comment |
I'm not sure what I pressed or clicked but I can no longer see the taskbar in KDE. I'm not finding any desktop switching keys though ALT+Tab still switches to already opened windows. Right-clicking on the blank empty black background does nothing. On Windows 7 I'd just CTRL+ALT+Delete, kill explorer.exe and start explorer again.
How do I show the missing taskbar in KDE?
kde
asked Oct 5 '16 at 13:50
JohnJohn
97621136
I think maybe your KDE silently died and left you with bare X server and your open windows. Did you try to restart the whole system?
– Kamil Maciorowski
Oct 5 '16 at 14:08
@KamilMaciorowski Yeah but it happened again. :-
– John
Oct 5 '16 at 14:15
Was there graphical login prompt? After login, did KDE interface appear (if only for a moment) or not?
– Kamil Maciorowski
Oct 5 '16 at 14:21
@KamilMaciorowski Either it crashed without a crash message or I either pressed a button or clicked my mouse and inadvertently screwed it up.
– John
Oct 5 '16 at 14:38
add a comment |
I'm not sure what I pressed or clicked but I can no longer see the taskbar in KDE. I'm not finding any desktop switching keys though ALT+Tab still switches to already opened windows. Right-clicking on the blank empty black background does nothing. On Windows 7 I'd just CTRL+ALT+Delete, kill explorer.exe and start explorer again.
How do I show the missing taskbar in KDE?
kde
asked Oct 5 '16 at 13:50
JohnJohn
97621136
I'm not sure what I pressed or clicked but I can no longer see the taskbar in KDE. I'm not finding any desktop switching keys though ALT+Tab still switches to already opened windows. Right-clicking on the blank empty black background does nothing. On Windows 7 I'd just CTRL+ALT+Delete, kill explorer.exe and start explorer again.
How do I show the missing taskbar in KDE?
kde
kde
asked Oct 5 '16 at 13:50
JohnJohn
97621136
asked Oct 5 '16 at 13:50
JohnJohn
97621136
edited Oct 5 '16 at 14:06
John
asked Oct 5 '16 at 13:50
JohnJohn
97621136
asked Oct 5 '16 at 13:50
JohnJohn
97621136
asked Oct 5 '16 at 13:50
JohnJohn
97621136
97621136
I think maybe your KDE silently died and left you with bare X server and your open windows. Did you try to restart the whole system?
– Kamil Maciorowski
Oct 5 '16 at 14:08
@KamilMaciorowski Yeah but it happened again. :-
– John
Oct 5 '16 at 14:15
Was there graphical login prompt? After login, did KDE interface appear (if only for a moment) or not?
– Kamil Maciorowski
Oct 5 '16 at 14:21
@KamilMaciorowski Either it crashed without a crash message or I either pressed a button or clicked my mouse and inadvertently screwed it up.
– John
Oct 5 '16 at 14:38
add a comment |
I think maybe your KDE silently died and left you with bare X server and your open windows. Did you try to restart the whole system?
– Kamil Maciorowski
Oct 5 '16 at 14:08
@KamilMaciorowski Yeah but it happened again. :-
– John
Oct 5 '16 at 14:15
Was there graphical login prompt? After login, did KDE interface appear (if only for a moment) or not?
– Kamil Maciorowski
Oct 5 '16 at 14:21
@KamilMaciorowski Either it crashed without a crash message or I either pressed a button or clicked my mouse and inadvertently screwed it up.
– John
Oct 5 '16 at 14:38
I think maybe your KDE silently died and left you with bare X server and your open windows. Did you try to restart the whole system?
– Kamil Maciorowski
Oct 5 '16 at 14:08
I think maybe your KDE silently died and left you with bare X server and your open windows. Did you try to restart the whole system?
– Kamil Maciorowski
Oct 5 '16 at 14:08
@KamilMaciorowski Yeah but it happened again. :-
– John
Oct 5 '16 at 14:15
@KamilMaciorowski Yeah but it happened again. :-
– John
Oct 5 '16 at 14:15
Was there graphical login prompt? After login, did KDE interface appear (if only for a moment) or not?
– Kamil Maciorowski
Oct 5 '16 at 14:21
Was there graphical login prompt? After login, did KDE interface appear (if only for a moment) or not?
– Kamil Maciorowski
Oct 5 '16 at 14:21
@KamilMaciorowski Either it crashed without a crash message or I either pressed a button or clicked my mouse and inadvertently screwed it up.
– John
Oct 5 '16 at 14:38
@KamilMaciorowski Either it crashed without a crash message or I either pressed a button or clicked my mouse and inadvertently screwed it up.
– John
Oct 5 '16 at 14:38
add a comment |
2 Answers
2
active
oldest
votes
Killing the plasmashell process and restarting it from a terminal helped me in this situation.
To terminate the plasmashell process you will need access to a terminal. On most distributions you can get a terminal with CTRL+ALT+F1 or CTRL+ALT+F2. Don't worry, your screen will turn black and you will be prompted to log in with your username and password.
To get back to your regular KDE session you will need to press CTRL+ALT+F7 or CTRL+ALT+F1!
Once you have opened a terminal session you can stop the plasmashell process with
killall plasmashell
and start it again with
plasmashell &
The & is only required if you want to be able to close the terminal or want to be able to keep using it for other commands. It will start the plasmashell process in the background so it does not close with the terminal and does not keep blocking the terminal from receiving further input.
Alternatively you can kill the plasmashell process in your terminal and then immediately return to KDE and hit your hotkey for krunner, which is afaik ALT+F2 by default, and enter plasmashell there.
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
1
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
add a comment |
In my case the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file got in a bad state (from switching from laptop to external monitor).
Rather than trying to fix the file, I just deleted it (ALT-F2 "konsole"):
rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Then logout from the session (ALT-F2 "logout")
Log back in, and the taskbar is now visible, some settings were lost (background color, ...)
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1131728%2fkde-taskbar-missing%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
Killing the plasmashell process and restarting it from a terminal helped me in this situation.
To terminate the plasmashell process you will need access to a terminal. On most distributions you can get a terminal with CTRL+ALT+F1 or CTRL+ALT+F2. Don't worry, your screen will turn black and you will be prompted to log in with your username and password.
To get back to your regular KDE session you will need to press CTRL+ALT+F7 or CTRL+ALT+F1!
Once you have opened a terminal session you can stop the plasmashell process with
killall plasmashell
and start it again with
plasmashell &
The & is only required if you want to be able to close the terminal or want to be able to keep using it for other commands. It will start the plasmashell process in the background so it does not close with the terminal and does not keep blocking the terminal from receiving further input.
Alternatively you can kill the plasmashell process in your terminal and then immediately return to KDE and hit your hotkey for krunner, which is afaik ALT+F2 by default, and enter plasmashell there.
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
1
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
add a comment |
Killing the plasmashell process and restarting it from a terminal helped me in this situation.
To terminate the plasmashell process you will need access to a terminal. On most distributions you can get a terminal with CTRL+ALT+F1 or CTRL+ALT+F2. Don't worry, your screen will turn black and you will be prompted to log in with your username and password.
To get back to your regular KDE session you will need to press CTRL+ALT+F7 or CTRL+ALT+F1!
Once you have opened a terminal session you can stop the plasmashell process with
killall plasmashell
and start it again with
plasmashell &
The & is only required if you want to be able to close the terminal or want to be able to keep using it for other commands. It will start the plasmashell process in the background so it does not close with the terminal and does not keep blocking the terminal from receiving further input.
Alternatively you can kill the plasmashell process in your terminal and then immediately return to KDE and hit your hotkey for krunner, which is afaik ALT+F2 by default, and enter plasmashell there.
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
1
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
add a comment |
Killing the plasmashell process and restarting it from a terminal helped me in this situation.
To terminate the plasmashell process you will need access to a terminal. On most distributions you can get a terminal with CTRL+ALT+F1 or CTRL+ALT+F2. Don't worry, your screen will turn black and you will be prompted to log in with your username and password.
To get back to your regular KDE session you will need to press CTRL+ALT+F7 or CTRL+ALT+F1!
Once you have opened a terminal session you can stop the plasmashell process with
killall plasmashell
and start it again with
plasmashell &
The & is only required if you want to be able to close the terminal or want to be able to keep using it for other commands. It will start the plasmashell process in the background so it does not close with the terminal and does not keep blocking the terminal from receiving further input.
Alternatively you can kill the plasmashell process in your terminal and then immediately return to KDE and hit your hotkey for krunner, which is afaik ALT+F2 by default, and enter plasmashell there.
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
Killing the plasmashell process and restarting it from a terminal helped me in this situation.
To terminate the plasmashell process you will need access to a terminal. On most distributions you can get a terminal with CTRL+ALT+F1 or CTRL+ALT+F2. Don't worry, your screen will turn black and you will be prompted to log in with your username and password.
To get back to your regular KDE session you will need to press CTRL+ALT+F7 or CTRL+ALT+F1!
Once you have opened a terminal session you can stop the plasmashell process with
killall plasmashell
and start it again with
plasmashell &
The & is only required if you want to be able to close the terminal or want to be able to keep using it for other commands. It will start the plasmashell process in the background so it does not close with the terminal and does not keep blocking the terminal from receiving further input.
Alternatively you can kill the plasmashell process in your terminal and then immediately return to KDE and hit your hotkey for krunner, which is afaik ALT+F2 by default, and enter plasmashell there.
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
edited Sep 11 '18 at 16:35
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
answered Jan 20 '18 at 14:56
FlyingFoXFlyingFoX
17617
17617
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
1
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
add a comment |
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
1
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
...I probably did not accept this answer because it lacked/lacks instructions. If someone is asking a question an answer should provide instructions.
– John
Sep 7 '18 at 9:55
1
1
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
That can be fixed :)
– FlyingFoX
Sep 11 '18 at 16:17
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
Thank you, I up-voted this, looks legitimate though since I'm no longer running that environment I can't technically accept it...right now. It might be a year down the line though with Microsoft busy destroying the parts of Windows that actually still works I'll eventually find some time to explore a hopefully even more matured Linux OS. KDE has been my preferred desktop environment.
– John
Sep 12 '18 at 12:57
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
I've stumbled upon a very similar phenomenon, but restarting plasmashell in a shell alone was enough, so this process crashed somehow before. Maybe there is a bug related to or in VSCode, because its small preview windows become very small before the task bar crashes. This happens when you click on the VSCode entry nonetheless.
– BairDev
Nov 30 '18 at 10:13
add a comment |
In my case the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file got in a bad state (from switching from laptop to external monitor).
Rather than trying to fix the file, I just deleted it (ALT-F2 "konsole"):
rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Then logout from the session (ALT-F2 "logout")
Log back in, and the taskbar is now visible, some settings were lost (background color, ...)
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
add a comment |
In my case the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file got in a bad state (from switching from laptop to external monitor).
Rather than trying to fix the file, I just deleted it (ALT-F2 "konsole"):
rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Then logout from the session (ALT-F2 "logout")
Log back in, and the taskbar is now visible, some settings were lost (background color, ...)
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
add a comment |
In my case the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file got in a bad state (from switching from laptop to external monitor).
Rather than trying to fix the file, I just deleted it (ALT-F2 "konsole"):
rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Then logout from the session (ALT-F2 "logout")
Log back in, and the taskbar is now visible, some settings were lost (background color, ...)
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
In my case the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file got in a bad state (from switching from laptop to external monitor).
Rather than trying to fix the file, I just deleted it (ALT-F2 "konsole"):
rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Then logout from the session (ALT-F2 "logout")
Log back in, and the taskbar is now visible, some settings were lost (background color, ...)
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
answered Jan 8 at 2:00
Richard PierreRichard Pierre
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1131728%2fkde-taskbar-missing%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 think maybe your KDE silently died and left you with bare X server and your open windows. Did you try to restart the whole system?
– Kamil Maciorowski
Oct 5 '16 at 14:08
@KamilMaciorowski Yeah but it happened again. :-
– John
Oct 5 '16 at 14:15
Was there graphical login prompt? After login, did KDE interface appear (if only for a moment) or not?
– Kamil Maciorowski
Oct 5 '16 at 14:21
@KamilMaciorowski Either it crashed without a crash message or I either pressed a button or clicked my mouse and inadvertently screwed it up.
– John
Oct 5 '16 at 14:38