Bug 456392 - Dolphin should not become fully unresponsive when accessing a drive which blocks (eg due a faulty connection)
Summary: Dolphin should not become fully unresponsive when accessing a drive which blo...
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.04.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-06 10:23 UTC by postix
Modified: 2024-07-04 08:36 UTC (History)
2 users (show)

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


Attachments
dmesg (16.36 KB, text/plain)
2022-07-06 10:23 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2022-07-06 10:23:09 UTC
Created attachment 150437 [details]
dmesg

SUMMARY

I have plugged in an external 3,5" HDD drive via USB 3.0 cable and mounted and opened in Dolphin.

However, most of the time Dolphin's window becomes unresponsive, in the sense that its window becomes gray and the title says "not responding", when going through the folder structure of this particular drive.

This is definitely not optimal. Unfortunately there wasn't anything useful in journalctl, but at least I could capture dmesg's output, showing the issues with the HDD:

```
[ 7161.853007] sd 4:0:0:0: [sdd] tag#17 data cmplt err -71 uas-tag 2 inflight: CMD
[ 7161.853012] sd 4:0:0:0: [sdd] tag#17 CDB: Write(16) 8a 00 00 00 00 00 00 00 08 a0 00 00 00 10 00 00
[ 7193.863216] sd 4:0:0:0: [sdd] tag#21 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT
[ 7193.863222] sd 4:0:0:0: [sdd] tag#21 CDB: Write(16) 8a 00 00 00 00 00 91 ee 77 30 00 00 00 08 00 00
[ 7193.867621] sd 4:0:0:0: [sdd] tag#20 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT
[ 7193.867624] sd 4:0:0:0: [sdd] tag#20 CDB: Write(16) 8a 00 00 00 00 00 91 88 06 00 00 00 00 08 00 00
[ 7193.875747] sd 4:0:0:0: [sdd] tag#19 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
[ 7193.875751] sd 4:0:0:0: [sdd] tag#19 CDB: Write(16) 8a 00 00 00 00 00 00 02 9e c0 00 00 00 10 00 00
[ 7193.883867] sd 4:0:0:0: [sdd] tag#18 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[ 7193.883870] sd 4:0:0:0: [sdd] tag#18 CDB: Write(16) 8a 00 00 00 00 00 00 00 25 a8 00 00 00 08 00 00
[ 7193.891994] sd 4:0:0:0: [sdd] tag#17 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD
[ 7193.891998] sd 4:0:0:0: [sdd] tag#17 CDB: Write(16) 8a 00 00 00 00 00 00 00 08 a0 00 00 00 10 00 00
[ 7196.167487] sd 4:0:0:0: [sdd] tag#16 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[ 7196.167491] sd 4:0:0:0: [sdd] tag#16 CDB: Read(16) 88 00 00 00 00 00 00 02 08 38 00 00 00 08 00 00
```

The complete log can be found in the attachment.

 I would expect Dolphin to be still fully usable and to display an inline message, that there are issues accessing the current folder.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220704
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.18.6-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 postix 2022-07-06 10:35:20 UTC
Not-using the extension USB-3.0 cable has resolved the issue, but anyway, Dolphin should never fully freeze.
Comment 2 847240 2024-07-04 08:36:43 UTC
I know its probably not easy to fix this, but I really wish it would be. I work alot with sshfs-mounts and sometimes I forget to unmount those drives before sending my laptop to sleep. After waking the laptop again dolphin freezes and it takes ages before the process can even be killed.