[dolphin] [Bug 460004] Dolphin crashes when unmounting external hard drive

[Félix Fernández]

https://bugs.kde.org/show_bug.cgi?id=460004

--- Comment #1 from Félix Fernández <felix.fer.rod at tutanota.de> ---
Created attachment 153314
  --> https://bugs.kde.org/attachment.cgi?id=153314&action=edit
New crash information added by DrKonqi

dolphin (22.08.1) using Qt 5.15.6

The error took place when I was unmounting the LUKS encrypted hard drive I use
for backups. I clicked on the button to unmount the open LUKS partition, then I
clicked on the button to unmount the drive, and Dolphin crashed.
When I opened it again to ensure the drive was correctly unmounted and didn't
break in the process, the drive was unmounted, and mounting it again didn't
raise any errors, so it might be that the drive gets correctly unmounted before
the crash and Dolphin just happens to crash right after unmounting, instead of
during the unmounting process.
However, when I unmounted it again, this error happened again. Trying again
resulted in the same crash, so I suppose that this would hoppen no matter how
many times I tried.

-- Backtrace (Reduced):
#4  0x0000557b550b778a in TerminalPanel::sendCdToTerminal (this=0x557b5606e960,
dir=..., addToHistory=TerminalPanel::HistoryPolicy::SkipHistory) at
/usr/src/debug/dolphin-22.08.1-1.fc36.x86_64/src/panels/terminal/terminalpanel.cpp:264
#5  0x0000557b55097d3d in TerminalPanel::goHome (this=0x557b5606e960) at
/usr/src/debug/dolphin-22.08.1-1.fc36.x86_64/src/panels/terminal/terminalpanel.cpp:58
#6  DolphinMainWindow::slotStorageTearDownFromPlacesRequested
(this=0x557b55cf6290, mountPath=...) at
/usr/src/debug/dolphin-22.08.1-1.fc36.x86_64/src/dolphinmainwindow.cpp:1426
#7  0x00007f8a79cdb9a6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc181d55e0,
r=<optimized out>, this=0x557b5607ecf0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x557b55d34a80, signal_index=24,
argv=0x7ffc181d55e0) at kernel/qobject.cpp:3919

-- 
You are receiving this mail because:
You are on the CC list for the bug.