Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report:
libglib2.0-data version 2.35.9-2ubuntu1 required, but 2.36.0-1ubuntu1 is available outdated debug symbol package for libcap2: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4 outdated debug symbol package for libprocps0: package version 1:3.3.3-2ubuntu5 dbgsym version 1:3.3.3-2ubuntu3 outdated debug symbol package for libcap2-bin: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4 outdated debug symbol package for libpam-cap: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4 outdated debug symbol package for procps: package version 1:3.3.3-2ubuntu5 dbgsym version 1:3.3.3-2ubuntu3 libglib2.0-0 version 2.35.9-2ubuntu1 required, but 2.36.0-1ubuntu1 is available libxml2 version 2.9.0+dfsg1-4ubuntu3 required, but 2.9.0+dfsg1-4ubuntu4 is available Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1160574/+attachment/3599406/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160574 Title: gvfsd-http crashed with SIGSEGV Status in “gvfs” package in Ubuntu: Invalid Bug description: Plugged in a Galaxy Nexus in fastboot mode and got this crash. Latest Raring updates. Also maybe related, cannot flash latest image: $ phablet-flash -l error: device not found Error while executing adb shell getprop ro.cm.device Make sure the device is connected and viewable by running 'adb devices' Ensure you have a root device, one which running 'adb root' does not return an error -- But phone is connected, also tried booting in to existing Ubuntu Touch image on it but not found that way either. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gvfs-backends 1.16.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 26 21:39:30 2013 Disassembly: => 0x7f7532c6d07d: Cannot access memory at address 0x7f7532c6d07d ExecutablePath: /usr/lib/gvfs/gvfsd-http InstallationDate: Installed on 2013-02-12 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130212) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.8 /org/gtk/gvfs/exec_spaw/2 SegvAnalysis: Segfault happened at: 0x7f7532c6d07d: Cannot access memory at address 0x7f7532c6d07d PC (0x7f7532c6d07d) ok SP (0x7ffff1862f80) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-http crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp