thunar crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1540186 reported by Jack Fromm on 2016-02-01
166
This bug affects 33 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
High
Unassigned

Bug Description

Dragging and dropping multiple files from one tab to another (different folder but on same partition) in the same Thunar window.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: thunar 1.6.10-2
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jan 31 20:07:17 2016
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2015-12-23 (39 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151222)
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7faddbf5e81d <g_type_check_instance_is_fundamentally_a+13>: mov (%rax),%rax
 PC (0x7faddbf5e81d) ok
 source "(%rax)" (0x00000002) 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

Jack Fromm (jjfrv8) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:
http://packages.qa.ubuntu.com/qatracker/reports/bugs/1540186

tags: added: package-qa-testing

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in thunar (Ubuntu):
status: New → Confirmed
Changed in thunar (Ubuntu):
importance: Undecided → High
Ruben Verweij (ruben-verweij) wrote :

Thunar also crashed for me when trying to rename a file. Crash happened after the file was successfully renamed.

Managed to get this crash while decompressing files
extracted .tar.bz2
what why did it put a (2) at the end
try it again
crash
open it back up
looks like it never refreshed and showed the 1st file of the same name

Martin Dauskardt (md001) wrote :
Download full text (6.3 KiB)

After upgrading from Xubuntu 18.04 to 18.10 I have the same segfault immidiately when starting thunar or when selecting the first file/folder.

martin@martin-desktop:/tmp$ gdb thunar core
GNU gdb (Ubuntu 8.2-0ubuntu1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from thunar...(no debugging symbols found)...done.
[New LWP 7382]
[New LWP 7383]
[New LWP 7385]
[New LWP 7384]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `thunar'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fe46a618acd in g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
[Current thread is 1 (Thread 0x7fe466593a80 (LWP 7382))]
(gdb) bt
#0 0x00007fe46a618acd in g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1 0x00007fe46a5fe826 in g_object_get_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2 0x00007fe46b1fd01d in gtk_tree_row_reference_free () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3 0x00007fe46a4f6aab in g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007fe46a5f9c82 in g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007fe46a5f42a4 in g_closure_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007fe46a60e874 in g_signal_handlers_destroy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007fe46a5f925d in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8 0x00007fe46a5f9c13 in g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007fe46a50254f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007fe46a5036a8 in g_hash_table_remove_all () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007fe46a5036ee in g_hash_table_destroy () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007fe46af6a45d in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#13 0x00007fe46a5f9c82 in g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x000055790383764a in ()
#15 0x00007fe46a5f4b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x00007fe46a6078f3 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007fe46a610882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007fe46a610ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007fe46a5f91d4 in () at /usr/lib/x86_64-linux-...

Read more...

Frits Letteboer (f-letteboer) wrote :

I had the same issues as here. It appears to be related to the treeview

Link to the original bug report:

https://bugzilla.xfce.org/show_bug.cgi?id=14714

The attachment "Crash in tree-view when multiple windows are open (Bug #14714)" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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