*** This bug is a duplicate of bug 376145 ***
https://bugs.launchpad.net/bugs/376145
I can confirm this too on Karmic.
Curiously HALd also refuses to start.
The error message telling gvfs-gdu-volume crashed comes very soon after
logging in, together with an error message about bzr-notify crashing, as
reported in bug #391158.
Running 'sudo hald --verbose=yes' gives no error messages, neither does
running 'sudo /etc/init.d/hal start', even though its status is not
running.
Running '/usr/lib/gvfs/gvfs-gdu-volume-monitor' doesn't give you the
next emtpy line in the console, but doesn't output anything at all.
Both hal and gvfs-gdu-volume-monitor don't show up at all when you try
to run them manually. The only remaining process with hal in it was
gvfs-hal-volume(something?).
--
gvfs-gdu-volume segfault in libgdu.so.0.0.0
https://bugs.launchpad.net/bugs/377426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
