Summary: | plasmashell freezes for some time after accessing an NFSv4 share with crossmounts | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Till Schäfer <till2.schaefer> |
Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kde, nate |
Priority: | NOR | ||
Version: | 5.26.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Till Schäfer
2023-01-29 21:31:12 UTC
Can you talk a bit about why you have this share manually mounted with fstab? Doing so is known to cause issues like this, and the recommend method of access is to simply navigate to the share in Dolphin or the file dialogs via its network URL or the network browser. If you want to be able to access the share quickly, you can make a bookmark or shortcut to that location. No need to manually mount using fstab. Is there a reason why this doesn't work? There are several reasons: * I do not use dolphin for file browsing, instead I often just work on the terminal in the first place or use Krusader * I have several resources that should be accessible by cron jobs, shell scripts that are not related to GUI / Plasma. * I want to access that share also from terminal via SSH, when I log in from remote without actually starting plasma * I have non-KDE GUI software, which needs access to the shares, e.g., some Eclipse workspaces are located there. * I want to have a unified path where certain resources are accessible across multiple machines I would like to add a point that makes this behaviour even more problematic to me: * after some idle time, the effect re-occurs even if the crossmnt file systems are already mounted. Thus accessing the share again causes plasma to freeze again. In my opinion the fstab is a pretty standard way of mounting file systems. Accessing a share (even when only done in terminal) should never freeze the complete plasma workspace. Thanks for the info. The problematic behaviour was fixed after I have deleted bloated user-places.xbel (which was spammed by kde connect see Bug 466416). Thus I report this as a duplicate of the more specific Bug 451876. *** This bug has been marked as a duplicate of bug 451876 *** |