Version is actually 4.14.1, but that choice was not offerred in the form. I believe I was seeing the same issue under 4.14.0. *Nearly* every time I right click on a file in Dolphin, it crashes. Sometimes it does not. It does NOT crash when I right-click a folder. The automatic bug report tool has not been able to gather data that it says will be useful, so I'm happy to provide any info that might help. I have experienced this bug fairly consistently under both Manjaro and Netrunner-Rolling over the course of the past couple of months. I'm tempted to choose "Happens Every Time" under reproducibility, because it's so very close to being every single time - but not quite. I have no particularly bizarre configurations, Dolphin is in a nearly default state. And, I'm not using split pane or any other advanced features to make this happen. All I have to do to reproduce is open dolphin, and right click a file, and dolphin will (nearly always) crash. Launching via terminal does not produce any output that (to me) looks useful. Reproducible: Sometimes Steps to Reproduce: 1. Launch Dolphin by any means. 2. Right click a file. 3. Watch Dolphin crash. Actual Results: Dolphin crashed. Expected Results: Not crash. Here is terminal output during a crash if it helps. The last 4 of lines don't appear until after I close the KDE crash notifier, and you'll see that I have to CTRL-C, but I'm not sure why. [joe@caemlyn ~]$ dolphin dolphin(12993) KXMLGUI::ActionList::plug: Index 25 is not within range (0 - 13 Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) dolphin(12993)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: dolphin(12993) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf WARNING: Ignoring invalid value 'share' for parameter 'security' Loaded services file OK. " QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied QFileSystemWatcher: failed to add paths: /var/lib/samba/usershares KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/joe/.kde4/socket-caemlyn/kdeinit4__0 [1]+ Stopped dolphin [joe@caemlyn ~]$ QSocketNotifier: Invalid socket 23 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... ^C [1]+ Exit 253 dolphin
Please add the backtrace for the crash, even if incomplete. Also, try with a freshly created user account.
Moreover, you could try to obtain a Valgrind log, see https://community.kde.org/Dolphin/FAQ/Crashes for details. Another thing that you could do is to disable the context menu plugins ("Configure Dolphin" -> "Services") one by one and try if the crash is still reproducible after each step.
By some ironic travesty, I can't seem to reproduce it now - despite that it's been eating at me for at least 2 months. But by coincidence, I did also change the options provided by the "root actions" context menu, which I hadn't done before. So Frank Reininghaus may have been on the right track. Sorry for the unhelpful comment, didn't want to appear to be ignoring the responses. Soon I will make a new user and try there, which should be sufficient to reproduce if my config changes "fixed" it, since I was using the default config previously.
Thanks for the feedback. If you can reproduce the problem at some point and you can provide helpful information (such as a backtrace), please let us know and either reopen this report or report the problem directly to the authors of the buggy context menu plugin.
Sorry for the delay - it did come back without having to create a fresh user or take any special action, have just had a busy few days. Here is the backtrace info as provided by the bug reporting tool - I'm concerned that this still doesn't look like much to go on though, so if I can provide more info please let me know. Application: Dolphin (dolphin), signal: Segmentation fault [Current thread is 1 (process 22196)] Thread 1 (process 22196): #0 0x00007fb14027379d in ?? () #1 0x0000000000000000 in ?? ()
(In reply to wavemotiongun from comment #5) > Here is the backtrace info as provided by the bug reporting tool - I'm > concerned that this still doesn't look like much to go on though, so if I > can provide more info please let me know. Thanks for the update. The backtrace is not really detailed, unfortunately - without any additional information, it's impossible to do anything about the problem. As I said in comment 2, disabling all context menu plugins and checking if that fixes the problem would be an option. Moreover, a more detailed backtrace and/or a Valgrind log would be helpful: https://community.kde.org/Dolphin/FAQ/Crashes Thanks for your help!
My apologies for letting this languish so long. Your suggestion fixed my issue, and again I'm sorry for not coming back to update the bug.