Bug 467343 - Dolphin permanently hung when modifying directory name via expanded tree view in main pane.
Summary: Dolphin permanently hung when modifying directory name via expanded tree view...
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.12.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-03-14 17:05 UTC by Roke Julian Lockhart Beedell
Modified: 2024-06-14 11:11 UTC (History)
2 users (show)

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


Attachments
Dolphin being unable to apply a rename after a rename. (1.17 MB, video/webm)
2024-06-04 10:06 UTC, Roke Julian Lockhart Beedell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roke Julian Lockhart Beedell 2023-03-14 17:05:35 UTC
Application: dolphin (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.2-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
The path of the directory was

```
/run/media/rokejulianlockhart/4b2478fd-5b2b-4927-91fb-19d9c9ef3087/#entities/[third='Beedell',	first='Roke'](https%3A%2F%2Fwim.nl.tab.digital%2Fapps%2Fcontacts%2FAll%2520contacts%2F4d67df6e-4c6c-4a49-8f83-bfbb6b68a933~contacts)/#media/#imagery/2-dimensional (pictography)/scans/#education/[G]eneral [C]ertificate of [S]econdary [E]ducation (#GCSE)/
```

When I reinitialized Dolphin (I was able to close it - despite it being hung - by simply clicking the X in the corner provided by KWin's Window Decorations panel) the previous path was open, albeit not in the selected tab. Navigating to that tab demonstrated that the path that I was viewing no longer existed. I navigated 3 directories above, and back down, and no data was lost, nor was the structure altered. Consequently, I assume that I must have modified the name of a higher directory and then its child directory via Dolphin simultaneously somehow, this confusing it.

DrKonqi appeared immediately after it hang. It never crashed, as previously explained. However, when hung, Dolphin itself (not KWin) was entirely unresponsive.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x00007fa5be327638 in KFileItem::~KFileItem() () from /lib64/libKF5KIOCore.so.5
#5  0x00007fa5be399eed in ?? () from /lib64/libKF5KIOCore.so.5
#6  0x00007fa5be3ad0f6 in ?? () from /lib64/libKF5KIOCore.so.5
#7  0x00007fa5be39ec3c in ?? () from /lib64/libKF5KIOCore.so.5
#8  0x00007fa5bc71338d in ?? () from /lib64/libQt5Core.so.5
#9  0x00007fa5bdb81e75 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5
#10 0x00007fa5bdb860db in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5
#11 0x00007fa5bdb86186 in KJob::kill(KJob::KillVerbosity) () from /lib64/libKF5CoreAddons.so.5
#12 0x00007fa5be3959c2 in ?? () from /lib64/libKF5KIOCore.so.5
#13 0x00007fa5be39b520 in ?? () from /lib64/libKF5KIOCore.so.5
#14 0x00007fa5be39b92f in ?? () from /lib64/libKF5KIOCore.so.5
#15 0x00007fa5be8d570c in KFileItemModel::refreshDirectory(QUrl const&) () from /lib64/libdolphinprivate.so.5
#16 0x00007fa5be93ffda in DolphinView::reload() () from /lib64/libdolphinprivate.so.5
#17 0x000055fe68173e96 in ?? ()
#18 0x00007fa5bc71338d in ?? () from /lib64/libQt5Core.so.5
#19 0x00007fa5bd39ebb2 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5
#20 0x00007fa5bd3a16fb in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5
#21 0x00007fa5bd3a22cd in QAction::event(QEvent*) () from /lib64/libQt5Widgets.so.5
#22 0x00007fa5bd3a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#23 0x00007fa5bc6dc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#24 0x00007fa5bcbaadfb in QShortcutMap::dispatchEvent(QKeyEvent*) () from /lib64/libQt5Gui.so.5
#25 0x00007fa5bcbab74b in QShortcutMap::tryShortcut(QKeyEvent*) () from /lib64/libQt5Gui.so.5
#26 0x00007fa5bcb52826 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /lib64/libQt5Gui.so.5
#27 0x00007fa5bcb774bd in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib64/libQt5Gui.so.5
#28 0x00007fa5bcb4f26c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Gui.so.5
#29 0x00007fa5ba1835d0 in ?? () from /lib64/libQt5WaylandClient.so.5
#30 0x00007fa5ba31ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#31 0x00007fa5ba31be48 in ?? () from /lib64/libglib-2.0.so.0
#32 0x00007fa5ba31bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#33 0x00007fa5bc733c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#34 0x00007fa5bc6dac5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#35 0x00007fa5bc6e2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#36 0x000055fe68171719 in ?? ()
#37 0x00007fa5bbe2caf0 in __libc_start_call_main () from /lib64/libc.so.6
#38 0x00007fa5bbe2cbb9 in __libc_start_main_impl () from /lib64/libc.so.6
#39 0x000055fe68171d85 in ?? ()
[Inferior 1 (process 7740) detached]

Reported using DrKonqi
Comment 1 Roke Julian Lockhart Beedell 2023-03-14 17:19:29 UTC
Drkonqi has hung, as well, just like in https://bugs.kde.org/show_bug.cgi?id=466427#c2
Comment 2 Akseli Lahtinen 2024-06-04 08:13:42 UTC
Hi, have you encountered this bug again?
Comment 3 Roke Julian Lockhart Beedell 2024-06-04 10:06:59 UTC
Created attachment 170129 [details]
Dolphin being unable to apply a rename after a rename.

(In reply to Akseli Lahtinen from comment #2)
Not to my knowledge, although considering how rare saving a new name for an inode whilst it's been programmatically renamed in the background must be, I'm not surprised. I tried to recreate it, and although it's buggy (as the attached video demonstrates) it doesn't appear easily reproducible.
Comment 4 Akseli Lahtinen 2024-06-14 11:11:14 UTC
Alright, thanks for the report! I am marking this as resolved then, but if you encounter it again, feel free to reopen this bug (or make new one!)