Red Hat Bugzilla – Bug 1282636
[abrt] yumex-dnf: locale.py:592:setlocale:locale.Error: unsupported locale setting
Last modified: 2016-12-20 10:59:40 EST
Version-Release number of selected component:
cmdline: /usr/bin/python3 -tt /bin/yumex-dnf
runlevel: N 5
locale.py:592:setlocale:locale.Error: unsupported locale setting
Traceback (most recent call last):
File "/bin/yumex-dnf", line 33, in <module>
from yumex import YumexApplication
File "/usr/lib/python3.4/site-packages/yumex/__init__.py", line 25, in <module>
from yumex.misc import doGtkEvents, _, CONFIG, ExceptionHandler,\
File "/usr/lib/python3.4/site-packages/yumex/misc.py", line 38, in <module>
File "/usr/lib64/python3.4/locale.py", line 592, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
Local variables in innermost frame:
Potential duplicate: bug 1225635
Created attachment 1095142 [details]
Created attachment 1095143 [details]
Look like some problem with the locale setting on your system
please post the output from
# locale -a
Created attachment 1103371 [details]
filechooser showing incorrect timedata format according to locale setting
screen shot of filechooser showing incorrect locale format. Same issue in dolphin and anywhere time/date is displayed.
I have also modified and a locale to properly display the timedate formats. It half works, displaying the date format correctly but not the time, despite what the locale reports.
(In reply to Tim Lauridsen from comment #3)
> Look like some problem with the locale setting on your system
> please post the output from
> # locale
> # locale -a
Was trying to set system time and date format to 24hr and YYYY-MM-DD. So was playing with locale settings. Created localized version of en_CA to en_CA@iso with proper required date/time format. Partially worked, date fmt displayed correctly but not time. Adding to either ~./bashrc or /etc/locale.conf did not properly work either.
Result is still can't proper date(24hr) & time formats (YYYY-MM-DD) displayed for en_CA.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.