Version-Release number of selected component: plasma-workspace-5.4.0-4.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/kscreenlocker_greet --immediateLock --ksldfd 38 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/libexec/kscreenlocker_greet global_pid: 3360 kernel: 4.2.0-0.rc6.git0.2.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #1 KCrash::defaultCrashHandler(int) at ../../src/kcrash.cpp:409
Created attachment 1069546 [details] File: backtrace
Created attachment 1069547 [details] File: cgroup
Created attachment 1069548 [details] File: core_backtrace
Created attachment 1069549 [details] File: dso_list
Created attachment 1069550 [details] File: environ
Created attachment 1069551 [details] File: limits
Created attachment 1069552 [details] File: maps
Created attachment 1069553 [details] File: mountinfo
Created attachment 1069554 [details] File: namespaces
Created attachment 1069555 [details] File: open_fds
Created attachment 1069556 [details] File: proc_pid_status
Another user experienced a similar problem: Unten neben Uhr, rechts, tray-icon "Lautstärke", rechte maustaste, und, boom, error. Es passiert, jedes zweites mal. Plasma absturtz. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 1 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 6963 kernel: 4.2.6-301.fc23.x86_64 package: plasma-workspace-5.4.3-3.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I'd clicked the launcher, and started typing in a program name. Just before crash, I saw the program & its icon, but not the usual list of documents matching the string below that. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 14213 kernel: 4.2.6-301.fc23.x86_64 package: plasma-workspace-5.5.0-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1024
Another user experienced a similar problem: This happened (and it does happen quite often) when I tried to switch off my external monitor using (autorandr - a script based on) xrandr. Everything blows up, including the konsole I launch the command in, after some time the plasma sometimes returns (this time it did return when I issued some xrandr commands blindly), but e.g. konsoles do not. May-be it is important that I change the --scale of my screen, i.e. I go from DP2-1@1x1+eDP1.65 to eDP1@1x1. This blow-up happens almost every time I do that - I have to reboot after that. This happens on Lenovo T540p using a Dock, but note that I do not undock before the blow-up. This instability is frustrating... reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 2 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 7714 kernel: 4.2.7-300.fc23.x86_64 package: plasma-workspace-5.5.0-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I pressed one of two volume tray icons, and tried to adjust the volume. plasma crashed. I had both kmix system tray and "the other" volume system tray active. I think it was the other that made plasma crash. I had both active, since I didn't want youtube videos to start at 100 % volume each time, and there was no "volume" plasmoid available when I searched. However, upon restart I suddenly had two. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 1776 kernel: 4.2.8-300.fc23.x86_64 package: plasma-workspace-5.5.0-4.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I clicked on the "view person" plasma widget, then plasmashell crashed. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: plasmashell crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell kernel: 4.3.3-300.fc23.x86_64 package: plasma-workspace-5.5.3-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp
Another user experienced a similar problem: Configured KDE Connect to link with my phone Received a notification on my phone Plasma crashed No idea if these are related, and due to the instability of Plasma after upgrading to Fedora 23, they likely are not. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 3496 kernel: 4.3.3-300.fc23.x86_64 package: plasma-workspace-5.5.3-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I logged into KDE, then tried to start an application with krunner. During typing of the application name krunner crashed. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/krunner crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/krunner global_pid: 1836 kernel: 4.3.3-301.fc23.x86_64 package: plasma-workspace-5.5.3-4.fc23 reason: krunner killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: plasmashell crashed when I connected to a VPN network using NetworkManager reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 2087 kernel: 4.3.3-301.fc23.x86_64 package: plasma-workspace-5.5.3-4.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This happens frequently. Some times, just using the Plasma Desktop (clicking here and there) it crashes, apparently without a specific reason. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 1 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 2950 kernel: 4.3.4-300.fc23.x86_64 package: plasma-workspace-5.5.4-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I recently connected to a network but beside this, I did nothing special, I think... reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 14237 kernel: 4.3.4-300.fc23.x86_64 package: plasma-workspace-5.5.4-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: - Right click on the audio tray icon - Click on "Audio Volume Settings..." - Every second time it crashes on my machine... reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --crashes 1 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 5039 kernel: 4.3.5-300.fc23.x86_64 package: plasma-workspace-5.5.4-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I inserted a luks-encrypted USB drive, clicked on "Open in File Manager" when the device notification popped up, entered the passphrase for the disk, and got an error saying something like "Could not mount a disk". That was bogus, because it was showing as mounted in the device notifier. I clicked "Open in File Manager" again, and got the error again, then plasmashell crashed.
*** Bug 1315551 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Error showed up right as the desktop loaded when logging in. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 1455 kernel: 4.4.3-300.fc23.x86_64 package: plasma-workspace-5.5.5-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1317098 has been marked as a duplicate of this bug. ***
*** Bug 1318096 has been marked as a duplicate of this bug. ***
*** Bug 1319474 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. Let the user's friend send pidgin message or let the user fast switch the windows. 2. The crash happened. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 1476 kernel: 4.4.5-300.fc23.x86_64 package: plasma-workspace-5.5.5-4.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Reported to upstream: https://bugs.kde.org/show_bug.cgi?id=356703 Can anybody please add KDE Bugzilla URL to "See also"? I don't have enough permissions.
(In reply to Diego from comment #30) > Reported to upstream: > https://bugs.kde.org/show_bug.cgi?id=356703 > > Can anybody please add KDE Bugzilla URL to "See also"? I don't have enough > permissions. I've added it to the external trackers instead.
*** Bug 1324146 has been marked as a duplicate of this bug. ***
*** Bug 1324654 has been marked as a duplicate of this bug. ***
*** Bug 1327147 has been marked as a duplicate of this bug. ***
*** Bug 1327357 has been marked as a duplicate of this bug. ***
*** Bug 1328538 has been marked as a duplicate of this bug. ***
*** Bug 1328631 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Resume from suspend reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 1 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 26193 kernel: 4.4.6-301.fc23.x86_64 package: plasma-workspace-5.5.5-5.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1329114 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I unlocked the screen from kscreenlocker and this crash popped up. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 1 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 8546 kernel: 4.4.6-301.fc23.x86_64 package: plasma-workspace-5.5.5-5.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: sleep mode fails wake up reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 1 crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 2833 kernel: 4.4.8-300.fc23.x86_64 package: plasma-workspace-5.5.5-5.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: setting up widgets reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 1440 kernel: 4.4.8-300.fc23.x86_64 package: plasma-workspace-5.5.5-5.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: i just try to open the bluetoot icon reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 2524 kernel: 4.4.8-300.fc23.x86_64 package: plasma-workspace-5.5.5-5.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1334498 has been marked as a duplicate of this bug. ***
plasmashell crashes after a dnf update, kde became UNUSABLE. i reported it manually in BZ #1333982 i am using lxqt desktop, since kde is unusable since this friday. today i was able to generate the backtrace for BZ #1333982, and abrt created BZ #1334498 (private dup of this one).
*** Bug 1336934 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Plasma crashed when enabling a previously saved wifi configuration reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 16994 kernel: 4.4.8-300.fc23.x86_64 package: plasma-workspace-5.6.3-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
qt5-qtdeclarative-5.6.0-11.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7e822d9239
qt5-qtdeclarative-5.6.0-11.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e78000fedc
qt5-qtdeclarative-5.6.0-11.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7e822d9239
qt5-qtdeclarative-5.6.0-11.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e78000fedc
Proposed as a Freeze Exception for 24-final by Fedora user rdieter using the blocker tracking app because: A workaround for plasma crash issue that is unfortunately not uncommon, as can be seen by the number of duplicate reports both downstream and upstream. Seems to affect some users more often (arguably making plasma unusable for them).
+1, fixing commonly-encountered crashers on live images is a good FE justification.
+1 FE, hard to imagine the fix involves a regression worse than frequent crashes, so let's fix it.
*** Bug 1342730 has been marked as a duplicate of this bug. ***
This bug was discussed at the 2016-06-06 blocker review meeting [1] and determined to be an AcceptedFreezeException as many people have experienced this and fixing it is a good idea in a release-blocking desktop. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-06-06/f24-blocker-review.2016-06-06-16.00.txt
qt5-qtdeclarative-5.6.0-11.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
qt5-qtdeclarative-5.6.0-11.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Similar problem has been detected: When starting up the desktop comes up a short time before the screen goes black. From the black screen you can run application through Alt-F2 searching. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 1388 kernel: 4.5.6-200.fc23.x86_64 package: plasma-workspace-5.6.4-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Please not that the patch to fix the problem has changed. There's now a workaround committed in plasma-nm and different proposed patch to Qt: https://bugs.kde.org/show_bug.cgi?id=346118#c131 Qt correct report is: https://bugreports.qt.io/browse/QTBUG-53677
We're already including the candidate for for QTBUG-53677 in the aforementioned qt5-qtdeclarative update. We can look into backporting the plasma-nm fix as well.
Similar problem has been detected: Every time I wake up my workstation from display power saving (I have a two monitor setup) I get this crash. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 3984 kernel: 4.5.6-200.fc23.x86_64 package: plasma-workspace-5.6.4-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to Diego from comment #62) > Similar problem has been detected: > > Every time I wake up my workstation from display power saving (I have a two > monitor setup) I get this crash. > > reporter: libreport-2.6.4 > backtrace_rating: 4 > cmdline: /usr/bin/plasmashell --shut-up > crash_function: KCrash::defaultCrashHandler(int) > executable: /usr/bin/plasmashell > global_pid: 3984 > kernel: 4.5.6-200.fc23.x86_64 > package: plasma-workspace-5.6.4-1.fc23 > reason: plasmashell killed by SIGSEGV > runlevel: N 5 > type: CCpp > uid: 1000 Please note that this is (always) happening to me with: $ rpm -q qt5-qtdeclarative qt5-qtdeclarative-5.6.0-11.fc23.x86_64 So the "try to connect to VPN / Wifi with changed MTU" problem seems to be fixed, while the "getting out of display power save" problem still leads to a crash.
Similar problem has been detected: While pressing Fn-F7 to go through the different display combinations of my laptop and external monitor. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 8252 kernel: 4.5.7-202.fc23.x86_64 package: plasma-workspace-5.6.5-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Logging in from a locked screen, and then using Fn-F7 to cycle through the second monitor combinations. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 24453 kernel: 4.5.7-202.fc23.x86_64 package: plasma-workspace-5.6.5-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: After resetting the display preferences for two monitors after logging in, when a second monitor was connected to the HDMI jack. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 4779 kernel: 4.6.4-201.fc23.x86_64 package: plasma-workspace-5.6.5-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: At login while using Fn-F7 to cycle through the different display with external monitor combinations. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 10437 kernel: 4.6.4-201.fc23.x86_64 package: plasma-workspace-5.6.5-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happend at login. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 1542 kernel: 4.6.5-200.fc23.x86_64 package: plasma-workspace-5.7.3-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1368627 has been marked as a duplicate of this bug. ***
Similar problem has been detected: It happened while switching virtual desktops. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 18533 kernel: 4.7.5-100.fc23.x86_64 package: plasma-workspace-5.7.5-2.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000