thunar crashed with SIGSEGV

Bug #1821589 reported by David Kastrup
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Double-clicked on an SDcard icon (only mounted on-demand on my desktop). Works most of the time: this is a sporadic occurence.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: thunar 1.8.4-1
ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
Uname: Linux 5.0.0-7-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 25 14:10:07 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2718 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f --daemon
SegvAnalysis:
 Segfault happened at: 0x56109cd91166: mov (%rdx),%rax
 PC (0x56109cd91166) ok
 source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_tree_row_reference_free () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare
separator:

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

StacktraceTop:
 thunar_tree_model_unref_node (tree_model=0x7fa4781a2b20, iter=0x7fffe69d5900) at thunar-tree-model.c:821
 gtk_tree_row_reference_unref_path_helper (path=path@entry=0x56109f240830, model=model@entry=0x7fa4781a2b20, parent_iter=parent_iter@entry=0x7fffe69d5960, depth=depth@entry=3, current_depth=current_depth@entry=2) at ../../../../gtk/gtktreemodel.c:2263
 gtk_tree_row_reference_unref_path_helper (path=path@entry=0x56109f240830, model=model@entry=0x7fa4781a2b20, parent_iter=parent_iter@entry=0x7fffe69d59c0, depth=depth@entry=3, current_depth=current_depth@entry=1) at ../../../../gtk/gtktreemodel.c:2262
 gtk_tree_row_reference_unref_path (path=0x56109f240830, model=0x7fa4781a2b20, depth=3) at ../../../../gtk/gtktreemodel.c:2277
 gtk_tree_row_reference_unref_path (depth=<optimized out>, model=<optimized out>, path=<optimized out>) at ../../../../gtk/gtktreemodel.c:2273

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
Launchpad Janitor (janitor) wrote :

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

Changed in thunar (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Klauer (daniel.c.klauer) wrote :

Same here when using Thunar to mount other partitions, seeing this right before crash:

(thunar:8364): Gtk-CRITICAL **: 00:09:37.161: ../../../../gtk/gtktreeview.c:6679 (validate_visible_area): assertion `has_child' failed.
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.

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

Thunar 1.8.14 is available in the 20.04 repository.

https://git.xfce.org/xfce/thunar/tree/NEWS?h=xfce-4.14

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.

Other bug subscribers

Remote bug watches

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