nautilus crashed with SIGSEGV in g_type_instance_get_private()

Bug #425296 reported by Sayantan Das on 2009-09-06
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Fix Released
brasero (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

this error is shown everytime i log in to the system, not after restart. only when i start the computer after a shut down

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Sep 6 17:14:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.91-0ubuntu3
ProcCmdline: nautilus
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
 Segfault happened at: 0x30b1c2 <g_type_instance_get_private+34>: mov (%eax),%edx
 PC (0x0030b1c2) ok
 source "(%eax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
 g_type_instance_get_private ()
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 __nptl_deallocate_tsd ()
 start_thread () from /lib/tls/i686/cmov/
Title: nautilus crashed with SIGSEGV in g_type_instance_get_private()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Sayantan Das (sayantan13) wrote :

StacktraceTop:IA__g_type_instance_get_private (instance=0x1,
brasero_medium_probed (data=0x1) at brasero-medium.c:2932
g_thread_cleanup (data=0x9c591a8)
__nptl_deallocate_tsd ()
start_thread () from /lib/tls/i686/cmov/

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
affects: nautilus (Ubuntu) → brasero (Ubuntu)
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here:

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
Changed in brasero:
status: Unknown → New
Pedro Villavicencio (pedro) wrote :

This has been fixed upstream, thanks for reporting.

Changed in brasero (Ubuntu):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package brasero - 2.28.1-0ubuntu1

brasero (2.28.1-0ubuntu1) karmic; urgency=low

  * New upstream version:
    - fix problems with drive/medium management
      (file descriptor leak preventing ejection, improved threading safety)
      (lp: #438065)
    - fix problems with libburn/libisofs
      (rare case data corruption, workaround TAO+dummy problem)
    - some crashes fixed (596625 among others) (lp: #425296, #437708)
    - memory leaks
    Updated translations:

 -- Sebastien Bacher <email address hidden> Mon, 05 Oct 2009 23:59:43 +0200

Changed in brasero (Ubuntu):
status: Fix Committed → Fix Released
Changed in brasero:
importance: Unknown → Critical
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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