Bug 1026492 - [abrt] smolt-1.4.3-6.fc17: smolt.py:744:send:UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 76: ordinal not in range(128)
[abrt] smolt-1.4.3-6.fc17: smolt.py:744:send:UnicodeDecodeError: 'ascii' code...
Product: Fedora
Classification: Fedora
Component: smolt (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-11-04 14:22 EST by gigalamer
Modified: 2015-02-17 14:02 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 14:02:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (848 bytes, text/plain)
2013-11-04 14:22 EST, gigalamer
no flags Details
File: environ (203 bytes, text/plain)
2013-11-04 14:22 EST, gigalamer
no flags Details

  None (edit)
Description gigalamer 2013-11-04 14:22:17 EST
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.9
cmdline:        /usr/bin/python /usr/bin/smoltSendProfile -c
executable:     /usr/bin/smoltSendProfile
kernel:         3.11.6-200.fc19.x86_64
runlevel:       N 5
type:           Python
uid:            999

Truncated backtrace:
smolt.py:744:send:UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 76: ordinal not in range(128)

Traceback (most recent call last):
  File "/usr/bin/smoltSendProfile", line 281, in <module>
  File "/usr/share/smolt/client/smolt.py", line 744, in send
    error(_('Error contacting Server: %s') % e)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 76: ordinal not in range(128)

Local variables in innermost frame:
e: URLGrabError(14, 'curl#6 - "Could not resolve host: www.smolts.org; Ta nazwa lub us\xc5\x82uga jest nieznana"')
smoonURL: 'http://www.smolts.org/'
self: <smolt._Hardware instance at 0x1623128>
serialize: <function serialize at 0x1622398>
batch: True
grabber: <urlgrabber.grabber.URLGrabber object at 0x13df490>
user_agent: 'smolt/0.97'
timeout: 120.0
proxies: None
Comment 1 gigalamer 2013-11-04 14:22:24 EST
Created attachment 819323 [details]
File: backtrace
Comment 2 gigalamer 2013-11-04 14:22:27 EST
Created attachment 819324 [details]
File: environ
Comment 3 Fedora End Of Life 2015-01-09 15:27:33 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 4 Fedora End Of Life 2015-02-17 14:02:34 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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

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.