Bug 1005347

Summary: [abrt] metromap-0.1.3-5.fc20: ReadMap.py:102:GetMapName:TypeError: coercing to Unicode: need string or buffer, list found
Product: [Fedora] Fedora Reporter: Christopher Meng <i>
Component: metromapAssignee: Fabian Affolter <mail>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: i, mail
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f041b18592b9fb859f1325be894705fe5a2e7042
Fixed In Version: metromap-0.1.4-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-22 04:24:15 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 Christopher Meng 2013-09-06 17:13:12 UTC
Version-Release number of selected component:
metromap-0.1.3-5.fc20

Additional info:
reporter:       libreport-2.1.6
cmdline:        /usr/bin/python /usr/bin/metromap
executable:     /usr/bin/metromap
kernel:         3.11.0-3.fc21.i686+PAE
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
ReadMap.py:102:GetMapName:TypeError: coercing to Unicode: need string or buffer, list found

Traceback (most recent call last):
  File "/usr/bin/metromap", line 368, in <module>
    name = GetMapName(f)
  File "/usr/share/metromap/modules/ReadMap.py", line 102, in GetMapName
    return unicode(name, detect_encoding(name))
TypeError: coercing to Unicode: need string or buffer, list found

Local variables in innermost frame:
name: ['Berlin']
lsec: ['options']
s: 'Options'
sec: ['Options']
ini: <StringIO.StringIO instance at 0x8fdcdcc>
cp: <ConfigParser.RawConfigParser instance at 0x8fdca2c>

Potential duplicate: bug 859683

Comment 1 Christopher Meng 2013-09-06 17:13:15 UTC
Created attachment 794903 [details]
File: backtrace

Comment 2 Christopher Meng 2013-09-06 17:13:20 UTC
Created attachment 794905 [details]
File: environ

Comment 3 Fedora Update System 2013-09-07 09:06:02 UTC
metromap-0.1.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/metromap-0.1.4-1.fc19

Comment 4 Fedora Update System 2013-09-07 09:06:10 UTC
metromap-0.1.4-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/metromap-0.1.4-1.fc18

Comment 5 Fedora Update System 2013-09-07 09:06:19 UTC
metromap-0.1.4-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/metromap-0.1.4-1.fc20

Comment 6 Fedora Update System 2013-09-07 17:04:45 UTC
Package metromap-0.1.4-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing metromap-0.1.4-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-16045/metromap-0.1.4-1.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-09-22 04:24:15 UTC
metromap-0.1.4-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-09-22 04:26:31 UTC
metromap-0.1.4-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-09-23 00:02:07 UTC
metromap-0.1.4-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.