I really want to like Dolphin. It seems like it’s very versatile as a file manager and would work great once I learn how to take advantage of it.
But I can’t, it keeps crashing!
So far it’s the only part of opensuse 11.2 I’ve been unhappy with. Every single time I try to use Dolphin for more than a couple minutes, it crashes. It doesn’t matter if I’m using it or not. If it’s just sitting in the background, it crashes. If I’m browsing files, it crashes. If I look at it wrong, it crashes. This frequently happens on both our desktops. One is an Intel Core 2 Duo on an X48 board, and the other is an AMD 5050e on a 790G motherboard. Completely different platforms with vastly different desktop settings.
So for now I have good, old Konqueror set as my file manager. But I’d love to know why Dolphin keeps crashing. How do I go about diagnosing this problem?
There was a thread a while back on the Arch forum in which some people reported dolphin crashes being fixed by disabling nepomuk. It’s a potshot, but hey…
Otherwise, run it from a terminal and see if it spits anything out when it dies.
Disabling nepomuk seems to have fixed the issue. Dolphin has been running for 10 minutes without crashing. That’s longer than ever!
I don’t think I was using any features that nepomuk provides anyways, so no big loss there.
Wasn’t really expecting that to work, to be honest. I think Nepomuk is one of those things that will be really interesting in six months or a year, but doesn’t really do much at present.
I would suggest going to the bug tracker, but this has been reported on a few different distros I think - I doubt there’s much to add.
[eta - cripes that’s a lot of 'really’s. I need to go to bed… ;)]
I’ve had Dolphin running for hours now without any issues. I was never able to use it for more than a couple minutes at a time before.
I wonder if it has anything to do with the fact that I have a bunch of auto-mounted NFS shares throughout my home directory sourced from different servers. The directory content from those shares does not “exist” until I try to access it, at which point the automounter loads up the NFS share. For example, ~/Pictures and ~/music are handled this way. Maybe it messes something up when Nepomuk tries to access those directories.
Technically, my entire home directory is automounted as an NFS share when I log in. Everything in my user account is hosted on a remote server. That may be part of the problem. Maybe Nepomuk’s indexing gets messed up as a result.
I’m only guessing, though.