nautilus crashed with SIGSEGV in g_object_get()

Bug #939239 reported by M.C. Botha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Had RhythmBox open with my folder with my music not yet mounted.
I then left RhythmBox open, mounted the folder.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Thu Feb 23 06:38:34 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '864x519+500+223'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x75bd5e <g_object_get+30>: mov (%esi),%eax
 PC (0x0075bd5e) ok
 source "(%esi)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_get () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_object_get()
UpgradeStatus: Upgraded to precise on 2012-01-31 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
M.C. Botha (mcbotha) wrote :
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 this software better. This particular crash has already been reported and is a duplicate of bug #929031, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-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.