*** 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
my dmesg after every single reboot and none of these get detected by
apport (could it be that they are supressed because I previously
submitted that gvfs-gdu-volume? afaik apport does not work that way? on
another karmic machine I have a kernel oops that happens during every
boot and for that one apport certainly asks me to report it every single
time). Besides the gvfs-gdu-volume bug itself, I also think there is
something wrong with apport in karmic:
[ 75.536602] gvfs-gdu-volume[3997]: segfault at c ip 00118fda sp bf9a5c20
error 4 in libgdu.so.0.0.0[110000+22000]
[ 77.946651] gvfs-gdu-volume[4015]: segfault at c ip 00d65fda sp bf847880
error 4 in libgdu.so.0.0.0[d5d000+22000]
[ 83.860279] gvfs-gdu-volume[4037]: segfault at c ip 00afdfda sp bff10380
error 4 in libgdu.so.0.0.0[af5000+22000]
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
