Version-Release number of selected component: system-config-printer-1.4.7-1.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py executable: /usr/share/system-config-printer/system-config-printer.py kernel: 3.18.7-100.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: utf_8.py:16:decode:UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-9: ordinal not in range(128) Traceback (most recent call last): File "/usr/share/system-config-printer/newprinter.py", line 2773, in on_tvNPDevices_cursor_changed u = device.menuentry.decode ('utf-8') File "/usr/lib64/python2.7/encodings/utf_8.py", line 16, in decode return codecs.utf_8_decode(input, errors, True) UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-9: ordinal not in range(128) Local variables in innermost frame: input: u'\u0412\u0456\u0434\u0434\u0430\u043b\u0435\u043d\u0438\u0439 \u043f\u0440\u0438\u043d\u0442\u0435\u0440 CUPS \u0437\u0430 \u0434\u043e\u043f\u043e\u043c\u043e\u0433\u043e\u044e DNS-SD' errors: 'strict'
Created attachment 994959 [details] File: backtrace
Created attachment 994960 [details] File: dso_list
Created attachment 994961 [details] File: environ
This seems like a problem with one of the translations. What does 'locale' say?
LANG=uk_UA.utf8 LC_CTYPE="uk_UA.utf8" LC_NUMERIC="uk_UA.utf8" LC_TIME="uk_UA.utf8" LC_COLLATE="uk_UA.utf8" LC_MONETARY="uk_UA.utf8" LC_MESSAGES="uk_UA.utf8" LC_PAPER="uk_UA.utf8" LC_NAME="uk_UA.utf8" LC_ADDRESS="uk_UA.utf8" LC_TELEPHONE="uk_UA.utf8" LC_MEASUREMENT="uk_UA.utf8" LC_IDENTIFICATION="uk_UA.utf8" LC_ALL=
Oh, I see what's going on. Fixed upstream: https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.x&id=8f78781c2c1e41febd69eca03c3deb4b994edefc
system-config-printer-1.4.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/system-config-printer-1.4.8-1.fc20
Package system-config-printer-1.4.8-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 system-config-printer-1.4.8-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4086/system-config-printer-1.4.8-1.fc20 then log in and leave karma (feedback).
This is included in system-config-printer-1.4.8-2.fc20, not sure why the update system didn't set this back to ON_QA.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.