Description of problem: This is the laptop described in Comment 14 of https://bugzilla.redhat.com/show_bug.cgi?id=1269004 with LVDS and an external monitor. Unfortunately, even after the "success" reported in Comment 14, I am now frequently getting crashes of plasma-workspace.x86_64 5.4.2-4.fc22 (obtained from updates-testing) at login, when I do a logout/login cycle, as it occurred for the present crash. After the crash reported here, the KDE desktop (on the external monitor) recovered nonetheless, without further actions on my part. The crash of plasma-workspace does not always happen, there seems to be a race condition. It seems that KDE (again) has difficulties deciding where to put the Primary Display, possibly because the external monitor activates late. I'm also observing crashes of - kf5-kactivities [already present with KDE frameworks 5.14] - kactivitymanagerd [seems to be new] which may or may not be related to the crashes of plasma-workspace. Version-Release number of selected component: plasma-workspace-5.4.2-4.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/plasmashell global_pid: 3918 kernel: 4.1.3-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 23629 Truncated backtrace: Thread no. 1 (1 frames) #1 KCrash::defaultCrashHandler(int) at ../../src/kcrash.cpp:418 Potential duplicate: bug 1259472
Created attachment 1084879 [details] File: backtrace
Created attachment 1084880 [details] File: cgroup
Created attachment 1084881 [details] File: core_backtrace
Created attachment 1084882 [details] File: dso_list
Created attachment 1084883 [details] File: environ
Created attachment 1084884 [details] File: limits
Created attachment 1084885 [details] File: maps
Created attachment 1084886 [details] File: mountinfo
Created attachment 1084887 [details] File: namespaces
Created attachment 1084888 [details] File: open_fds
Created attachment 1084889 [details] File: proc_pid_status
Created attachment 1084890 [details] File: var_log_messages
Another user experienced a similar problem: Happens occasionally when writing name of commands (like wireshark) or soon after starting. I'm using it on a system with dual head config and Intel GPU (Thinkpad X230) reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/krunner crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/krunner global_pid: 3941 kernel: 4.2.3-200.fc22.x86_64 package: plasma-workspace-5.4.2-4.fc22 reason: krunner killed by SIGSEGV runlevel: N 5 type: CCpp uid: 20970
Another user experienced a similar problem: occasionally during work in dual screen configuration reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/krunner crash_function: KCrash::defaultCrashHandler(int) executable: /usr/bin/krunner global_pid: 9830 kernel: 4.2.5-201.fc22.x86_64 package: plasma-workspace-5.4.2-4.fc22 reason: krunner killed by SIGSEGV runlevel: N 5 type: CCpp uid: 20970
Another user experienced a similar problem: When using Fn-F7 to cycle through the possible screen combinations. 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: 1673 kernel: 4.2.8-200.fc22.x86_64 package: plasma-workspace-5.4.3-3.fc22 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: After adjusting the dual monitor for my laptop by cycling through FN-F7, I selected a program for focus (Thunderbird I think) and the task bar momentarily disappeared. Afterwards the error showed up. 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: 12131 kernel: 4.2.8-200.fc22.x86_64 package: plasma-workspace-5.5.1-1.fc22 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Software updates notifier popped up notifying me of new updates. I clicked the pop-up, and the error message appeared. I noticed no problems with the behavior of the desktop. 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: 29176 kernel: 4.3.4-200.fc22.x86_64 package: plasma-workspace-5.5.4-2.fc22 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I inserted a CD to rip, and instead of getting a message from the device notifier, the error occurred. 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: 1625 kernel: 4.3.4-200.fc22.x86_64 package: plasma-workspace-5.5.4-2.fc22 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I clicked on the print icon in the system tray (well after the job had finished) and it opened with a big red X and a message that there were no jobs in the queue. After that the system panel/task bar thing crashed and restarted. 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: 16455 kernel: 4.4.13-200.fc22.x86_64 package: plasma-workspace-5.5.5-2.fc22 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Similar problem has been detected: After logging in from a freshly booted system, using the search box in the default Application Launcher causes plasmashell to crash. This happens most reliably when trying to use the search as described above, but after that whether using the search box will cause another crash or not is more sporadic. Having looked briefly at the backtrace, it may be worth mentioning that I have had baloo search disabled when these crashes happened. I have enabled baloo search for now to see if it reduces the amount of plasmashell crashes. 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: 2670 kernel: 4.4.14-200.fc22.x86_64 package: plasma-workspace-5.5.5-2.fc22 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
<nod>, having baloo search disabled is a less-tested configuration. May be worth keeping it enabled, except configure it to exclude (all of) $HOME