Bug 901367 - [abrt] system-config-bind-4.0.15-6.fc18: RRGUI.py:1934:browse_clicked:TypeError: cannot concatenate 'str' and 'list' objects
Summary: [abrt] system-config-bind-4.0.15-6.fc18: RRGUI.py:1934:browse_clicked:TypeErr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-bind
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7d3949dfe1a51b136b9a7a9fbfa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 04:18 UTC by Ted Henscheid
Modified: 2014-02-05 15:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:07:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (456 bytes, text/plain)
2013-01-18 04:18 UTC, Ted Henscheid
no flags Details
File: environ (295 bytes, text/plain)
2013-01-18 04:18 UTC, Ted Henscheid
no flags Details
File: smolt_data (2.71 KB, text/plain)
2013-01-18 04:18 UTC, Ted Henscheid
no flags Details

Description Ted Henscheid 2013-01-18 04:18:00 UTC
Version-Release number of selected component:
system-config-bind-4.0.15-6.fc18

Additional info:
cmdline:        /usr/bin/python /usr/sbin/system-config-bind
core_backtrace: a426c127b7482744daa2bd8d34ecfb384b5de989 0x78e browse_clicked /usr/share/system-config-bind/RRGUI.py -
executable:     /usr/sbin/system-config-bind
kernel:         3.7.2-201.fc18.x86_64
uid:            0

Truncated backtrace:
RRGUI.py:1934:browse_clicked:TypeError: cannot concatenate 'str' and 'list' objects

Traceback (most recent call last):
  File "/usr/share/system-config-bind/RRGUI.py", line 1934, in browse_clicked
    name += ' '+_('for')+' '+s.dialog.name
TypeError: cannot concatenate 'str' and 'list' objects

Local variables in innermost frame:
s: <RRGUI.DNS_Path instance at 0x168d7a0>
b: <gtk.Button object at 0x1694640 (GtkButton at 0x191c0f0)>
name: 'Choose File'

Comment 1 Ted Henscheid 2013-01-18 04:18:02 UTC
Created attachment 682004 [details]
File: backtrace

Comment 2 Ted Henscheid 2013-01-18 04:18:18 UTC
Created attachment 682005 [details]
File: environ

Comment 3 Ted Henscheid 2013-01-18 04:18:20 UTC
Created attachment 682006 [details]
File: smolt_data

Comment 4 Fedora End Of Life 2013-12-21 10:30:01 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2014-02-05 15:07:15 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.