Crash when opening any Dolphin window. STEPS TO REPRODUCE 1. Request opening any Dolphin window, by any available means (shortcut, through the application launcher, opening folder from any application...) OBSERVED RESULT No Dolphin window appears. Instead, the KDE Crash Handler pops up. EXPECTED RESULT A Dolphin window. SOFTWARE/OS VERSIONS Application: kdeinit5 (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.9.0-1-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid ADDITIONAL INFORMATION
Can you attach a backtrace of the crash? https://community.kde.org/Get_Involved/Issue_Reporting#Crash_reports_must_include_backtraces
I will try to install the required packs to get the backtrace. Probably not until the weekend, though.
Hello, Nate. Last weekend a regular update of packages left my KDE installation all broken: I couldn't even log in. So I reinstalled Debian 9 from an old DVD. I want to go back to Plasma 4 anyway. But what I got instead is Plasma 5 with Dolphin still crashing from a fresh installation of an older version (16.08.3). This sounds as though the problem is in my machine, but my machine hasn't changed from the latest times Dolphin worked to the current situation. Plus, Dolphin is the only one that seems to be presenting this sort of behavior. Anyway, I wanted to generate a good backtrace, so I look at the list of missing files that the crash handler says I'm missing: /usr/bin/dolphin /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so Wrong start: I have them all. Anyway, the I think I'm getting enough information from the stack trace and from running it with GDB: Thread 1 (Thread 0x7f8c111d8e00 (LWP 4464)): [KCrash Handler] #6 0x00007f8c24b44fff in raise () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007f8c24b4642a in abort () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x00007f8c2246249b in KXMLGUIClient::setXML(QString const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #9 0x00007f8c22462d19 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #10 0x00007f8c2247ef27 in KXmlGuiWindow::createGUI(QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #11 0x00007f8c224801cb in KXmlGuiWindow::setupGUI(QSize const&, QFlags<KXmlGuiWindow::StandardWindowOption>, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #12 0x00007f8c224802e2 in KXmlGuiWindow::setupGUI(QFlags<KXmlGuiWindow::StandardWindowOption>, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #13 0x00007f8c24efc64d in DolphinMainWindow::DolphinMainWindow (this=0x5632141c0880, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at ./src/dolphinmainwindow.cpp:146 #14 0x00007f8c24f1130f in kdemain (argc=<optimized out>, argv=<optimized out>) at ./src/main.cpp:130 #15 0x00007f8c24b322e1 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #16 0x000056321264b7ba in _start () Debugging, I get this message the third time I enter KXMLGUIClient::setXML : «Error parsing XML document: "unexpected character" at line 153 column 1». Unfortunately I haven't found out which XML file is it reading, which contains that "unexpected character".
Thanks, looks like it's in KXMLGUIClient::setXML() That makes it the same issue as Bug 400271. Deleting ~/.local/share/kxmlgui5/dolphin/dolphinui.rc should fix the problem. Alternatively, you can open the file and try to find the error in it that is causing the crash. *** This bug has been marked as a duplicate of bug 400271 ***