Bug 292956

Summary: Having NFS shares mounted makes opening KMenu spin up NAS
Product: [Unmaintained] plasma4 Reporter: Egbert van der Wal <ewal>
Component: widget-kickoffAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: adaptee, Juergen.Bausa
Priority: NOR    
Version First Reported In: 4.7.3   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Egbert van der Wal 2012-01-31 11:51:48 UTC 
Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

I have a Netgear ReadyNAS Duo in my network, of which I have some shares mounted using NFS. None of these shares are used for system files or home directories, and none of them are mentioned in the Places in Dolphin e.g

For energy conservation, the NAS shuts down the hard drivers after short periods of inactivity. 

The problem is that whenever I open the KMenu from the main panel, it tries to access these shares for some reason, meaning the NAS has to spin up the hard drives, introducing a delay of several seconds (up to 15). This is of course very annoying.

Why is KMenu accessing my NFS share? It shoudln't unless I specifically ask it to.

Reproducible: Always

Steps to Reproduce:
- Add NFS share to /etc/fstab to automount on boot
- Login to KDE
- Open KMenu

Actual Results:  
NAS spins up hard drives, takes about 15 seconds to access introducing a long delay

Expected Results:  
KMenu opens instantly and does not freeze while trying to access the NAS
Comment 1 Egbert van der Wal 2012-01-31 11:52:34 UTC 
By the way, this is running when vanilla Kubuntu 11.10.
Comment 2 Jekyll Wu 2012-07-11 11:31:49 UTC 
*** Bug 263521 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2018-06-08 19:42:26 UTC 
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham