nautilus crashed with SIGSEGV in g_main_context_dispatch()

Bug #943797 reported by Federico Vera
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
overlay-scrollbar (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happened when I ejected a mounted usb drive (pressing on the eject icon right beside the name) and nautilus was showing the content of the drive.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: overlay-scrollbar 0.2.15-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 1 01:54:18 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
PackageArchitecture: all
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f4b065af9f8: mov 0xb0(%rbx),%ecx
 PC (0x7f4b065af9f8) ok
 source "0xb0(%rbx)" (0xaaaaaaaaaaaaab5a) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: overlay-scrollbar
StacktraceTop:
 ?? () from /usr/lib/liboverlay-scrollbar3-0.2.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Federico Vera (fedevera) 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 #907111, 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-amd64-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.