thunar crashed with SIGSEGV in g_mutex_lock()
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
ProcVersionSign
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/
()
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
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:
Changed in thunar: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
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