nautilus crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
none
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu3
ProcVersionSign
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Thu Feb 12 12:41:40 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
InstallationDate: Installed on 2014-10-24 (111 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=es_UY:es
PATH=(custom, no user)
LANG=es_UY.UTF-8
SHELL=/bin/bash
TERM=unknown
SegvAnalysis:
Segfault happened at: 0x7fdc892da919 <g_type_
PC (0x7fdc892da919) ok
source "(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
g_signal_
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to vivid on 2015-01-05 (38 days ago)
UserGroups:
usr_lib_nautilus:
brasero 3.12.0-0ubuntu2
evince 3.14.1-0ubuntu3
file-roller 3.14.2-0ubuntu4
gnome-terminal 3.14.2-0ubuntu1
nautilus-share 0.7.3-1ubuntu5
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 #447459, 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.