thunar crashed with SIGSEGV

Bug #1868884 reported by David Kastrup
This bug report is a duplicate of:  Bug #1834014: thunar crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
New
Undecided
Unassigned

Bug Description

This has been happening for years on end now with SDcards in a card reader at random times while browsing. Possibly short after automount, but also on other occasions.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: thunar 1.8.12-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
Uname: Linux 5.4.0-18-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Tue Mar 24 22:53:05 2020
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (3084 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: 0x55caf3921f5c: mov (%r14),%r12
 PC (0x55caf3921f5c) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_hash_table_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to focal on 2020-03-09 (15 days ago)
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 : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1834014, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
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.