thunar crashed with SIGSEGV in g_sequence_insert_sorted_iter() aftr backing out folder while it was listing contents
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
thunar: 1.6.10-2
Browsing in to folder and backing out with "3rd" mousebutton while thunar still updating folders contents view crashed instead backing to previous folder.
I'm almost sure this behaviour occured in 15.10 too, atleast once in a while. Could this be brtrfs related? This current crash was on btrfs formatted harddisk.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: thunar 1.6.10-2
ProcVersionSign
Uname: Linux 4.4.0-8-lowlatency x86_64
NonfreeKernelMo
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar 3 20:11:57 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2015-11-07 (116 days ago)
InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: Thunar --sm-client-id 2c06c7426-
ProcEnviron:
LANGUAGE=fi_FI
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fi_FI.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x555aae4815a2: cmpl $0x2,0x20(%rdi)
PC (0x555aae4815a2) ok
source "$0x2" ok
destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
?? ()
?? ()
?? () from /lib/x86_
?? () from /lib/x86_
g_sequence_
Title: thunar crashed with SIGSEGV in g_sequence_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip disk libvirtd lp lpadmin plugdev roccat sambashare scanner sudo
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 #1147349, 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.