Dolphin refuses to open.

judd

Active Member

Reaction score: 201
Messages: 237

Hi, I've probably touched something in dolphin and I don't remember what it was, because if I could open it, it would be easier to find out what I did wrong ... trying to open it by console it throws me:

Code:
% dolphin
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-solo'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-solo'
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = dolphin path = /usr/local/bin pid = 69205
KCrash: Arguments: /usr/local/bin/dolphin
KCrash: Attempting to start /usr/local/lib/libexec/drkonqi
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-solo'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-solo'

Suspended (signal)

There is also a window to restart the application, but it doesn't do it.

Thank you for your help!
 
OP
judd

judd

Active Member

Reaction score: 201
Messages: 237

Alexander88207

Thank you for your response.
I don't have anything in those files, but with pcmanfm I got by without any problems and I haven't lost any of my files.
 

astyle

Aspiring Daemon

Reaction score: 348
Messages: 815

Looking at this console dump, it looks just like mine did when I was trying Wayland earlier this year, before FreeBSD 13-RELEASE was finally released. Your QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-solo' is the result of messing with settings that supposedly help Wayland get started. I never cleaned that up properly, messed my whole system up, and decided to reinstall from scratch. Fortunately, this happened on an SSD that was pretty much set up for that kind of scenario - play, make mistakes, learn from them, wipe clean.
 
Top