[dolphin] [Bug 504981] New: Dolphin SMB Authentication Shortcut Crash
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Thu May 29 20:13:35 BST 2025
https://bugs.kde.org/show_bug.cgi?id=504981
Bug ID: 504981
Summary: Dolphin SMB Authentication Shortcut Crash
Classification: Applications
Product: dolphin
Version First 25.04.1
Reported In:
Platform: unspecified
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: estefan at lfctech.org
CC: kfm-devel at kde.org
Target Milestone: ---
Application: dolphin (25.04.1)
ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.14.0
Operating System: Linux 6.11.0-26-generic x86_64
Windowing System: X11
Distribution: KDE neon 6.3
DrKonqi: 6.3.5 [CoredumpBackend]
-- Information about the crash:
I have SMB shortcuts in my "Remote" section of Dolphin. I am on KDE neon 6.3
When clicking a shortcut, Dolphin crashes with the provided error logs and
message.
This is the shortcut:
smb://SERVERIPHERE/ShareName/
This share requires authentication to access. The authentication is saved in my
computer.
I fixed the crash by changing the shortcut to:
smb://USER@SERVERIPHERE/ShareName/
This no longer results in a crash and functions as intended :) it appears that
adding the intended authenticated user to the path prevents the crash somehow.
Samba shares that do NOT require authentication to access do NOT experience
this crash.
The crash can be reproduced every time.
-- Backtrace (Reduced):
#6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>)
at ./nptl/pthread_kill.c:44
#7 __pthread_kill_internal (signo=6, threadid=<optimized out>) at
./nptl/pthread_kill.c:78
#8 __GI___pthread_kill (threadid=<optimized out>, signo=signo at entry=6) at
./nptl/pthread_kill.c:89
#9 0x00007c612384527e in __GI_raise (sig=sig at entry=6) at
../sysdeps/posix/raise.c:26
#10 0x00007c61238288ff in __GI_abort () at ./stdlib/abort.c:79
Reported using DrKonqi
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list