Bug#1120915: dolphin: After today update dolphin behavior is broken : cannot enter directories
On 11/18/25 13:50, Sune Stolborg Vuorela wrote:
I think you need to install libkf6kiocore6-dbgsym from the debug archive
deb http://deb.debian.org/debian-debug/ unstable-debug main
I did. I also loaded debug symbol from libqt6core6t64 as the backtrace
seems to go there.
and that at least should give better symbols from the backtrace you have.
The backtraces does point to kiocore, which is very much where my initial
suspicion of which part of frameworks would be responsible for this.
/Sune
kf.kio.workers.trash: Root trash dir "/multimedia\u0000/.Trash" exists
but didn't pass the security checks, can't use it
KCrash: Application 'kioworker' crashing... crashRecursionCounter = 2
Thread 20 "KIO::WorkerThre" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffaf6816c0 (LWP 11080)]
__pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=6, no_tid=no_tid@entry=0)
at ./nptl/pthread_kill.c:44
⚠ warning: 44 ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce nom
(gdb) bt
#0 __pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=6, no_tid=no_tid@entry=0)
at ./nptl/pthread_kill.c:44
#1 0x00007ffff4c9571f in __pthread_kill_internal (threadid=<optimized
out>, signo=6) at ./nptl/pthread_kill.c:89
#2 0x00007ffff4c40462 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3 0x00007ffff4c284ac in __GI_abort () at ./stdlib/abort.c:77
#4 0x00007ffff54dc53b in qAbort () at ./src/corelib/global/qassert.cpp:46
#5 qt_message_fatal<QString&> (context=<optimized out>, message=...) at
./src/corelib/global/qlogging.cpp:2149
#6 qt_message(QtMsgType, const QMessageLogContext &, const char *,
typedef __va_list_tag __va_list_tag *)
(msgType=msgType@entry=QtWarningMsg, context=...,
msg=msg@entry=0x7ffff5845198 "Broken filename passed to function",
ap=ap@entry=0x7fffaf67ef48) at ./src/corelib/global/qlogging.cpp:381
#7 0x00007ffff54dc8c9 in QMessageLogger::warning
(this=<optimized out>, msg=0x7ffff5845198 "Broken filename passed
to function") at ./src/corelib/global/qlogging.cpp:633
#8 0x00007ffff550378e in QFileSystemEngine::canonicalName (entry=...,
data=...)
at ./src/corelib/io/qfilesystemengine_unix.cpp:707
#9 0x00007ffff5563fdd in QFileInfoPrivate::getFileName
(this=0x7fffa8007d90,
name=name@entry=QAbstractFileEngine::CanonicalName) at
./src/corelib/io/qfileinfo.cpp:28
#10 0x00007ffff5564bbd in QFileInfo::canonicalFilePath (this=<optimized
out>) at ./src/corelib/io/qfileinfo.cpp:604
#11 0x00007ffff57a2f2b in QStorageInfoPrivate::doStat
(this=0x7fffa8002ea0) at ./src/corelib/io/qstorageinfo_linux.cpp:449
#12 0x00007ffff5587245 in QStorageInfo::QStorageInfo
(this=0x7fffaf680508, path=..., this=<optimized out>,
path=<optimized out>) at ./src/corelib/io/qstorageinfo.cpp:81
#13 0x00007fffba75c674 in ??? () at
/usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/kio_file.so
#14 0x00007ffff782ded5 in KIO::WorkerSlaveBaseBridge::virtual_hook
(this=0x7fffa8001460, id=<optimized out>, data=<optimized out>) at
./src/core/workerbase_p.h:190
#15 0x00007ffff7825dff in KIO::SlaveBase::dispatch (this=0x7fffa8001460,
command=95, data=...) at ./src/core/slavebase.cpp:1292
#16 0x00007ffff782698e in KIO::SlaveBase::dispatchLoop() [clone
.constprop.0] (this=0x7fffa8001460)
at ./src/core/slavebase.cpp:330
#17 0x00007ffff78b8379 in KIO::WorkerThread::run (this=0x55555660cb60)
at ./src/core/workerthread.cpp:47
#18 0x00007ffff571c6e4 in operator() (__closure=<optimized out>) at
./src/corelib/thread/qthread_unix.cpp:434
#19 (anonymous
namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()>
> (t=<optimized out>)
at ./src/corelib/thread/qthread_unix.cpp:366
#20 QThreadPrivate::start (arg=0x55555660cb60) at
./src/corelib/thread/qthread_unix.cpp:394
#21 0x00007ffff4c937db in start_thread (arg=<optimized out>) at
./nptl/pthread_create.c:448
#22 0x00007ffff4d111f8 in __GI___clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
Hope this helps. Do not hesitate to ask for more debug. I did not use
gdb for long time but as an ex embedded os developper I'm quite familiar
to it.
--
Eric Valette
Reply to: