always reports "can't stat() fuse.gvfs-fuse-daemon"

Bug #662168 reported by Andrew Schulman on 2010-10-17
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
lsof (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: lsof

Whenever I run lsof, I get a bunch of these error messages:

# lsof /dev/sdd1
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/andrex/.gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/carey/.gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/elijah/.gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/mathieu/.gvfs
      Output information may be incomplete.

Just nuisance, really.
Thanks,
Andrew.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: lsof 4.81.dfsg.1-1build1
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Oct 17 09:53:18 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lsof

Andrew Schulman (andrex) wrote :
Sam Brightman (sambrightman) wrote :

If I run lsof now, it doesn't produce this message. When it runs tonight from my user's crontab, it will produce this message (every time). I can stat the file, too.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lsof (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers