I'm having problems getting the replaced gvfsd to start. I've created a wrapper script, similar to the one described in the pages of the other bug. When I try to start it, it works, but doesn't come back in the System Monitor (process is not listed there, even though it exists; I can find it with ps and top). After a reboot, the gvfsd doesn't start automatically, and therefore the x-windows / gnome environment doesn't start as wanted (no Desktop) there is a warning, but I forgot what it is. Currently, I have put everything back (x-windows / gnome is working fine), to make sure I am trying to monitor the right program. I think this has to do with the fact that it's gvfsd, not gvfsd-<something>, but I'm not sure yet on how to resolve it. As I mentioned earlier, if I shoot gvfsd, init (or something) restarts it automatically. However, with the wrapper script, this doesn't happen (init isn't happy with the new environment, and thinks gvfsd isn't started, or it actually doesn't start).
Anyway, for now, the result is the same; I either don't get a working gvfsd or I don't get a working x-windows / gnome environment. Some suggestions would be appreciated. > the bug you listed there is specific to the webdav backend and has been > fixed in jaunty, gvfsd is usually stable, some backends are still buggy > and need work though > -- gvfsd allocates huge amounts of memory while playing audio files https://bugs.launchpad.net/bugs/316093 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
