nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I opened Nautilus to find and view a file I had just saved. When closing Nautilus, the first click on the close button didn't work so had to click again. Apport then started, reporting this crash. I don't seem to be able to reproduce it anymore.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 20 23:18:27 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f36345d1800 <gtk_ui_
PC (0x7f36345d1800) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gtk_ui_
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in gtk_ui_
UpgradeStatus: Upgraded to precise on 2012-02-11 (9 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
| Bruno Girin (brunogirin) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #925503, 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.