nautilus crashed with SIGSEGV in gdk_display_get_event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've been having alot of crashes with gnome-shell today in libclutter, so this may or may not be related
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 14:50:53 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
org.gnome.
org.gnome.
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/nautilus --no-desktop /home/username/
SegvAnalysis:
Segfault happened at: 0x7f1fac156210: mov 0x70(%rdi),%rdx
PC (0x7f1fac156210) ok
source "0x70(%rdi)" (0x00000070) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gdk_display_
Title: nautilus crashed with SIGSEGV in gdk_display_
UpgradeStatus: Upgraded to precise on 2012-01-05 (103 days ago)
UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin mythtv plugdev sambashare vboxusers video
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 #952546, 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.