Bug 798972 - liveusb fails with non illogical error message
Summary: liveusb fails with non illogical error message
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: liveusb-creator
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Luke Macken
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-01 12:08 UTC by Jes Sorensen
Modified: 2016-09-20 02:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-01 17:04:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jes Sorensen 2012-03-01 12:08:13 UTC
Description of problem:
Fedora 17 Alpha install with updates. Trying to launch liveusb-creator
it fails with the following output:

[jes@mahomaho ~]$ liveusb-creator
Traceback (most recent call last):
  File "/sbin/liveusb-creator", line 89, in <module>
    main()
  File "/sbin/liveusb-creator", line 82, in main
    from liveusb.gui import LiveUSBApp
  File "/usr/lib/python2.7/site-packages/liveusb/__init__.py", line 29, in <module>
    os.environ['LANG'] = lang
  File "/usr/lib64/python2.7/os.py", line 471, in __setitem__
    putenv(key, item)
TypeError: must be string, not None
[jes@mahomaho ~]$ echo $LANG
en_US.UTF-8
[jes@mahomaho ~]$ 

I tried un-setting $LANG, but it results in the same error.

Version-Release number of selected component (if applicable):
[root@mahomaho ~]# rpm -q liveusb-creator 
liveusb-creator-3.11.6-2.fc17.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Install F17 Alpha
2. yum install liveusb-creator
3. run liveusb-creator
  
Actual results:
Fails to start with illogical python backtrace

Expected results:


Additional info:

Comment 1 Luke Macken 2013-03-01 17:04:47 UTC
This issue has been fixed with the latest version of the liveusb-creator. Please re-open if you still experience this problem. Thanks!


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