Thunar crashes when renaming file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunar (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
With the latest updates on Xubuntu 16.04 beta 2 I rename a file with the file browser.
It crashes about 5-10% of the time I rename a file. all the open file windows are closed. other running programs are not affected.
To replicate:
install the latest xubuntu beta ISO. open a folder in the user's home directory. create a new document by right clicking in the window. press f2 to open the rename dialog. give it a different name, and press enter.
repeat the f2 rename to new name step. after 10-20 renames, thunar will crash.
file system is btrfs in an encrypted partition.
$ lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
$ apt-cache policy thunar
thunar:
Installed: 1.6.10-2
Candidate: 1.6.10-2
Version table:
*** 1.6.10-2 500
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: thunar 1.6.10-2
ProcVersionSign
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Apr 2 10:32:02 2016
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2016-03-27 (6 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/bin/Thunar file://
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: thunar
StacktraceTop:
thunar_
?? ()
?? () from /lib/x86_
?? () from /lib/x86_
g_sequence_
Title: thunar crashed with SIGSEGV in thunar_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo
information type: | Private → Public |
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 #1495409, 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.