Bug 1135652

Summary: [abrt] bleachbit: GUI.py:368:worker_done:Error: Timeout was reached
Product: [Fedora] Fedora Reporter: ihatewindoze
Component: bleachbitAssignee: Christopher Meng <i>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: i, mastaizawfm, metherid, redstar3894
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fa0d8eec5c2cf78a716892433c0ebbf6c14e3b45
Whiteboard: abrt_hash:065277ae72d103c68e49f048c87986ea9a5e1580
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:19:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description ihatewindoze 2014-08-29 22:23:14 UTC
Description of problem:
was exiting/quitting the program/application, after cleaning.

Version-Release number of selected component:
bleachbit-1.3-1.fc20

Additional info:
reporter:       libreport-2.2.3
cmdline:        python /usr/bin/bleachbit
executable:     /usr/bin/bleachbit
kernel:         3.15.10-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
GUI.py:368:worker_done:Error: Timeout was reached

Traceback (most recent call last):
  File "/usr/share/bleachbit/Worker.py", line 271, in run
    self.ui.worker_done(self, self.really_delete)
  File "/usr/share/bleachbit/GUI.py", line 368, in worker_done
    notify.show()
Error: Timeout was reached

Local variables in innermost frame:
really_delete: True
pynotify: <module 'pynotify' from '/usr/lib64/python2.7/site-packages/gtk-2.0/pynotify/__init__.pyc'>
worker: <bleachbit.Worker.Worker instance at 0xe0fd88>
elapsed: 87.18002486228943
notify: <pynotify.Notification object at 0x1473aa0 (NotifyNotification at 0x1164240)>
self: <bleachbit.GUI.GUI instance at 0xcb8560>

Comment 1 ihatewindoze 2014-08-29 22:23:16 UTC
Created attachment 932823 [details]
File: backtrace

Comment 2 ihatewindoze 2014-08-29 22:23:16 UTC
Created attachment 932824 [details]
File: environ

Comment 3 Fedora Admin XMLRPC Client 2015-03-21 18:40:08 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2015-05-29 12:45:49 UTC
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.

Comment 5 Fedora End Of Life 2015-06-29 22:19:30 UTC
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.