gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gvfs
There appears to be the same bug reported, but it is for the i386 architecture, and people seem to think it has been resolved.
I have all the latest updates as of this morning, rebooted the machine and this bug showed up before I had done anything.
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 10 08:40:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
NonfreeKernelMo
Package: gvfs 1.4.0-0ubuntu1
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7f4829985c91 <gdu_pool_
PC (0x7f4829985c91) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
gdu_pool_
?? ()
?? ()
g_object_newv () from /usr/lib/
g_object_
Title: gvfs-gdu-
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #436871, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.