Created attachment 965416 [details] error screenshot Description of problem: I regularly get error an internal error has occured. No detailed error is given by the notification dialog. After clicking ok the KDE panel freezes for a few seconds and then everything works just fine. It came to my notice sometime around F21 RC4 release. Please see the screenshot. Version-Release number of selected component (if applicable): Fedora 21 RC4 How reproducible: Occurs periodically. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 965417 [details] root dmesg
Created attachment 965418 [details] xsession-errors
It is not just the KDE Panel but the whole desktop freezes. I can't right click on desktop. Although apps keep working fine. I can shuffle across them using Alt-Tab shortcut.
pretty sure this is apper (and PackageKit) related, reassigning there.
Per irc , asked to run: pkcon refresh force result: Failed to contact PackageKit: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PackageKit timed out
and the referenced dmesg log definitely includes packagekitd crashing, [ 44.706795] packagekitd[1524]: segfault at 0 ip 00007f85741961f7 sp 00007fff90962fa8 error 4 in libc-2.20.so[7f8574052000+1b4000] [ 75.767571] packagekitd[1794]: segfault at 0 ip 00007f04821261f7 sp 00007fff94385c08 error 4 in libc-2.20.so[7f0481fe2000+1b4000] [ 147.909659] packagekitd[2081]: segfault at 0 ip 00007faf6ef891f7 sp 00007fffbba012b8 error 4 in libc-2.20.so[7faf6ee45000+1b4000] [ 172.943139] packagekitd[2206]: segfault at 0 ip 00007f1ee724c1f7 sp 00007fffd66fc678 error 4 in libc-2.20.so[7f1ee7108000+1b4000] [ 408.069005] packagekitd[3227]: segfault at 0 ip 00007fd6855001f7 sp 00007fffa04f5008 error 4 in libc-2.20.so[7fd6853bc000+1b4000] [ 462.467711] packagekitd[3455]: segfault at 0 ip 00007f6f23e451f7 sp 00007fff0bd12f88 error 4 in libc-2.20.so[7f6f23d01000+1b4000]
on irc, determined backtrace to be dup bug #1164330 and confirmed user had bumblebee repo enabled *** This bug has been marked as a duplicate of bug 1164330 ***