Bug 1323004

Summary: [abrt] Thunar: g_local_file_trash(): thunar killed by SIGABRT
Product: [Fedora] Fedora Reporter: taku158 <taku158>
Component: ThunarAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: cwickert, dhiru, kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f862ca2ed01b1aaad449fb0a1c05b752347087fe
Whiteboard: abrt_hash:d8a125d9a133e3c62ddfe2742d96d0a1cfa66694;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:44:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description taku158 2016-03-31 23:59:28 UTC 
Description of problem:
I deleted 3 folder on a NTFS partition, including the ".Trash-1000" folder.

Version-Release number of selected component:
Thunar-1.6.10-2.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/Thunar --daemon
crash_function: g_local_file_trash
executable:     /usr/bin/thunar
global_pid:     3498
kernel:         4.3.5-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #7 g_local_file_trash at glocalfile.c:2143
 #8 _thunar_io_jobs_trash at thunar-io-jobs.c:823
 #9 thunar_simple_job_execute at thunar-simple-job.c:119
 #10 exo_job_scheduler_job_func at exo-job.c:317
 #11 io_job_thread at gioscheduler.c:85
 #12 g_task_thread_pool_thread at gtask.c:1283
 #14 g_thread_proxy at gthread.c:778
Comment 1 taku158 2016-03-31 23:59:42 UTC 
Created attachment 1142387 [details]
File: backtrace
Comment 2 taku158 2016-03-31 23:59:45 UTC 
Created attachment 1142388 [details]
File: cgroup
Comment 3 taku158 2016-03-31 23:59:52 UTC 
Created attachment 1142389 [details]
File: core_backtrace
Comment 4 taku158 2016-03-31 23:59:56 UTC 
Created attachment 1142390 [details]
File: dso_list
Comment 5 taku158 2016-03-31 23:59:58 UTC 
Created attachment 1142391 [details]
File: environ
Comment 6 taku158 2016-04-01 00:00:01 UTC 
Created attachment 1142392 [details]
File: limits
Comment 7 taku158 2016-04-01 00:00:09 UTC 
Created attachment 1142393 [details]
File: maps
Comment 8 taku158 2016-04-01 00:00:13 UTC 
Created attachment 1142394 [details]
File: mountinfo
Comment 9 taku158 2016-04-01 00:00:14 UTC 
Created attachment 1142395 [details]
File: open_fds
Comment 10 taku158 2016-04-01 00:00:17 UTC 
Created attachment 1142396 [details]
File: proc_pid_status
Comment 11 Mukundan Ragavan 2016-04-01 00:01:21 UTC 
I wonder if this is a variation of the "Crash upon move" issue we have been having.
Comment 12 Mukundan Ragavan 2016-04-01 01:22:16 UTC 
To test my hypothesis, can you install this build and try to reproduce the crash?

https://nonamedotc.fedorapeople.org/thunar-fix/

The page linked above has packages for rawhide, f24, f23 and f22 on x86_64, i686 and arm arches.
Comment 13 Fedora End Of Life 2016-11-24 16:19:22 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2016-12-20 19:44:48 UTC 
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.