nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Nautilus crashed just after login. Nothing else was happening at the time.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Tue Sep 25 07:18:28 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ffa7d65ae8c <g_type_
PC (0x7ffa7d65ae8c) 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: Upgraded to quantal on 2012-09-07 (18 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev postgres sambashare sudo wireshark
This crash has the same stack trace characteristics as bug #1053670. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.