Hide Forgot
Created attachment 805352 [details] Backtrace file when I clicked to "trash" button Description of problem: First when I click the "trash" button on thunar It's gonna be stuck and never give reponse or any abrt signal. I just click "close" button on window manager and see "force close" messages click "yes", re-open thunar.and so on. For see backtrace and crash report ##################################### /etc/abrt/plugins/python.conf adding this line set RequireAbsolutePath = no ##################################### /etc/abrt/abrt-action-save-package-data.conf adding this line set ProcessUnpackaged = yes ##################################### Final backtrace file in attachment
What does: rpm -q python-simplejson output? If it's not installed, and you do a 'yum install python-simplejson' does it start working?
rpm -q python simplejson It wasn't installed. After that I installed. and still stuck and crash. Not working.
Is the backtrace the same now? Or did it change?
This time no error just "Thunar" gonna stuck only was I have "force" close and no messages from "grep /var/log/messages/" For backtrace no backtrace coming up with settings I wrote up there.
So, this 'freeze' happens every time you click the empty trash?
Yes always happen... I also notice on desktop trash icon looks empty but when I click the inside I can see file in there so there must sync problem with trash but always show empty and never open.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.