*** This bug is a duplicate of bug 376145 ***
https://bugs.launchpad.net/bugs/376145
Uggh. Commented on the wrong bug. I actually wanted to comment on bug #376145.
My apologizes for the noise.
--
gvfs-gdu-volume segfault in libgdu.so.0.0.0
https://bugs.launchpad.net/bugs/377426
You received
*** 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 cra
*** This bug is a duplicate of bug 376145 ***
https://bugs.launchpad.net/bugs/376145
On Sun, May 17, 2009 at 11:59:00AM -, Martin Olsson wrote:
> However, right now on karmic with all updates up to may 17th I
> consistently see 3 gvfs-gdu-volume crashes in my dmesg after every
> single re
*** This bug is a duplicate of bug 376145 ***
https://bugs.launchpad.net/bugs/376145
Note: I'm the original reporter of bug 376145 so apport did certainly
trigger for me at least once. However, right now on karmic with all
updates up to may 17th I consistently see 3 gvfs-gdu-volume crashes in
*** This bug is a duplicate of bug 376145 ***
https://bugs.launchpad.net/bugs/376145
OK, it does look like a duplicate of bug #376145.
** This bug has been marked a duplicate of bug 376145
gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
--
gvfs-gdu-volume segf
*** This bug is a duplicate of bug 376145 ***
https://bugs.launchpad.net/bugs/376145
"If you are running the _Ubuntu Stable Release_ you might need to enable
apport in /etc/default/apport and restart."
Karmic is hardly the stable release, but you're right, having checked,
apport is not enable
Just updated my VM to the current state of karmic, this is still
happening. The nautilus windows no longer close themselves but the
segfault is still logged by the kernel.
This is still gvfs-backends 1.3git20090512-0ubuntu1. libgdu0 is
0.3.0-0ubuntu2.
Attached is a manually updated Dependencies.t
bug #376145 could be your issue but not easy to say without a debug
stacktrace, steps are not always enough especially if the issue depends
of the harware you are using
--
gvfs-gdu-volume segfault in libgdu.so.0.0.0
https://bugs.launchpad.net/bugs/377426
You received this bug notification because
> 1) If you read my original report you'll see that apport didn't catch
the crash.
Did you enable apport as explained before? It's not running by default
> 2) I haven't tested the bleeding edge - I thought the point of the alpha
> releases was to get a few more people testing than those that ha
1) If you read my original report you'll see that apport didn't catch
the crash. There is no crash file. I tried to attach with gdb but the
process doesn't run continuously. I have however provided steps to
reproduce which seem to work reliably (here at least.)
2) I haven't tested the bleeding edg
10 matches
Mail list logo
