nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1512562 reported by Farran
404
This bug affects 76 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Confirmed
High
Unassigned

Bug Description

Closed the Downloads folder window, that was the only nautilus window open (my Desktop does not have nautilus painting it). Nothing appeared amiss, then a few minutes later the crash report dialogue appeared. No idea as to the nature of the crash.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.18.1-0ubuntu1~wily1 [origin: LP-PPA-gnome3-team-gnome3-staging]
Uname: Linux 4.2.0-040200rc1-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 3 03:33:19 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff87417c88d <g_type_check_instance_is_fundamentally_a+13>: mov (%rax),%rax
 PC (0x7ff87417c88d) ok
 source "(%rax)" (0x2b12e7930a) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to wily on 2015-10-25 (8 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Farran (farran) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceSource:

StacktraceTop:

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Tim Lunn (darkxst)
information type: Private → Public
Tim Lunn (darkxst)
tags: added: xenial
removed: wily
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
milestone: none → xenial
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Edson T. Marques (edsontmarques) wrote :

Got it here... xenial.

nayer (nayerbensalah)
Changed in ubuntu-gnome:
status: Confirmed → Fix Committed
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
status: Fix Committed → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.