Ubuntu
thunar package

thunar crashed with SIGSEGV

Bug #1829921 reported by David Kastrup on 2019-05-21

16

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Thunar File Manager	Fix Released	Medium	xfce-bugs #15452
	thunar (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Not sure what other bug this may be equal to. Crashed while exploring folders, possibly in connection with SDcard in a USB reader (Expresscard size factor, Sony VGP-MCA20).

Bus 002 Device 006: ID 054c:0281 Sony Corp.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x054c Sony Corp.
  idProduct 0x0281
  bcdDevice 4.52
  iManufacturer 1 Sony
  iProduct 2 UMH-U09
  iSerial 3 F0000020B320
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 0x0027
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk-Only
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 1
:

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: thunar 1.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
Uname: Linux 5.0.0-13-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May 21 21:36:03 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2776 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: 0x5610d9563220: mov 0x28(%rdi),%rax
PC (0x5610d9563220) ok
source "0x28(%rdi)" (0x00000028) 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/libgobject-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to eoan on 2019-05-12 (9 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare
separator:

Tags:

Revision history for this message

David Kastrup (dak) wrote on 2019-05-21:

#1

Dependencies.txt Edit (9.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (688 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (13.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1010 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (293 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (91.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (15.8 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2019-05-21:

#2

StacktraceTop:
thunar_file_get_file (file=0x0) at thunar-file.c:1460
thunar_tree_view_context_menu (view=view@entry=0x5610d9fde3c0, model=<optimized out>, iter=iter@entry=0x7ffc87326420) at thunar-tree-view.c:1363
thunar_tree_view_button_press_event (widget=<optimized out>, event=<optimized out>) at thunar-tree-view.c:744
_gtk_marshal_BOOLEAN__BOXEDv (closure=0x5610d9de8c60, return_value=0x7ffc87326640, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x5610d9de1ff0) at ../../../../gtk/gtkmarshalers.c:129
_g_closure_invoke_va (closure=0x5610d9de8c60, return_value=0x7ffc87326640, instance=0x5610d9fde3c0, args=0x7ffc87326710, n_params=1, param_types=0x5610d9de1ff0) at ../../../gobject/gclosure.c:873

Revision history for this message

Apport retracing service (apport) wrote on 2019-05-21: Stacktrace.txt

#3

Stacktrace.txt Edit (9.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2019-05-21: StacktraceSource.txt

#4

StacktraceSource.txt Edit (5.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2019-05-21: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (13.3 KiB, text/plain)

Changed in thunar (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

In Xfce Bugzilla #15452, Pipicalzaslargass (pipicalzaslargass) wrote on 2019-05-22:

#6

Created attachment 8571
journalctl dumped core

Right click on any unmounted volume in left tree panel make thunar to crash.

Arch linux 64 bits updated.
xfce4 and thunar updated.

Revision history for this message

In Xfce Bugzilla #15452, Alexxcons-x (alexxcons-x) wrote on 2019-05-23:

#7

Thanks for reporting !

I cannot reproduce this bug. Does it always happen for you, or just rarely ?

Does the crash happen for all kind of volumes ? How did you mount / unmount it ?

Could you please try to generate a backtrace with debug symbols ? ( Without symbols it is almost useless )
Here some distro-specific how to: https://docs.xfce.org/contribute/bugs/start

Revision history for this message

In Xfce Bugzilla #15452, Pipicalzaslargass (pipicalzaslargass) wrote on 2019-05-23:

#8

Created attachment 8576
Backtrace Trace.log

Revision history for this message

In Xfce Bugzilla #15452, Pipicalzaslargass (pipicalzaslargass) wrote on 2019-05-23:

#9

Created attachment 8577
Backtrace

Yes, the crash happens with all UNMOUNTED partitions, volumes (connected hard disk, ssd), MTP device(android) and usb pendrives, when I click with right mouse button on them. Only unmounted ones that shows the tree view

Revision history for this message

In Xfce Bugzilla #15452, Gitbot (gitbot) wrote on 2019-05-24:

#10

Andre Miranda referenced this bugreport in commit 479655f5ccaf9189d9599c941c563fe5ae32578e

Fix crash on unmounted volume in tree pane right click (Bug #15452)

https://git.xfce.org/xfce/thunar/commit?id=479655f5ccaf9189d9599c941c563fe5ae32578e

Revision history for this message

In Xfce Bugzilla #15452, Gitbot (gitbot) wrote on 2019-05-24:

#11

Andre Miranda referenced this bugreport in commit ba3502eaaf398ef5fac12dcc9d23fe47959c4eba

Fix crash on unmounted volume in tree pane right click (Bug #15452)

https://git.xfce.org/xfce/thunar/commit?id=ba3502eaaf398ef5fac12dcc9d23fe47959c4eba

Revision history for this message

In Xfce Bugzilla #15452, Andreldm-2 (andreldm-2) wrote on 2019-05-24:

#12

I guess this regression was introduce by this commit:
https://git.xfce.org/xfce/thunar/commit/?id=cb12bc1

We should not rely on _thunar_return_val_if_fail or g_return_val_if_fail for NULL check, those macros are only meant for debugging.

Revision history for this message

In Xfce Bugzilla #15452, Alexxcons-x (alexxcons-x) wrote on 2019-06-02:

#13

*** Bug 15508 has been marked as a duplicate of this bug. ***

Bug Watch Updater (bug-watch-updater) on 2019-06-25

Changed in thunar:
importance:	Unknown → Medium
status:	Unknown → Fix Released

Revision history for this message

Theo Linkspfeifer (lastonestanding) wrote on 2020-04-24:

#14

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:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1830621

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

xfce-bugs #15452
[RESOLVED FIXED] Edit

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