nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Booted up, had several Nautilus windows open, this crash occurred.
Description: Ubuntu quantal (development branch)
Release: 12.10
Codename: quantal
Linux Aspire1 3.4.0-5-generic #11-Ubuntu SMP Tue Jun 5 17:35:46 UTC 2012 i686 i686 i686 GNU/Linux
Last update on 10 June. I'll do another today.
Acer Aspire 1 netvbook
Intel(R) Atom(TM) CPU N455 @ 1.66GHz
Intel Corporation N10 Family Integrated Graphics Controller
Jerry
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.1-0ubuntu5
ProcVersionSign
Uname: Linux 3.4.0-5-generic i686
ApportVersion: 2.1.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Tue Jun 12 07:16:18 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120606.2)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x80c716e: mov 0xc(%eax),%eax
PC (0x080c716e) ok
source "0xc(%eax)" (0xaaaaaab6) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
g_cclosure_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: nautilus crashed with SIGSEGV in g_cclosure_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1009951, 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.