[dolphin] [Bug 508130] Dolphin crashing my entire session on debian 13

[email protected]
Newsgroups gmane.comp.kde.devel.kfm
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=508130

--- Comment #2 from [email protected] ---
Hello,
thanks for the answer. Oddly enough the bug hasn't occured for the past 2
days, I don't know why, there hasn't been any updates or changes to my
system.

Looking back I noticed that it's actually x11 that became unresponsive for
some reason (no report in journalctl or anywhere else), so I suppose the
crash is caused by x11 "just vanishing": Here's the journalctl from
*before* the dolphin crash

```
août 11 21:30:48 deksor-ryzen-pc kded6[379057]: org.kde.pulseaudio: No
object for name "bluez_output.xx_xx_xx_xx_xx_xx.1" août 11 21:30:48
deksor-ryzen-pc kded6[379057]: org.kde.pulseaudio: No object for name
"@DEFAULT_SINK@" août 11 21:30:49 deksor-ryzen-pc baloorunner[379629]: The
X11 connection broke (error 1). Did the X11 server die? août 11 21:30:49
deksor-ryzen-pc Discord[379759]: X connection to :0 broken (explicit kill
or server shutdown). août 11 21:30:49 deksor-ryzen-pc dolphin[400278]: The
X11 connection broke (error 1). Did the X11 server die? août 11 21:30:49
deksor-ryzen-pc code[389928]: X connection to :0 broken (explicit kill or
server shutdown). août 11 21:30:49 deksor-ryzen-pc konsole[400514]: The X11
connection broke (error 1). Did the X11 server die? août 11 21:30:49
deksor-ryzen-pc Discord[379686]:
[379686:0811/213049.303901:ERROR:connection.cc(68)] X connection error
received. août 11 21:30:49 deksor-ryzen-pc Discord[379634]:
[379634:0811/213049.306214:FATAL:electron_browser_main_parts.cc(502)]
Failed to shutdown. août 11 21:30:49 deksor-ryzen-pc Discord[379686]: X
connection to :0 broken (explicit kill or server shutdown). août 11
21:30:49 deksor-ryzen-pc Discord[379653]:
[0811/213049.314430:ERROR:elf_dynamic_array_reader.h(64)] tag not found
août 11 21:30:49 deksor-ryzen-pc Discord[379653]:
[0811/213049.314507:ERROR:elf_dynamic_array_reader.h(64)] tag not found
août 11 21:30:49 deksor-ryzen-pc Discord[379653]:
[0811/213049.314574:ERROR:elf_dynamic_array_reader.h(64)] tag not found
août 11 21:30:49 deksor-ryzen-pc systemd[2014]: plasma-baloorunner.service:
Consumed 1.009s CPU time, 21.8M memory peak. août 11 21:30:49
deksor-ryzen-pc Discord[379653]:
[0811/213049.325987:ERROR:file_io_posix.cc(153)] open
/home/deksor/.config/discord/Crashpad/pending/35211df0-50b5-4088-a1b4-0e474d382913.lock:
File exists (17) août 11 21:30:49 deksor-ryzen-pc Discord[379653]:
[0811/213049.326022:ERROR:file_io_posix.cc(153)] open
/home/deksor/.config/discord/Crashpad/pending/5b92bc26-7f64-4349-851d-ddbcc2cfc457.lock:
File exists (17) août 11 21:30:49 deksor-ryzen-pc systemd[2014]:
[email protected]: Main process exited,
code=exited, status=1/FAILURE août 11 21:30:49 deksor-ryzen-pc
kalendarac[379422]: The X11 connection broke (error 1). Did the X11 server
die? août 11 21:30:49 deksor-ryzen-pc kalendarac[379374]: The X11
connection broke (error 1). Did the X11 server die? août 11 21:30:49
deksor-ryzen-pc polkit-kde-authentication-agent-1[379159]: The X11
connection broke (error 1). Did the X11 server die? août 11 21:30:49
deksor-ryzen-pc kded6[379135]: X connection to :0 broken (explicit kill or
server shutdown). août 11 21:30:49 deksor-ryzen-pc
xdg-desktop-portal-kde[379346]: The X11 connection broke (error 1). Did the
X11 server die? août 11 21:30:49 deksor-ryzen-pc
org_kde_powerdevil[379160]: The X11 connection broke (error 1). Did the X11
server die? août 11 21:30:49 deksor-ryzen-pc kwin_x11[379058]: The X11
connection broke: I/O error (code 1) août 11 21:30:49 deksor-ryzen-pc
kwin_x11[379058]: XIO: fatal IO error 2 (Aucun fichier ou dossier de ce
nom) on X server ":0" août 11 21:30:49 deksor-ryzen-pc kwin_x11[379058]:
after 4710580 requests (4710577 known processed) with 0 events remaining.
août 11 21:30:49 deksor-ryzen-pc plasmashell[379108]: The X11 connection
broke: I/O error (code 1) août 11 21:30:49 deksor-ryzen-pc
plasmashell[379108]: XIO: fatal IO error 2 (Aucun fichier ou dossier de ce
nom) on X server ":0" août 11 21:30:49 deksor-ryzen-pc plasmashell[379108]:
after 84209 requests (68699 known processed) with 0 events remaining. août
11 21:30:49 deksor-ryzen-pc DiscoverNotifier[379306]: The X11 connection
broke (error 1). Did the X11 server die? août 11 21:30:49 deksor-ryzen-pc
kscreen_backend_launcher[379138]: The X11 connection broke (error 1). Did
the X11 server die? août 11 21:30:49 deksor-ryzen-pc
kactivitymanagerd[379111]: The X11 connection broke (error 1). Did the X11
server die? août 11 21:30:49 deksor-ryzen-pc kactivitymanagerd[379111]:
QThreadStorage: Thread 0x563a5f920510 exited after QThreadStorage 6
destroyed août 11 21:30:49 deksor-ryzen-pc kactivitymanagerd[379111]:
QThreadStorage: Thread 0x563a5f920510 exited after QThreadStorage 2
destroyed août 11 21:30:49 deksor-ryzen-pc kactivitymanagerd[379111]:
QThreadStorage: Thread 0x563a5f920510 exited after QThreadStorage 1
destroyed août 11 21:30:49 deksor-ryzen-pc kactivitymanagerd[379111]:
QThreadStorage: Thread 0x563a5f920510 exited after QThreadStorage 0
destroyed août 11 21:30:49 deksor-ryzen-pc gmenudbusmenuproxy[379157]: The
X11 connection broke (error 1). Did the X11 server die? août 11 21:30:49
deksor-ryzen-pc gmenudbusmenuproxy[379157]: QThreadStorage: Thread
0x55e31ac294c0 exited after QThreadStorage 1 destroyed août 11 21:30:49
deksor-ryzen-pc gmenudbusmenuproxy[379157]: QThreadStorage: Thread
0x55e31ac294c0 exited after QThreadStorage 0 destroyed août 11 21:30:49
deksor-ryzen-pc kglobalacceld[379016]: The X11 connection broke (error 1).
Did the X11 server die? août 11 21:30:49 deksor-ryzen-pc
kglobalacceld[379016]: The X11 connection broke: I/O error (code 1) août 11
21:30:49 deksor-ryzen-pc kglobalacceld[379016]: X connection to :0 broken
(explicit kill or server shutdown). août 11 21:30:49 deksor-ryzen-pc
kglobalacceld[379016]: QThreadStorage: Thread 0x56369832d8d0 exited after
QThreadStorage 7 destroyed août 11 21:30:49 deksor-ryzen-pc
kglobalacceld[379016]: QThreadStorage: Thread 0x56369832d8d0 exited after
QThreadStorage 3 destroyed août 11 21:30:49 deksor-ryzen-pc
kglobalacceld[379016]: QThreadStorage: Thread 0x56369832d8d0 exited after
QThreadStorage 2 destroyed août 11 21:30:49 deksor-ryzen-pc
kglobalacceld[379016]: QThreadStorage: Thread 0x56369832d8d0 exited after
QThreadStorage 0 destroyed août 11 21:30:49 deksor-ryzen-pc kded6[379057]:
The X11 connection broke (error 1). Did the X11 server die? août 11
21:30:49 deksor-ryzen-pc kalendarac[379381]: org.kde.pim.akonadiserver:
Subscriber "SpecialCollectionsMonitor - 94169024258368" disconnected août
11 21:30:49 deksor-ryzen-pc xembedsniproxy[379161]: The X11 connection
broke (error 1). Did the X11 server die? août 11 21:30:49 deksor-ryzen-pc
ksmserver[379055]: The X11 connection broke (error 1). Did the X11 server
die? août 11 21:30:49 deksor-ryzen-pc kaccess[379158]: The X11 connection
broke (error 1). Did the X11 server die? août 11 21:30:49 deksor-ryzen-pc
systemd[2014]: plasma-kscreen.service: Main process exited, code=exited,
status=1/FAILURE août 11 21:30:49 deksor-ryzen-pc kalendarac[379374]:
QThreadStorage: Thread 0x563626214cc0 exited after QThreadStorage 2
destroyed août 11 21:30:49 deksor-ryzen-pc kalendarac[379374]:
QThreadStorage: Thread 0x563626214cc0 exited after QThreadStorage 1
destroyed août 11 21:30:49 deksor-ryzen-pc systemd[2014]:
plasma-kscreen.service: Failed with result 'exit-code'. août 11 21:30:49
deksor-ryzen-pc kalendarac[379418]: The X11 connection broke (error 1). Did
the X11 server die? août 11 21:30:49 deksor-ryzen-pc kalendarac[379424]:
The X11 connection broke (error 1). Did the X11 server die? août 11
21:30:49 deksor-ryzen-pc kalendarac[379427]: The X11 connection broke
(error 1). Did the X11 server die? août 11 21:30:49 deksor-ryzen-pc
systemsettings[383389]: The X11 connection broke (error 1). Did the X11
server die? août 11 21:30:49 deksor-ryzen-pc kdeconnectd[379281]:
2025-08-11T21:30:49 default: The X11 connection broke (error 1). Did the
X11 server die? août 11 21:30:49 deksor-ryzen-pc kalendarac[379381]:
org.kde.pim.akonadiserver: Control process died, exiting! août 11 21:30:49
deksor-ryzen-pc at-spi-bus-launcher[379339]: X connection to :0 broken
(explicit kill or server shutdown). août 11 21:30:49 deksor-ryzen-pc
systemd[2014]: plasma-xembedsniproxy.service: Main process exited,
code=exited, status=1/FAILURE ``` I think that I have been too quick to
blame dolphin for this issue, but I'm a bit lost about what exactly
happened here and why it "fixed itself" since. I will report back if it
happens again however. Anyways thanks a lot for the work you and the KDE
team put in KDE, I really like it !

Le mer. 13 août 2025 à 19:34, TraceyC <[email protected]> a écrit :

> https://bugs.kde.org/show_bug.cgi?id=508130
>
> TraceyC <[email protected]> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |BACKTRACE
>                  CC|                            |[email protected]
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from TraceyC <[email protected]> ---
> Thank you for the bug report. I'm not able to reproduce this on git-master.
> Unfortunately the backtrace is incomplete and missing debug symbols for the
> following lines that we need to figure out exactly what's going wrong:
>
> #4  0x000055981f568aa6 n/a (/usr/bin/dolphin + 0x5aaa6)
> #10 0x00007f5c3b5fbc24 n/a (libQt6Core.so.6 + 0x3fbc24)
>
> Could you please install debug symbols and attach a new symbolicated
> backtrace
> generated by using `coredumpctl gdb` in a terminal window? See
>
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
> for details about how to do this. Thanks again!
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.