Red Hat Bugzilla – Bug 1285892
[abrt] Thunar: thunar_file_info_reload(): thunar killed by SIGSEGV
Last modified: 2016-04-25 04:28:50 EDT
Version-Release number of selected component:
cmdline: Thunar --daemon
runlevel: N 5
Thread no. 1 (4 frames)
#0 thunar_file_info_reload at thunar-file.c:975
#1 thunar_file_load at thunar-file.c:1177
#2 thunar_file_reload at thunar-file.c:3926
#7 gtk_main at gtkmain.c:1268
Created attachment 1099462 [details]
Created attachment 1099463 [details]
Created attachment 1099464 [details]
Created attachment 1099465 [details]
Created attachment 1099466 [details]
Created attachment 1099467 [details]
Created attachment 1099468 [details]
Created attachment 1099469 [details]
Created attachment 1099470 [details]
Created attachment 1099471 [details]
Created attachment 1099472 [details]
Created attachment 1099473 [details]
What were you doing when this crash happened?
Can you duplicate it?
I really don't know what caused this, I had a directory structure as follows:
SAMSUNG ELECTRONICS CO., LTD._N145P/
With 7 or 8 text files inside, (my /home/ mountpoint is actually in another partition on the same disk, if that matters), and I then proceeded to navigate down until N260P_ZWSC93KB100450/ to see the files, then I navigated up twice into SAMSUNG ELECTRONICS CO., LTD._N145P/ and copied N250P/'s name (by using Ctrl+F2 to rename, copy, and then ESC to close the rename dialog), navigated up once into my home to rename "SAMSUNG ELECTRONICS CO., LTD._N145P/" and appended _N250P to the name. Then I navigated down into N250P/ to copy N260P_ZWSC93KB100450/'s name, navigated up twice into my home again to finally renaming SAMSUNG ELECTRONICS CO., LTD._N145P_N250P/ to "SAMSUNG ELECTRONICS CO., LTD._N145P_N250P_N260P_ZWSC93KB100450", I then navigated down into N260P_ZWSC93KB100450/, cut the files (CTRL+X) and navigated up into (now named) SAMSUNG ELECTRONICS CO., LTD._N145P_N250P_N260P_ZWSC93KB100450/ to paste them (CTRL+V) and the crash happened. When I opened Thunar again all the files were where I pasted them and none were corrupted or missing.
What I basically did was
- Be at /home/ariel/.
- Navigated down into /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P/N250P/N260P_ZWSC93KB100450/ to see the files.
- Navigated up into /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P/ and copied N250P/'s name.
- Navigated up into /home/ariel and renamed /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P/ to /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P_N250P/.
- Navigated down into /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P_N250P/N250P/ and copied N260P_ZWSC93KB100450/'s name.
- Navigated up into /home/ariel and renamed /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P_N250P/ to /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P_N250P_N260P_ZWSC93KB100450/
- Navigated down into /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P_N250P_N260P_ZWSC93KB100450/N250P/N260P_ZWSC93KB100450/ and cut the files (CTRL+A, CTRL+X)
- Navigated up into /home/ariel/SAMSUNG ELECTRONICS CO., LTD._N145P_N250P_N260P_ZWSC93KB100450/ and pasted the files (CTRL+V).
Then the crash happened.
I tried to reproduce this by creating a tree structure of at least 2 levels with some files inside, navigating up, renaming the top dir, navigating down to cut the files and navigating up to paste the files, but it did not crash again.
Another user experienced a similar problem:
I moved a file from one folder to sub-folder of the first folder, using CTRL+X and CTRL+V.
The program then crashed.
Sorry, not easily possible to reproduce.
reason: thunar killed by SIGSEGV
runlevel: N 5
Ctrl-x + ctrl-v here as well, from parent folder to its subfolder.
... happened also twice tonight after/during rename (via mouse left).
Created attachment 1135968 [details]
I recompiled Thunar with address sanitizer (./configure --enable-dbus --enable-debug=yes FLAGS="-fsanitize=address" CXXFLAGS="-fsanitize=address" LDFLAGS="-fsanitize=address" --prefix=/var/tmp/thunar). Please find attached a crash report. Don't remember anymore what I was doing when it happened...
Can you try this build?
This build might mitigate the issue some but not really solve I believe.
*** Bug 1320402 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1279070 ***
*** Bug 1329971 has been marked as a duplicate of this bug. ***