nautilus and evince should not access smb mounts at startup

[Rolf Leggewie]

Binary package hint: nautilus

I have a samba share automounted with autofs at /mnt/smb/mynas (which as the name suggests is a NAS box). Nautilus as well as evince seem to be accessing that share whenever the program is started. This results in an unnecessary spin-up of the hard-drive in the NAS which I would like to avoid.

[Sebastien Bacher (seb128)]

thank you for your bug report. what ubuntu version do you use. how do you know nautilus is accessing those?

[Rolf Leggewie (r0lf)]

I use an uptodate hardy installation. I can reliably spin up the NAS drive by calling either evince or nautilus. Whether it is those programs themselves or a lib or something else that they use, I cannot say. The start of those programs awakes the drive from sleep, that is what I can say with certainty.

[Sebastien Bacher (seb128)]

could you try to strace evince and see what file it's trying to acces on the drive?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[Philip Rose (philrosedba)]

I ran into the same thing on Fedora. Turns out that evince is doing a file stat on everything associated with evince in ~/.recently-used.xbel. I deleted the xbel file, and it's no longer mounting the samba share. It's a temporary fix until documents on the share are added back into the xbel file.

[Sebastien Bacher (seb128)]

closing the nautilus bug since the submitter didn't give the required detail, you can reopen if you still get the issue though

[Rolf Leggewie (r0lf)]

I had thought that Philip had given all the needed info (and more)

reopening, since of course, this is still present in Jaunty

[Philip Rose (philrosedba)]

I found it especially frustrating on the laptop when autofs tries to mount shares that are inaccessible. It sometimes causes autofs to hang, and long delays starting evince. A good workaround I'm using is to make the .recently-used.xbel file immutable after clearing Recent Documents in GNOME.

As root:
# chattr +i /home/<user>/.recently-used.xbel

[Sebastien Bacher (seb128)]

one task is enough that seems rather a gtk issue then

[Sebastien Bacher (seb128)]

the bug should be sent to bugzilla.gnome.org by somebody who consider the behaviour buggy which I don't, the software need to stat recent files to list only those which are available and can be used

[Mörgæs (moergaes)]

Closing as this concerns an obsolete Ubuntu release.
If a similar bug appears in 13.10 please open a new report.