nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Had just install the distribution updates for 9/20/12 and rebooted into the 12.10 unity desktop. Desktop sessions have been slow to respond lately so I did not think much of the slow execution of my web browser after selecting it. I had clicked on the dash panel applet first and then clicked on my browser's icon. My browser eventually opened and when loading my home page the apport crash notification appeared. I have not rebooted to see if this is reproducible , yet. I will try that after I finish what I started to do. And append this if the crash happens again.
Best Wishes
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Thu Sep 20 15:14:07 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f4afe3ebe8c <g_type_
PC (0x7f4afe3ebe8c) ok
source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors: (nautilus:2091): GLib-GObject-
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 #1053670, 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.