thunar crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| thunar (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
This one happened when trying to unmount an extfs device (SDcard) which was still busy. Notification appeared, so I closed two eom image windows still open on the device (probably blocking it by virtue of having their cwd on the device rather than any file actively open). Then the notification window disappeared on its own (which would be close to what I expected) and Thunar crashed.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: thunar 1.8.6-0ubuntu1
ProcVersionSign
Uname: Linux 5.0.0-15-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon May 27 16:04:44 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2782 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/Thunar --daemon
SegvAnalysis:
Segfault happened at: 0x559720bd8220: mov 0x28(%rdi),%rax
PC (0x559720bd8220) 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/
() at /usr/lib/
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to eoan on 2019-05-12 (15 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare
separator:
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-amd64-retrace |
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 #1829921, 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.