Bug 481936 - Dolphin crash after system wakeup from sleep
Summary: Dolphin crash after system wakeup from sleep
Status: RESOLVED DUPLICATE of bug 470845
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 23.08.1
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-02-28 15:00 UTC by matrais
Modified: 2024-02-28 15:29 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matrais 2024-02-28 15:00:44 UTC
Application: dolphin (23.08.1)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.6.15-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Hi,

Dolphin crashes when opening, all the time, no matter how many times I click on the icon. 
Fresh install of Debian Stable (12) and apt dist-upgraded to Testing successfully without any errors. 

HW setup:
- ASUS TUF GAMING B550 PRO
- Ryzen 5 PRO 4650G (integrated GPU)
- 2x16G Samsung DDR4-2400@3200 (Samsung B-Die) ECC UDIMM (ECC checked, working fine)
Quite a stable hw, I expect no issues here, quality parts and 7/24 proven since about a year now. 

SW setup:
- boot from USB pendrive (Debian UEFI install)
- /boot created with the installer onto another USB pendrive
- / created with the installer onto a USB-C external 250G SSD (Verbatim, 1-week new, HD Sentinel reports 100/100, surface R/W tested)
- aforementioned external SSD is LUKS encrypted, / is on /dev/mapper.. - the unlocked part

What happened:
- system went to sleep while I was doing home office work
- woke up, I typed in my lock screen password
- I was back to KDE (kde-full) with Firefox running, nothing else
- clicked on Dolphin - crash. And again. And again. It won't start anymore. 

I'll reboot and check if the issue still persists. If it's gone, maybe it's somehow related to the sleep and then wake-up process, however I see no issues, file sys is mounted, Midnight Commander starting, everything is working fine.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007f21d69b0748 in Solid::StorageAccess::isEncrypted() const () from /lib/x86_64-linux-gnu/libKF5Solid.so.5
#5  0x00007f21d6de2937 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#6  0x00007f21d6de2a66 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#7  0x00007f21d6de7851 in KIO::PreviewJob::slotResult(KJob*) () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#8  0x00007f21d4d062b2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f21d62bb979 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#10 0x00007f21d62bceeb in ?? () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#11 0x00007f21d4d062b2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f21d6b4003a in KIO::SlaveInterface::error(int, QString const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#13 0x00007f21d6b423a7 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#14 0x00007f21d6b408fa in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#15 0x00007f21d6b45791 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#16 0x00007f21d4d062b2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f21d4cf9940 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f21d5962f32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f21d4ccc748 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f21d4ccfe51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f21d4d28697 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f21d2b111f4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f21d2b14317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f21d2b14930 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f21d4d27d4a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f21d4ccb0fb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00007f21d4cd38a4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x000055bff990217e in ?? ()
#29 0x00007f21d5ee56ca in __libc_start_call_main (main=main@entry=0x55bff9900ed0, argc=argc@entry=1, argv=argv@entry=0x7ffc5b6e0958) at ../sysdeps/nptl/libc_start_call_main.h:58
#30 0x00007f21d5ee5785 in __libc_start_main_impl (main=0x55bff9900ed0, argc=1, argv=0x7ffc5b6e0958, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc5b6e0948) at ../csu/libc-start.c:360
#31 0x000055bff99026b1 in ?? ()
[Inferior 1 (process 3526) detached]

Reported using DrKonqi
Comment 1 matrais 2024-02-28 15:08:30 UTC
As promised, rebooted the system. 
Dolphin starts flawlessly.
Comment 2 fanzhuyifan 2024-02-28 15:29:23 UTC
Fixed in frameworks 5.108. Unfortunately it seems that even testing on debian isn't on that yet..........

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