nautilus crashed with SIGSEGV in g_atomic_int_exchange_and_add()

Bug #713419 reported by kyleabaker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

Nautilus crashes on its own periodically and doesn't seem to be triggered by any user input.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu natty (development branch)
Release: 11.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
nautilus:
  Installed: 1:2.32.2.1-0ubuntu5
  Candidate: 1:2.32.2.1-0ubuntu5
  Version table:
 *** 1:2.32.2.1-0ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 4 17:59:45 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd1b65a80b2 <g_atomic_int_exchange_and_add+2>: lock xadd %eax,(%rdi)
 PC (0x7fd1b65a80b2) ok
 source "%eax" ok
 destination "(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_atomic_int_exchange_and_add () from /lib/libglib-2.0.so.0
 g_variant_unref () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_atomic_int_exchange_and_add()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_nautilus: nautilus 1:2.32.2.1-0ubuntu5brasero 2.32.1-0ubuntu1nautilus-sendto 2.32.0-0ubuntu1totem 2.32.0-0ubuntu8nautilus-dropbox 0.6.7nautilus-dropbox 0.6.7ubuntuone-client-gnome 1.5.3-0ubuntu3nautilus-share 0.7.2-14ubuntu1evince 2.32.0-0ubuntu9ubuntuone-client-gnome 1.5.3-0ubuntu3gnome-disk-utility 2.32.1-0ubuntu3file-roller 2.32.1-0ubuntu2nautilus-dropbox 0.6.7ubuntuone-client-gnome 1.5.3-0ubuntu3

Revision history for this message
kyleabaker (kyleabaker) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #713281, 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
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.