gvfsd-smb crashed with SIGSEGV in g_main_context_dispatch()

Bug #649201 reported by craigsn@hotmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: shotwell

I was importing foto links from a windows box, when this happened. Just prior to this, I had another crash with Shotwell, but it was listed as a different problem, although I was attempting to do the same thing, import foto links.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gvfs-backends 1.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Sep 27 15:56:39 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.11 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x410304: mov 0x18(%rdi),%rax
 PC (0x00410304) 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:
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: gvfsd-smb crashed with SIGSEGV in g_main_context_dispatch()
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare

Revision history for this message
craigsn@hotmail.com (craigsn-hotmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 command_read_cb (source_object=0x16dd370,
 async_ready_callback_wrapper (
 read_async_cb (data=<value optimized out>,
 g_main_context_dispatch (context=0x165bcd0)
 g_main_context_iterate (context=0x165bcd0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in shotwell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Omer Akram (om26er)
visibility: private → public
Revision history for this message
Jim Nelson (yorba-jim) wrote :

This sounds similar to https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/649200 but the crash point is different in each. When you say you were attempting to import photos, what were you doing (or what was Shotwell doing) when the crash occurred? Did you choose File -> Import From Folder..., or drag-and-dropping the folder on Shotwell from Nautilus, or was the import already underway?

Revision history for this message
Omer Akram (om26er) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks

Changed in shotwell (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

affects: shotwell (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
status: Incomplete → Invalid
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.