Ubuntu
gvfs package

gvfsd-computer crashed with SIGSEGV in strchr()

Bug #387036 reported by Linus Hoppe
74
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Critical
gvfs (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

When i klicked on the Button "Computer" in my menue-panel, this error was shown. it is reproducable. error message see screenshot!

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Jun 14 20:00:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfsd-computer
Package: gvfs 1.3git20090512-0ubuntu2
ProcCmdline: /usr/lib/gvfs/gvfsd-computer --spawner :1.10 /org/gtk/gvfs/exec_spaw/4
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.30-9.10-generic
SegvAnalysis:
 Segfault happened at: 0x3130c3 <strchr+99>: mov (%eax),%ecx
 PC (0x003130c3) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 strchr () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gvfsd-computer crashed with SIGSEGV in strchr()
Uname: Linux 2.6.30-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

See original description

Related branches

lp:ubuntu/lucid/gvfs
Revision history for this message
Linus Hoppe (linus-hoppe-deactivatedaccount) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strchr () at ../sysdeps/i386/strchr.S:127
recompute_files (backend=<value optimized out>)
try_mount (backend=0x9b1bc10, job=0x9b1dc18,
try (job=0x9b1dc18) at gvfsjobmount.c:131
g_vfs_job_try (job=0x9b1dc18) at gvfsjob.c:216

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Linus Hoppe (linus-hoppe-deactivatedaccount)
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report Linus, the backtrace matches http://bugzilla.gnome.org/show_bug.cgi?id=582772 ; linking the report.

Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
status: Unknown → New
Revision history for this message
Linus Hoppe (linus-hoppe-deactivatedaccount) wrote :

I'll attach a valgrind log of "gvfsd-computer"!

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is fixed upstream now

Changed in gvfs (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Linus Hoppe (linus-hoppe-deactivatedaccount) wrote :

When will you release the fix?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the new gvfs versions don't build with the current devicekit-disks so not before that issue is fixed upstream or before getting new versions for it available and in karmic

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.3.1-0ubuntu2

---------------
gvfs (1.3.1-0ubuntu2) karmic; urgency=low

  * debian/patches/90_git_change_fix_computer_crash.patch:
    - git change to fix the gvfsd-computer crashing when devices have no names
      (lp: #387036)
  * debian/control.in:
    - gvfs depends on policykit-1-gnome which is required for mounting now

 -- Sebastien Bacher <email address hidden> Mon, 29 Jun 2009 14:38:51 +0200

Changed in gvfs (Ubuntu):
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
status: New → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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