Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 cmdline: python /usr/bin/tintwizard.py executable: /usr/bin/tintwizard.py kernel: 3.1.2-1.fc16.x86_64 reason: tintwizard.py:2057:writeConf:IOError: [Errno 2] No such file or directory: '/home/jlo/.config/tint2/tintwizard.conf' time: Sun 11 Dec 2011 03:35:42 PM EET uid: 500 backtrace: :tintwizard.py:2057:writeConf:IOError: [Errno 2] No such file or directory: '/home/jlo/.config/tint2/tintwizard.conf' : :Traceback (most recent call last): : File "/usr/bin/tintwizard.py", line 2209, in <module> : tw = TintWizardGUI() : File "/usr/bin/tintwizard.py", line 187, in __init__ : self.readConf() : File "/usr/bin/tintwizard.py", line 1732, in readConf : self.writeConf() : File "/usr/bin/tintwizard.py", line 2057, in writeConf : f = open(pathName+"tintwizard.conf", "w") :IOError: [Errno 2] No such file or directory: '/home/jlo/.config/tint2/tintwizard.conf' : :Local variables in innermost frame: :confStr: '#Start\n[defaults]\nborderColor = None\nbgColor = None\nfont = None\nfgColor = None\nbgCount = None\n#End\n' :self: <TintWizardGUI object at 0x147b5f0 (uninitialized at 0x0)> :pathName: '/home/jlo/.config/tint2/' :key: 'bgCount'
Try running tint2 before opening tintwizard, and let me know what happens.
I do not remember anymore where did that bug report and backtrace came from, and it doesn't seem to say it the report. The report was created somehow by abrt-daemon, so the bug (not had run tintwizard before) is somewhere in the abrt-system then. Additionally I didn't even have tintwizard installed in my cleanly installed Fedora 16 PC, so could it be just a missing dependency in some abrt-package what was the problem.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.