thunar crashed with SIGSEGV in g_mutex_lock()

Bug #1832992 reported by David Kastrup
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Thunar File Manager
Confirmed
Medium
thunar (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

This is getting increasingly frequent and annoying. This time just trying to open a memory card was enough to trigger it.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: thunar 1.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-16.17-lowlatency 5.0.8
Uname: Linux 5.0.0-16-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sun Jun 16 15:34:50 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2802 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/Thunar --daemon
SegvAnalysis:
 Segfault happened at: 0x7f02eb85baf5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f02eb85baf5) ok
 source "%eax" ok
 destination "(%rdi)" (0x00000030) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: thunar crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: Upgraded to eoan on 2019-05-12 (35 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare
separator:

Revision history for this message
In , LAZA (laza74) wrote :

Created attachment 8349
journalctl crash report

Thunar is crashing permanently and reproducible on one drive:

https://forum.manjaro.org/t/thunar-crashes-how-to-sort-out-what-the-problem-is/79866

Revision history for this message
In , Alexxcons-x (alexxcons-x) wrote :

Same as for Bug #15212. Please provide a backtrace with debug symbols, and/or some more details on the use case .. what exactly you were doing in Thunar while it crashed ? Which view is used ? Which side-pane ?

Revision history for this message
In , LAZA (laza74) wrote :

I was searching for a file which contains a number at the beginning.

- detailled view
- tree
- tool style (?)

Revision history for this message
David Kastrup (dak) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_mutex_lock (mutex=mutex@entry=0x30) at ../../../glib/gthread-posix.c:1354
 thunar_thumbnailer_queue_async_reply (proxy=0x55c0633cd9e0, res=0x55c062d8e8c0, user_data=user_data@entry=0x7f02a80c15a0) at thunar-thumbnailer.c:344
 g_task_return_now (task=0x55c062d8e8c0) at ../../../gio/gtask.c:1209
 g_task_return (task=0x55c062d8e8c0, type=<optimized out>) at ../../../gio/gtask.c:1278
 g_task_return (type=G_TASK_RETURN_SUCCESS, task=<optimized out>) at ../../../gio/gtask.c:1678

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in thunar (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
In , Theo Linkspfeifer (lastonestanding) wrote :
Revision history for this message
In , Theo Linkspfeifer (lastonestanding) wrote :

Created attachment 9788
test diff

With this change I get the crash when browsing a folder with image files.

Revision history for this message
In , Andreldm-2 (andreldm-2) wrote :

(In reply to Theo Linkspfeifer from comment #4)
> Created attachment 9788 [details]
> test diff
>
> With this change I get the crash when browsing a folder with image files.

It seems like thumbnailer gets free'd before thunar_thumbnailer_queue_async_reply is run.
However I don't think that's a valid reproducer and we can't just return if thumbnailer is NULL.
It would be much better if you (or OP) could find a reliable way to reproduce the crash.

Revision history for this message
In , Theo Linkspfeifer (lastonestanding) wrote :

I found a similar occurrence of this bug:

#0 0x00007f876295cce9 in g_mutex_lock (mutex=mutex@entry=0x40) at ../glib/gthread-posix.c:1354
        _g_boolean_var_ = <optimized out>
#1 0x00007f8761210ba5 in xfconf_cache_set_property_reply_handler (proxy=0x5639b6ad6bb0 [GDBusProxy], res=0x5639b6aa68f0, user_data=user_data@entry=0x7f8754017c10) at xfconf-cache.c:608
        cache = 0x0
        old_item = 0x7f8754017c10
        item = <optimized out>
        error = 0x0
        result = <optimized out>

Source: https://bugzilla.redhat.com/show_bug.cgi?id=1722851

Revision history for this message
In , Theo Linkspfeifer (lastonestanding) wrote :

Other variant of the Thunar crash:

#0 0x00007fe6d3f996ba in g_type_check_instance_cast (type_instance=0x1, iface_type=94349881536000) at ../gobject/gtype.c:4050
No locals.
#1 0x000055cf8acd997a in thunar_thumbnailer_queue_async_reply (proxy=0x55cf8b066950, res=0x55cf8b44e990, user_data=user_data@entry=0x55cf8b057e60) at thunar-thumbnailer.c:340
        job = 0x55cf8b057e60
        thumbnailer = <optimized out>
        error = 0x0
        handle = 32742

Source: https://bugzilla.redhat.com/show_bug.cgi?id=1748063

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
Changed in thunar:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Sean Davis (bluesabre) wrote :

Reportedly fixed in thunar 1.8.15 and thunar 4.15.0.

Changed in thunar (Ubuntu):
status: Confirmed → Fix Released
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.