nautilus crashed with SIGSEGV in g_type_check_instance()

Bug #1542667 reported by heiko
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

Nautilus crashed while performing actions/deleting a folder on a webdav cloud location.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.18.5-0ubuntu1~wily1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Feb 6 17:16:44 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
InstallationDate: Installed on 2015-12-29 (39 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1ec1ffee5c <g_type_check_instance+60>: testb $0x4,0x16(%rdx)
 PC (0x7f1ec1ffee5c) ok
 source "$0x4" ok
 destination "0x16(%rdx)" (0x6369736e6574615a) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fax lpadmin plugdev sambashare sudo vboxusers www-data

Revision history for this message
heiko (heikosch) wrote :
Revision history for this message
heiko (heikosch) wrote :

Nautilus crashed while performing actions/deleting a folder on a webdav location.

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

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x24fa040) at /build/glib2.0-EZCcr2/glib2.0-2.46.2/./gobject/gtype.c:4140
 g_signal_emit_valist (instance=0x24fa040, signal_id=641, detail=0, var_args=var_args@entry=0x7ffdecf48680) at /build/glib2.0-EZCcr2/glib2.0-2.46.2/./gobject/gsignal.c:3168
 g_signal_emit (instance=<optimized out>, signal_id=signal_id@entry=641, detail=detail@entry=0) at /build/glib2.0-EZCcr2/glib2.0-2.46.2/./gobject/gsignal.c:3439
 g_context_specific_source_dispatch (source=0x270a650, callback=<optimized out>, user_data=<optimized out>) at /build/glib2.0-EZCcr2/glib2.0-2.46.2/./gio/gcontextspecificgroup.c:54
 g_main_context_dispatch (context=0x17cddc0) at /build/glib2.0-EZCcr2/glib2.0-2.46.2/./glib/gmain.c:3154

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : StacktraceSource.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: removed: need-amd64-retrace
Tim Lunn (darkxst)
information type: Private → Public
Changed in ubuntu-gnome:
milestone: none → xenial
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.