Bug 510378

Summary:	Dolphin freeze when network connection to NAS is interrupted
Product:	[Applications] dolphin	Reporter:	Rüdiger <linux>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	REPORTED ---
Severity:	crash	CC:	dolphin-bugs-null, kdedev, linux
Priority:	NOR
Version First Reported In:	25.08.1
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=423187
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rüdiger 2025-10-08 08:14:57 UTC

***
I have set a bookmark for mounting my NAS via /mnt/samba/NAS.
If my NAS is turned on and WLAN is connected there is no problem at all. But if I have opened a window to a NAS folder in Dolphin like /mnt/samba/NAS/ and have turned off either my network connection or my NAS than Dolphin always freezes. Probably because it is searching continously for the NAS connection. But this is a real problem. If there is no more connection to the NAS Dolphin should "accept and leave" it.
***


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.8-1-MANJARO (64-bit)

Comment 1 TraceyC 2025-10-08 19:58:17 UTC

As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

If there isn't a coredump, then this is a freeze, rather than a crash.

Thanks.

Comment 2 Rüdiger 2025-10-09 15:35:02 UTC

I am using archlinux Manjaro with KDE Plasma. Having asked AI. Which command output would you need for to get a helpful failure report?

# Dolphin-Logs seit gestern
journalctl --since yesterday -u plasma-dolphin.service

# Oder alle Dolphin-bezogenen Logs
journalctl --since yesterday | grep -i dolphin

# Letzte Woche, nur Fehler und kritische Meldungen
journalctl --since "1 week ago" --priority=err | grep -i dolphin

# Alle Dolphin-relevanten Einträge mit Zeitstempel
journalctl -b -g dolphin --since "1 week ago"

Comment 3 Rüdiger 2025-10-09 15:35:58 UTC

By the way. I believe it is a freeze because of a missing connection.

Comment 4 TraceyC 2025-10-09 17:01:08 UTC

It's more likely a freeze, since Dolphin doesn't exit and Dr Konqui (the crash reporter) doesn't appear.

Be mindful of using AI to try to get advice on how to troubleshoot. AIs hallucinate and cannot be trusted to produce accurate technical data. None of the commands you were provided would get a crash dump.

In terms of the freeze, the commands you were provided would produce a lot of noise, and not be very helpful. It would also exclude information from kioworker, which is responsible for communicating with IO.

The most helpful logs for Dolphin would be gotten through Valgrind
See [https://community.kde.org/Dolphin/FAQ/Crashes](https://community.kde.org/Dolphin/FAQ/Crashes) for how to use it to get those logs. You'll probably need to install valgrind before you can use it to run Dolphin.

Note that the FAQ talks about crashes, which is not what's happening here, but the logs will still be potentially useful. Thanks.

Comment 5 Rüdiger 2025-10-13 08:13:26 UTC

Would you kindly give me a clear step by step instruction how to use valgrind for a failure report of dolphhin. Thanks.

Comment 6 TraceyC 2025-10-14 19:58:29 UTC

(In reply to Rüdiger from comment #5)
> Would you kindly give me a clear step by step instruction how to use
> valgrind for a failure report of dolphhin. Thanks.

The link I provided has steps on how to use Valgrind for this. Please have a read. Thanks.

Comment 7 Bug Janitor Service 2025-10-29 03:47:52 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Rüdiger 2025-11-02 07:16:09 UTC

Here is the log with "valgrind dolphin 2> log.txt" I got after freezing dolphin because of missing network connection to NAS

==80764== Memcheck, a memory error detector
==80764== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==80764== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info
==80764== Command: dolphin
==80764== 
==80764== Syscall param writev(vector[0]) points to uninitialised byte(s)
==80764==    at 0x76F36D0: writev (writev.c:26)
==80764==    by 0x83BC3DD: UnknownInlinedFun (xcb_conn.c:296)
==80764==    by 0x83BC3DD: _xcb_conn_wait.part.0 (xcb_conn.c:553)
==80764==    by 0x83BC55F: UnknownInlinedFun (xcb_out.c:469)
==80764==    by 0x83BC55F: _xcb_out_send (xcb_out.c:470)
==80764==    by 0x83BC7D6: _xcb_out_flush_to (xcb_out.c:495)
==80764==    by 0x83BC9A4: wait_for_reply (xcb_in.c:514)
==80764==    by 0x83BDB45: xcb_wait_for_reply (xcb_in.c:552)
==80764==    by 0xEC7ADAF: QXcbConnection::initializeScreensFromMonitor(xcb_screen_iterator_t*, int, QXcbScreen**, bool) (in /usr/lib/libQt6XcbQpa.so.6.9.2)
==80764==    by 0xEC7CD86: QXcbConnection::initializeScreens(bool) (in /usr/lib/libQt6XcbQpa.so.6.9.2)
==80764==    by 0xEC72ED2: QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (in /usr/lib/libQt6XcbQpa.so.6.9.2)
==80764==  Address 0xe4ce885 is 4,533 bytes inside a block of size 21,176 alloc'd
==80764==    at 0x49A7C13: calloc (vg_replace_malloc.c:1675)
==80764==    by 0x83BEF05: xcb_connect_to_fd (xcb_conn.c:368)
==80764==    by 0x83BFC58: xcb_connect_to_display_with_auth_info (xcb_util.c:563)
==80764==    by 0x82AB1BA: _XConnectXCB (xcb_disp.c:78)
==80764==    by 0x829B7AF: XOpenDisplay (OpenDis.c:129)
==80764==    by 0xEC76A05: QXcbBasicConnection::QXcbBasicConnection(char const*) (in /usr/lib/libQt6XcbQpa.so.6.9.2)
==80764==    by 0xEC72C78: QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (in /usr/lib/libQt6XcbQpa.so.6.9.2)
==80764==    by 0xEC9EB21: QXcbIntegration::QXcbIntegration(QList<QString> const&, int&, char**) (in /usr/lib/libQt6XcbQpa.so.6.9.2)
==80764==    by 0x49B9389: ??? (in /usr/lib/qt6/plugins/platforms/libqxcb.so)
==80764==    by 0x64F9197: QGuiApplicationPrivate::createPlatformIntegration() (in /usr/lib/libQt6Gui.so.6.9.2)
==80764==    by 0x64FA627: QGuiApplicationPrivate::createEventDispatcher() (in /usr/lib/libQt6Gui.so.6.9.2)
==80764==    by 0x6E83654: QCoreApplicationPrivate::init() (in /usr/lib/libQt6Core.so.6.9.2)
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20813B81: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20874ED1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20876B21: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x208787A1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2087A541: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2087BCB1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2087D521: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2087ECF1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20880621: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x208821D1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20883B01: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x208853B1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20886ED1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x20888C21: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2088AAF1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2089B091: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2089C671: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2089DC71: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x2089FC81: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x208A20D1: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x208A5081: ???
==80764== 
==80764== Conditional jump or move depends on uninitialised value(s)
==80764==    at 0x20355EA4: ???
==80764==    by 0x208A6B51: ???
==80764==

Comment 9 TraceyC 2025-11-03 21:02:20 UTC

Thanks for the logs, that looks like it will be useful for the Dolphin developers. I'll let them take it from here.