FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon
process(es) stuck
Matt
datahead4 at gmail.com
Fri Aug 8 17:47:28 UTC 2008
On Wed, May 7, 2008 at 10:33 AM, Jeremy Chadwick <koitsu at freebsd.org> wrote:
>
> On Wed, May 07, 2008 at 10:22:09AM -0500, Matt wrote:
> > On Wed, May 7, 2008 at 9:53 AM, Matt <datahead4 at gmail.com> wrote:
> > > On Wed, May 7, 2008 at 9:48 AM, Robert Noland <rnoland at 2hip.net> wrote:
> > > > On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote:
> > > > > On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote:
> > > > > > Sorry - should have been more specific than the generic "stuck"
> > > > > > description. Top shows the process state as "fu_msg" and it is not
> > > > > > consuming any processor resources, just seemingly sits there idling.
> > > > > > Output from ps is:
> > > > > >
> > > > > > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND
> > > > > > 1000 4019 1 0 44 0 6324 2528 - Ts ?? 0:00.00
> > > > > > /usr/local/libexec//gvfs-fuse-daemon /home/mtosto
> > > > >
> > > > > The "T" flag under State says that the process is stopped. It's as if
> > > > > the process was running in the foreground, and was ^Z'd -- same
> > > > > behaviour.
>
As a (very) late follow-up to this issue, looks like the latest Gnome
ports have eliminated this issue. I haven't seen it for the last few
weeks after doing a full portupgrade on Gnome.
Thanks,
Matt
More information about the freebsd-ports
mailing list