Bug 511313

Summary:	Dolphin crashes after renaming a folder
Product:	[Applications] dolphin	Reporter:	Laurentiu <chitimia>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	dolphin-bugs-null, kdedev, strong.drum0546
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	23.08.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Laurentiu 2025-10-29 12:18:20 UTC

Application: dolphin (23.08.5)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.0-86-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04.3 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
Situation: 
Computer just wake up from stand-by
4 Dolphin windows opened, each with 3-4 tabs
No file from the target directory was opened

Action:
Rename ~/Directory to ~/Directory1 through Left Click, then type "1" (not using F2 or Right Click > Rename)

Result:
Directory was renamed, but Dolphin window crashed in ~1 sec after pressing "Enter". The other Doplhin windows were not impacted. Other windows and programs were not impacted.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x000076882fcaacb4 in KFileItem::operator==(KFileItem const&) const () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#5  0x000076882fd566eb in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#6  0x000076882fd5fd09 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#7  0x000076882fd65e2e in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#8  0x000076882e112e16 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x000076882fd846b4 in OrgKdeKDirNotifyInterface::FileRenamedWithLocalPath(QString const&, QString const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#10 0x000076882fd85a12 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#11 0x000076882f37979b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x000076882e106343 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x000076882ed6bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x000076882e0d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x000076882e0db94b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x000076882e135c0f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x000076882bd145c5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x000076882bd73737 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x000076882bd13a63 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x000076882e135279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x000076882e0d6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x000076882e0df3e8 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x0000612a628f547a in ?? ()
#24 0x000076882d62a1ca in __libc_start_call_main (main=main@entry=0x612a628f2c60, argc=argc@entry=3, argv=argv@entry=0x7ffd172f42e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#25 0x000076882d62a28b in __libc_start_main_impl (main=0x612a628f2c60, argc=3, argv=0x7ffd172f42e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd172f42d8) at ../csu/libc-start.c:360
#26 0x0000612a628f5c25 in ?? ()
[Inferior 1 (process 4078) detached]

The reporter indicates this bug may be a duplicate of or related to bug 496387.

Reported using DrKonqi

Comment 1 Lenzoid 2025-10-29 22:14:53 UTC

Hi, thanks for your detailed bug report. It looks like you're still using KDE 5 which is not receiving support anymore. You can see an explanation here https://discuss.kde.org/t/how-long-plasma-5-will-be-mantained/7276/6
Shame really because your bug report is high quality.

Comment 2 TraceyC 2025-10-30 00:20:15 UTC

Thanks for the bug report!

As mentioned, Plasma 5.27.12 no longer receives updates or maintenance from KDE; active versions are 6.4.5 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need support for your version of Plasma, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If this issue is still reproducible in a maintained version of Plasma, feel free to re-open this bug report.