thunar crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1553509 reported by Coya DeBrojara
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Duplicate bug 1540186
Error while moving a file from the window to the side panel (picture), using the "drag and drop".

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: thunar 1.6.10-2
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Mar 5 15:44:25 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2016-02-26 (8 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160216)
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=pl
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff0a439f7ed <g_type_check_instance_is_fundamentally_a+13>: mov (%rax),%rax
 PC (0x7ff0a439f7ed) ok
 source "(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
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
 ?? ()
 ?? ()
 ?? ()
Title: thunar crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Coya DeBrojara (coyadebrojara) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in thunar (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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