Bug 488428 - Opening Dolphin always shows a message kioworker closed unexpectedly (Crash in TrashImpl::readInfoFile)
Summary: Opening Dolphin always shows a message kioworker closed unexpectedly (Crash i...
Status: RESOLVED DUPLICATE of bug 486697
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Trash (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-12 19:55 UTC by Vincent
Modified: 2024-06-13 18:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Report from kioworker crash handler (it says that the generated crash information is useful) (2.25 KB, text/vnd.kde.kcrash-report)
2024-06-12 19:55 UTC, Vincent
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent 2024-06-12 19:55:02 UTC
Created attachment 170436 [details]
Report from kioworker crash handler (it says that the generated crash information is useful)

SUMMARY
Opening Dolphin always shows a message kioworker closed unexpectedly

STEPS TO REPRODUCE
1. Open Dolphin.

OBSERVED RESULT
Dolphin is opened successfully but there's always some kind of crash of Dr Konqi kioworker.

EXPECTED RESULT
No crash.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Attaching a crash report.
Comment 1 Nate Graham 2024-06-13 18:54:13 UTC
Application: kioworker (kioworker), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=126442726900352) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=126442726900352) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=126442726900352, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x000072ffc1c42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x000072ffc1c287f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x000072ffc24fdb6e in qAbort() () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#10 0x000072ffc24f820a in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#11 0x000072ffc24fe511 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#12 0x000072ffc24c2ac2 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#13 0x000072ffbdcffb13 in TrashImpl::readInfoFile (trashId=0, info=..., infoPath=..., this=0x7ffd82fe52e0) at ./src/kioworkers/trash/trashimpl.cpp:782
#14 TrashImpl::infoForFile (this=0x7ffd82fe52e0, trashId=0, fileId=..., info=...) at ./src/kioworkers/trash/trashimpl.cpp:735
#15 0x000072ffbdd042f8 in TrashImpl::list (this=0x7ffd82fe52e0) at ./src/kioworkers/trash/trashimpl.cpp:715
#16 0x000072ffbdd05ee6 in TrashProtocol::listRoot (this=0x7ffd82fe52c0) at ./src/kioworkers/trash/kio_trash.cpp:506
#17 TrashProtocol::listDir (this=0x7ffd82fe52c0, url=...) at ./src/kioworkers/trash/kio_trash.cpp:403
#18 0x000072ffc270a8b8 in KIO::WorkerSlaveBaseBridge::listDir (this=0x5d4f420f0280, url=...) at ./src/core/workerbase_p.h:121
#19 0x000072ffc2707786 in KIO::SlaveBase::dispatch (this=0x5d4f420f0280, command=71, data=...) at ./src/core/slavebase.cpp:1229
#20 0x000072ffc27ba76a in KIO::SlaveBase::dispatchLoop() [clone .constprop.0] (this=<optimized out>) at ./src/core/slavebase.cpp:350
#21 0x000072ffc2704ccd in KIO::WorkerBase::dispatchLoop (this=<optimized out>) at ./src/core/workerbase.cpp:27
#22 0x000072ffbdd03ae9 in kdemain (argc=<optimized out>, argc@entry=4, argv=<optimized out>) at ./src/kioworkers/trash/kio_trash.cpp:48
#23 0x00005d4f40bb15a0 in main (argc=5, argv=0x7ffd82fe5658) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qvarlengtharray.h:84
[Inferior 1 (process 98890) detached]
Comment 2 Nate Graham 2024-06-13 18:55:57 UTC
Aha, this is Bug 486697.

*** This bug has been marked as a duplicate of bug 486697 ***