closing the nautilus bug since the submitter didn't give the required
detail, you can reopen if you still get the issue though
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
nautilus and evince should not accesses smb mounts at startup
https://bugs.launchpad.net/bugs/24
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
** Also affects: evince (Fedora)
Importance: Undecided
Status: New
--
nautilus and evince should not accesses smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
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.
** Changed in: evince (Ubuntu)
could you try to strace evince and see what file it's trying to acces on
the drive?
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Incomplete
--
nautilus and evince should not accesses smb mou
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 ce
thank you for your bug report. what ubuntu version do you use. how do
you know nautilus is accessing those?
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
Status: New => Incomplete
--
nautilus and evince should not accesses smb mounts at startup
https://bugs.launchpad.ne
