https://bugs.kde.org/show_bug.cgi?id=526653
--- Comment #2 from Villemur Clément <[email protected]> --- (In reply to TraceyC from comment #1) > Thanks for the crash report. As the message at the top of the summary says, > if something crashed, we do need a backtrace of it so we can figure out > what's going on. Can you please attach a backtrace of the crash, as detailed > in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports ? Then, set the status back to REPORTED. > > Thanks. As I said earlier, DrKonqi doesn't see the app crashing. Same for Crashed Process Viewer. When using GDB instead, GDB crashes a few second after starting Dolphin. Should I report this problem to KDE Linux ? GNU gdb (GDB) 18.1 Copyright (C) 2026 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Find the GDB manual online at: ┃ ┃ http://www.gnu.org/software/gdb/documentation/. ┃ ┃ For help, type "help". ┃ ┃ Type "apropos word" to search for commands related to "word". ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ Reading symbols from dolphin... This GDB supports auto-downloading debuginfo from the following URLs: <http://debuginfod.kdeos.haraldsitter.eu> <https://debuginfod.archlinux.org> Enable debuginfod for this session? (y or [n]) y Debuginfod has been enabled. To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit. Reading symbols from /home/maledict/.cache/debuginfod_client/4647b0a7c002fcc3159e7e8aa9fd1cff89d67969/debuginfo... (gdb) run Starting program: /usr/bin/dolphin [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffec9ff6c0 (LWP 6210) (id 2)] [New Thread 0x7fffebdff6c0 (LWP 6211) (id 3)] [New Thread 0x7fffeb5fe6c0 (LWP 6212) (id 4)] [New Thread 0x7fffeaa9b6c0 (LWP 6213) (id 5)] [New Thread 0x7fffea29a6c0 (LWP 6214) (id 6)] [New Thread 0x7fffe9a996c0 (LWP 6215) (id 7)] [New Thread 0x7fffe91ca6c0 (LWP 6216) (id 8)] [New Thread 0x7fffe89b26c0 (LWP 6217) (id 9)] [Detaching after vfork from child process 6218] [New Thread 0x7fffc79ff6c0 (LWP 6220) (id 10)] /usr/include/c++/16/string_view:291: constexpr const std::basic_string_view<_CharT, _Traits>::value_type& std::basic_string_view<_CharT, _Traits>::back() const [with _CharT = char; _Traits = std::char_traits<char>; const_reference = const char&]: Assertion 'this->_M_len > 0' failed. Fatal signal: Abandon ----- Backtrace ----- 0x55ef678da481 ??? 0x55ef67a6e1ed ??? 0x7f952623e6ef ??? 0x7f952629a11c ??? 0x7f952623e5cf gsignal 0x7f9526225684 abort 0x7f952669d5bc _ZSt21__glibcxx_assert_failPKciS0_S0_ 0x55ef67721f73 ??? 0x55ef6773c57d ??? 0x55ef679be638 ??? 0x55ef679bd72a ??? 0x55ef679bd4b5 ??? 0x7f952629d79b ??? 0x7f952629d818 pthread_once 0x55ef6841be6e ??? 0x7f95266ea858 ??? 0x7f9526298041 ??? 0x7f952632072b ??? 0xffffffffffffffff ??? --------------------- A fatal error internal to GDB has been detected, further debugging is not possible. GDB will now terminate. This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. zsh: abort (core dumped) gdb dolphin -- You are receiving this mail because: You are watching all bug changes.
