Bug 460094 - Dolphin Freeze while opening nfs mount with several restricted folders
Summary: Dolphin Freeze while opening nfs mount with several restricted folders
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: panels: folders (show other bugs)
Version: 22.04.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
: 460093 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-10-07 14:18 UTC by rasmus.oltrogge
Modified: 2022-10-07 14:18 UTC (History)
1 user (show)

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


Attachments
Notification pop-ups (77.86 KB, image/jpeg)
2022-10-07 14:18 UTC, rasmus.oltrogge
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rasmus.oltrogge 2022-10-07 14:18:10 UTC
Created attachment 152629 [details]
Notification pop-ups

SUMMARY
Dolphin and Taskbar freezes completely for several seconds (even minutes sometimes)

STEPS TO REPRODUCE
1. mount nfs point with several folders without having even read rights on them (except for the one you have access to) (it is a nfs4 mountpoint. maybe it is related to that)
2. try opening mountpoint via Dolphin
3. await several notifications, that it was not able to open the folders
4. then everything works again

OBSERVED RESULT
- fan speed increases (due to higher CPU load?)
- Dolphin freezes for a few seconds
- Taskbar, Application Starter, Widgets etc. freeze until...
- ...several notifications pop up, that the filesystem does not respond.
- then it works again

EXPECTED RESULT
- no freeze while opening mountpoint with several access restricted folders
- immediate opening of the mountpoint
(- maybe even hiding the folders, the user does not have access to?)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Fedora 36
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
maybe similar to 412724
Comment 1 rasmus.oltrogge 2022-10-07 14:18:19 UTC
*** Bug 460093 has been marked as a duplicate of this bug. ***