gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()

Bug #833859 reported by Till Kamppeter
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
High
Unassigned

Bug Description

Crash message popped up right after login.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-fuse 1.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Wed Aug 24 23:42:35 2011
ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon
ProcCmdline: /usr/lib/gvfs//gvfs-fuse-daemon /var/lib/lightdm/.gvfs
ProcCwd: /
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f14b4414eb7: mov 0x18(%rax),%rax
 PC (0x7f14b4414eb7) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
UpgradeStatus: Upgraded to oneiric on 2009-12-18 (615 days ago)
UserGroups:

visibility: private → public
Changed in gvfs (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-11.10-beta-1
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #832533, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.