| Summary: | Dolphin crash due to bus error [KSharedDataCache::Private::CacheLocker::cautiousLock] | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | MountainX <davestechshop> |
| Component: | kshareddatacache | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | frank78ac, mpyne, richts |
| Priority: | NOR | ||
| Version: | 4.8.5 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=309824 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
MountainX
2012-11-14 18:20:46 UTC
Thanks for the bug report. You don't happen to use 'bleachbit', do you (see bug 254741)? I do not use bleachbit. Did you manipulate the contents of /var/tmp in some other way? I did not knowingly do anything to /var/tmp at this time and I don't believe I have any unusual scripts or applications that would manipulate the contents of /var/tmp. Here's my fstab with the UUIDs simplified: # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda2 during installation UUID=mno987 / btrfs noatime,subvol=@ 0 0 # /boot was on /dev/sda1 during installation UUID=pqr678 /boot ext2 defaults 0 2 # /home was on /dev/sdb1 during installation UUID=wxy456 /home btrfs noatime,subvol=@home 0 0 # /nocrypt was on /dev/sdc1 during installation UUID=abc123 /shared btrfs noatime 0 0 # swap was on /dev/sdc2 during installation UUID=def567 none swap sw 0 0 Let me know if I can provide any additional info. Thanks. I'm out of ideas here (except the trivial one that your disk might have been full at the time of the crash), but maybe Michael can say what the cause of such a crash might be. Frank, Thanks for the feedback. It is nice to have some idea of what might have happened. I checked disk space immediately after rebooting and there was plenty (actually, a ton of free space). However, my computer had not been rebooted prior to the crash for weeks. I guess it is possible that /var/tmp became temporarily full. I'll see if I can find evidence of that in the logs. Are there terms you would suggest searching for in the logs? Thanks Dave On Wed, Nov 14, 2012 at 6:30 PM, Frank Reininghaus <frank78ac@googlemail.com > wrote: > https://bugs.kde.org/show_bug.cgi?id=310111 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |frank78ac@googlemail.com, > | |mpyne@kde.org > Component|general |kshareddatacache > Version|2.0 |4.8.5 > Assignee|dolphin-bugs-null@kde.org |kdelibs-bugs@kde.org > Product|dolphin |kdelibs > Summary|KDE went crazy!!! |Dolphin crash due to bus > | |error > | > |[KSharedDataCache::Private: > | > |:CacheLocker::cautiousLock] > > --- Comment #5 from Frank Reininghaus <frank78ac@googlemail.com> --- > I'm out of ideas here (except the trivial one that your disk might have > been > full at the time of the crash), but maybe Michael can say what the cause of > such a crash might be. > > -- > You are receiving this mail because: > You reported the bug. > KSharedDataCache has received additional crash guards since KDE 4.8.5 (one of which *might* be relevant here). It's also possible you can stop Dolphin from crashing by removing the stored KSharedDataCache (which is generated on-demand).
The path to your KDE cache directory can be found by running "kde4-config --path cache". In that directory (and subdirectories under it) will be *.kcache files, which can be removed.
To do this quickly you can run:
find $(kde4-config --path cache) -name '*.kcache' -ok rm {} \;
at a Konsole or other terminal. The "-ok" command to find will require permission from you each time it removes a file.
If this works it's still a bug on my end but at least you'll be able to use Dolphin while I'm chasing it down. :-/
*** Bug 332391 has been marked as a duplicate of this bug. *** Still an issue as of 2016-09-06. *** This bug has been marked as a duplicate of bug 361426 *** |