You are not logged in.
Pages: 1
Topic closed
Recently, I've had trouble with KDE crashing in two different instances.
* Right clicking the taskbar/application panel. Usually to close a window.
* Clicking the application launcher, or activating it using the keyboard shortcut that I configured.
I also cannot open the KDE system settings.
I created a test user and that user with a fresh profile doesn't experience any of the problems.
So, my issue is that I've tried every way that I can find people suggesting for resetting/clearing KDE and Plasma settings, but I'm still not getting a completely fresh KDE profile and I'm still experincing the problems.
I've backed up/delete:
* Every plasma file and folder in the ~/.config/ and ~/.local/share/ folders
* ~/.kde4
* ~/.kde4/share/config/kdeglobals
* ~/.cache/plasmashell
There are a couple of bugs on the KDE bug traker for this, but I don't want to wait for if/when the bugs get solved.
* https://bugs.kde.org/show_bug.cgi?id=388477
* https://bugs.kde.org/show_bug.cgi?id=387562
What else do I need to delete to reset my KDE profile?
Last edited by lyntux (2018-01-18 04:15:58)
Offline
Deleting random things fixes random things by random chance only...
Figure what the bug is. DrKonqi should show up on crashes (in doubt install it) and provide you access to a backtrace.
Online
Since the last update, also for me PlasmaShell is crashing periodically. It crashes, and after a while it comes back again, then it crashes again after a few minutes. Repeat...
Dual monitor with Nvidia drivers.
Offline
What else do I need to delete to reset my KDE profile?
Remove ~/.local/share/kactivitymanagerd/resources/
Offline
Since the last update, also for me PlasmaShell is crashing periodically. It crashes, and after a while it comes back again, then it crashes again after a few minutes. Repeat...
Dual monitor with Nvidia drivers.
This is unrelated and caused by the latest Discover update. Disable the updates applet form the system tray.
Offline
Remove ~/.local/share/kactivitymanagerd/resources/
Doesn't resolve anything but deletes favorits and stuff.
DrKonqi should show up on crashes (in doubt install it) and provide you access to a backtrace.
Right in theory, however the only backtrace there is reads...
Application: Plasma (plasmashell), signal: Segmentation fault
Update: Ups - I may have written to the wrong Issue here. My issue is crashing as soon as starting a search (while typing fast) within krunnder or k menue (on 3 different arch installations). Sorry. May open this as separate issue (but right now I'm running out of time).
Last edited by Herr_Irrtum (2018-01-14 15:02:30)
Offline
There is *nothing* else? You should run plasmashell in gdb then.
Online
There is *nothing* else? You should run plasmashell in gdb then.
Thx Seth. But gdb? I'd rather use strace. But I'm in the wrong thread anyway. Sorry for waking anyone up...
Offline
strace would only tell you which system calls occur while things go south - that's only relevant to see what files are opened but you'd be more interested in which library (and ideally of course which call/line) the segfault occurs.
Online
Dual monitor with Nvidia drivers.
Nailed it.
There is *nothing* else? You should run plasmashell in gdb then.
I'm not very familiar with gdb, I'm not having much luck googling. I tried attaching gdb to plasmashell, but plasma just freezes until I detach it in gdb. I have a .kcrash output from DrKonqi and can post it if you think that would help.
Offline
lyntux wrote:What else do I need to delete to reset my KDE profile?
Remove ~/.local/share/kactivitymanagerd/resources/
It worked for me (to be certain I just deleted the directory contents, and I lost all my favorite settings, but alas.)
In my case what I saw was that kactivitymanage was dumping after a number of messages stating that the kactivities database couldn't open in wal mode. In fact, my directory lacked the "database" file
Offline
sunnylx wrote:Since the last update, also for me PlasmaShell is crashing periodically. It crashes, and after a while it comes back again, then it crashes again after a few minutes. Repeat...
Dual monitor with Nvidia drivers.
This is unrelated and caused by the latest Discover update. Disable the updates applet form the system tray.
That explains why in my work computer, plasmashell doesn't crash since on that one I do not have Discover installed.
Thanks for the tip.
Offline
you have to "run" or "continue" in gdb after starting / attaching a process.
Online
Resolve for me following Arojas "Remove ~/.local/share/kactivitymanagerd/resources/"
Thanks !!!!
Offline
Thanks for the reply seth, I just wish other "quick start guide to gdb" had advice that helpful.
Here's what I got. I don't know if this is helpful to anyone, since it's a lot shorter than I expected.
Process:
* ran gdb
* attached to plasma
* continued in gdb
* right clicked in plasma
* gdb output:
Thread 1 "plasmashell" received signal SIGABRT, Aborted.
* continued in gdb
* gdb output:
Thread 1 "plasmashell" received signal SIGABRT, Aborted.
* plasma ended and restarted, gdb stopped logging since plasma has a new pid
(gdb) attach 10873
Attaching to process 10873
[New LWP 10877]
[New LWP 10878]
[New LWP 10882]
[New LWP 10895]
[New LWP 10896]
[New LWP 10906]
[New LWP 10910]
[New LWP 10914]
[New LWP 10944]
[New LWP 10945]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f636bc8c91b in poll () from /usr/lib/libc.so.6
(gdb) continue
Continuing.
Thread 1 "plasmashell" received signal SIGABRT, Aborted.
0x00007f636bbd5860 in raise () from /usr/lib/libc.so.6
(gdb) continue
Continuing.
Thread 1 "plasmashell" received signal SIGABRT, Aborted.
0x00007f636bbd5860 in raise () from /usr/lib/libc.so.6
(gdb)
I can post the DrKonqi output, but I don't know if I need to censor anything in that.
Offline
https://wiki.archlinux.org/index.php/De … _the_trace
Continuing a crashed process won't help. We need the backtrace (ie. what caused the abort in libc)
Online
Does the DrKonqi output help?
Offline
Sure (it's the backtrace, I thought you'd run into the same output as Herr_Irrtum)
#6 0x00007f0b349dbec9 in abort () at /usr/lib/libc.so.6
#7 0x00007f0b3517d8c8 in () at /usr/lib/libQt5Core.so.5
#8 0x00007f0a75333227 in () at /usr/lib/libKF5ActivitiesStats.so.1
#9 0x00007f0a75316d84 in KActivities::Stats::ResultSet::ResultSet(KActivities::Stats::Query) () at /usr/lib/libKF5ActivitiesStats.so.1
#10 0x00007f0a6d61e099 in () at /usr/lib/qt/qml/org/kde/plasma/private/taskmanager/libtaskmanagerplugin.so
#11 0x00007f0a6d62ca14 in () at /usr/lib/qt/qml/org/kde/plasma/private/taskmanager/libtaskmanagerplugin.so
#12 0x00007f0b383496ba in () at /usr/lib/libQt5Qml.so.5
Online
Removed ~/.local/share/kactivitymanagerd/resources/ and everything's working again. Thanks for everyone's help!
Offline
That worked great thanks! However is anyone else having the issue of the meta key no longer opening the application launcher?
Anybody been able to fix this?
Last edited by doctorzeus (2018-01-25 04:29:50)
Offline
Sorry, my meta key is working just fine.
Offline
Ok so solution for the meta key problem if anyone else comes across this thread later:
Go to ~/.config/kwinrc
Then Remove These Lines:
[ModifierOnlyShortcuts]
Meta=
Offline
Everything is working great after regular system update. You have got a specific issue.
Offline
Please pay attention to which thread you are responding to, you are posting in a 2 year old solved thread.
https://wiki.archlinux.org/index.php/Co … bumping%22
Closing.
Offline
Pages: 1
Topic closed