KDE Plasma crash after a few seconds (Kubuntu 18.04)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Since a few days I have the problem that after the start of my system only for a moment the desktop is visible (in fact, only the background image) and then plasma crashes. Everything else works fine, so I can start any application using KRunner, for example.
Some information:
- Kubuntu 18.04
- KDE Plasma 5.12.7
- KDE Framework 5.44.0
- Qt 5.9.5
- Kernel 4.15.0-45-generic (but the problem also exists under an older kernel)
What did I try:
- Added last packages removed via
apt-get autoremove(x11proto-dri2-dev:amd64andx11proto-gl-dev:amd64) - System update
- Disable startup programs
- Reset to default settings (
plasma-org.kde.plasma.desktop-appletsrc,plasmarcandplasmashellrcremoved) - Create new user
Currently, I suspect the reason for my problem somewhere in the last updates made. The last packages that were updated before the problem occurred were: libcurl4:amd64, spotify-client:amd64 and libcurl3-gnutls:amd64.
I appreciate any help.
kubuntu kde crash plasma plasma-5
asked Feb 13 at 7:41
BrokieBrokie
11
add a comment |
Since a few days I have the problem that after the start of my system only for a moment the desktop is visible (in fact, only the background image) and then plasma crashes. Everything else works fine, so I can start any application using KRunner, for example.
Some information:
- Kubuntu 18.04
- KDE Plasma 5.12.7
- KDE Framework 5.44.0
- Qt 5.9.5
- Kernel 4.15.0-45-generic (but the problem also exists under an older kernel)
What did I try:
- Added last packages removed via
apt-get autoremove(x11proto-dri2-dev:amd64andx11proto-gl-dev:amd64) - System update
- Disable startup programs
- Reset to default settings (
plasma-org.kde.plasma.desktop-appletsrc,plasmarcandplasmashellrcremoved) - Create new user
Currently, I suspect the reason for my problem somewhere in the last updates made. The last packages that were updated before the problem occurred were: libcurl4:amd64, spotify-client:amd64 and libcurl3-gnutls:amd64.
I appreciate any help.
kubuntu kde crash plasma plasma-5
asked Feb 13 at 7:41
BrokieBrokie
11
add a comment |
Since a few days I have the problem that after the start of my system only for a moment the desktop is visible (in fact, only the background image) and then plasma crashes. Everything else works fine, so I can start any application using KRunner, for example.
Some information:
- Kubuntu 18.04
- KDE Plasma 5.12.7
- KDE Framework 5.44.0
- Qt 5.9.5
- Kernel 4.15.0-45-generic (but the problem also exists under an older kernel)
What did I try:
- Added last packages removed via
apt-get autoremove(x11proto-dri2-dev:amd64andx11proto-gl-dev:amd64) - System update
- Disable startup programs
- Reset to default settings (
plasma-org.kde.plasma.desktop-appletsrc,plasmarcandplasmashellrcremoved) - Create new user
Currently, I suspect the reason for my problem somewhere in the last updates made. The last packages that were updated before the problem occurred were: libcurl4:amd64, spotify-client:amd64 and libcurl3-gnutls:amd64.
I appreciate any help.
kubuntu kde crash plasma plasma-5
asked Feb 13 at 7:41
BrokieBrokie
11
Since a few days I have the problem that after the start of my system only for a moment the desktop is visible (in fact, only the background image) and then plasma crashes. Everything else works fine, so I can start any application using KRunner, for example.
Some information:
- Kubuntu 18.04
- KDE Plasma 5.12.7
- KDE Framework 5.44.0
- Qt 5.9.5
- Kernel 4.15.0-45-generic (but the problem also exists under an older kernel)
What did I try:
- Added last packages removed via
apt-get autoremove(x11proto-dri2-dev:amd64andx11proto-gl-dev:amd64) - System update
- Disable startup programs
- Reset to default settings (
plasma-org.kde.plasma.desktop-appletsrc,plasmarcandplasmashellrcremoved) - Create new user
Currently, I suspect the reason for my problem somewhere in the last updates made. The last packages that were updated before the problem occurred were: libcurl4:amd64, spotify-client:amd64 and libcurl3-gnutls:amd64.
I appreciate any help.
kubuntu kde crash plasma plasma-5
kubuntu kde crash plasma plasma-5
asked Feb 13 at 7:41
BrokieBrokie
11
asked Feb 13 at 7:41
BrokieBrokie
11
asked Feb 13 at 7:41
BrokieBrokie
11
asked Feb 13 at 7:41
BrokieBrokie
11
asked Feb 13 at 7:41
BrokieBrokie
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I found the (somewhat surprising) solution: Blocked print jobs in CUPS killed the complete desktop environment! So, if someone faces the same problem:
- Go to the CUPS server or to the print manager and remove all print jobs that have stopped or
- run
lprm -
- Check if all print jobs could be removed! In my case, some jobs could not be removed. They belonged to a printer with a suspicious configuration, so in the end I simply removed the entire printer.
Hope it helps!
answered Feb 15 at 11:31
BrokieBrokie
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1117857%2fkde-plasma-crash-after-a-few-seconds-kubuntu-18-04%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
I found the (somewhat surprising) solution: Blocked print jobs in CUPS killed the complete desktop environment! So, if someone faces the same problem:
- Go to the CUPS server or to the print manager and remove all print jobs that have stopped or
- run
lprm -
- Check if all print jobs could be removed! In my case, some jobs could not be removed. They belonged to a printer with a suspicious configuration, so in the end I simply removed the entire printer.
Hope it helps!
answered Feb 15 at 11:31
BrokieBrokie
11
add a comment |
I found the (somewhat surprising) solution: Blocked print jobs in CUPS killed the complete desktop environment! So, if someone faces the same problem:
- Go to the CUPS server or to the print manager and remove all print jobs that have stopped or
- run
lprm -
- Check if all print jobs could be removed! In my case, some jobs could not be removed. They belonged to a printer with a suspicious configuration, so in the end I simply removed the entire printer.
Hope it helps!
answered Feb 15 at 11:31
BrokieBrokie
11
add a comment |
I found the (somewhat surprising) solution: Blocked print jobs in CUPS killed the complete desktop environment! So, if someone faces the same problem:
- Go to the CUPS server or to the print manager and remove all print jobs that have stopped or
- run
lprm -
- Check if all print jobs could be removed! In my case, some jobs could not be removed. They belonged to a printer with a suspicious configuration, so in the end I simply removed the entire printer.
Hope it helps!
answered Feb 15 at 11:31
BrokieBrokie
11
I found the (somewhat surprising) solution: Blocked print jobs in CUPS killed the complete desktop environment! So, if someone faces the same problem:
- Go to the CUPS server or to the print manager and remove all print jobs that have stopped or
- run
lprm -
- Check if all print jobs could be removed! In my case, some jobs could not be removed. They belonged to a printer with a suspicious configuration, so in the end I simply removed the entire printer.
Hope it helps!
answered Feb 15 at 11:31
BrokieBrokie
11
answered Feb 15 at 11:31
BrokieBrokie
11
answered Feb 15 at 11:31
BrokieBrokie
11
answered Feb 15 at 11:31
BrokieBrokie
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1117857%2fkde-plasma-crash-after-a-few-seconds-kubuntu-18-04%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
