Bug 753403

Summary: [abrt] pyrenamer-0.6.0-8.fc16: pyrenamer_prefs.py:99:create_preferences_dialog:TypeError: Gtk.Entry.set_text() argument 1 must be string, not None
Product: [Fedora] Fedora Reporter: Daniel <daniel.distler>
Component: pyrenamerAssignee: Gwyn Ciesla <gwync>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gwync, net.subscription, OrangeRedHatBugzilla, unix63
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8223912af33b4e7d7a80d307f725d2a4ef338730
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 15:59:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Daniel 2011-11-12 09:50:14 UTC
libreport version: 2.0.6
abrt_version:   2.0.4.981
cmdline:        python /usr/bin/pyrenamer
executable:     /usr/bin/pyrenamer
kernel:         3.1.0-7.fc16.x86_64
reason:         pyrenamer_prefs.py:99:create_preferences_dialog:TypeError: Gtk.Entry.set_text() argument 1 must be string, not None
time:           Sat Nov 12 09:54:46 2011
uid:            1000

backtrace:
:pyrenamer_prefs.py:99:create_preferences_dialog:TypeError: Gtk.Entry.set_text() argument 1 must be string, not None
:
:Traceback (most recent call last):
:  File "/usr/lib/python2.7/site-packages/pyrenamer/pyrenamer.py", line 1261, in on_preferences_activate
:    self.prefs.create_preferences_dialog()
:  File "/usr/lib/python2.7/site-packages/pyrenamer/pyrenamer_prefs.py", line 99, in create_preferences_dialog
:    self.prefs_entry_root.set_text(root_dir)
:TypeError: Gtk.Entry.set_text() argument 1 must be string, not None
:
:Local variables in innermost frame:
:active_dir: None
:signals: {'on_prefs_browse_root_clicked': <bound method PyrenamerPrefs.on_prefs_browse_root_clicked of <pyrenamer.pyrenamer_prefs.PyrenamerPrefs instance at 0xb536c8>>, 'on_prefs_window_destroy': <bound method PyrenamerPrefs.on_prefs_destroy of <pyrenamer.pyrenamer_prefs.PyrenamerPrefs instance at 0xb536c8>>, 'on_prefs_browse_active_clicked': <bound method PyrenamerPrefs.on_prefs_browse_active_clicked of <pyrenamer.pyrenamer_prefs.PyrenamerPrefs instance at 0xb536c8>>, 'on_prefs_close_clicked': <bound method PyrenamerPrefs.on_prefs_close_clicked of <pyrenamer.pyrenamer_prefs.PyrenamerPrefs instance at 0xb536c8>>}
:self: <pyrenamer.pyrenamer_prefs.PyrenamerPrefs instance at 0xb536c8>
:client: <gconf.Client object at 0xd50780 (GConfClient at 0xa57120)>
:root_dir: None

comment:
:open preferences
:leave both text boxes empty
:error will be handled properly (default values are inserted) but ABRT pops up

Comment 1 Rakesh Jain 2011-11-12 12:17:04 UTC
Package: pyrenamer-0.6.0-8.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
open the renamer

Comment 2 Fedora End Of Life 2013-01-16 14:43:40 UTC
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

Comment 3 Fedora End Of Life 2013-02-13 15:59:11 UTC
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.