nautilus crashed with SIGSEGV in g_atomic_int_exchange_and_add()
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://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu5
ProcVersionSign
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=
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd1b65a80b2 <g_atomic_
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_
g_variant_unref () from /lib/libglib-
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_atomic_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_nautilus: nautilus 1:2.32.
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.