Bug 1609073 - [abrt] autojump: lambda(): autojump_data.py:71:<lambda>:UnicodeEncodeError: 'decimal' codec can't encode characters in position 0-28597: invalid decimal Unicode string
Summary: [abrt] autojump: lambda(): autojump_data.py:71:<lambda>:UnicodeEncodeError: '...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: autojump
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thibault North
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:fbd2507b1c5251b4bec63cde4df...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-27 00:10 UTC by Paul DeStefano
Modified: 2019-05-28 21:58 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 21:58:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (112.50 KB, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details
File: cgroup (339 bytes, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details
File: cpuinfo (1.44 KB, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details
File: environ (4.46 KB, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details
File: mountinfo (5.12 KB, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details
File: namespaces (129 bytes, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details
File: open_fds (286 bytes, text/plain)
2018-07-27 00:10 UTC, Paul DeStefano
no flags Details

Description Paul DeStefano 2018-07-27 00:10:09 UTC
Version-Release number of selected component:
autojump-22.3.2-5.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        /usr/bin/python2 /usr/bin/autojump --add /home/pdestefa/tmp
crash_function: lambda
exception_type: UnicodeEncodeError
executable:     /usr/bin/autojump
interpreter:    python2-2.7.15-2.fc28.x86_64
kernel:         4.17.7-200.fc28.x86_64
runlevel:       N 5
type:           Python
uid:            13013

Truncated backtrace:
#1 <lambda> in /usr/lib/python2.7/site-packages/autojump_data.py:71
#2 load in /usr/lib/python2.7/site-packages/autojump_data.py:81
#3 main in /usr/bin/autojump:364
#4 <module> in /usr/bin/autojump:420

Comment 1 Paul DeStefano 2018-07-27 00:10:16 UTC
Created attachment 1470911 [details]
File: backtrace

Comment 2 Paul DeStefano 2018-07-27 00:10:17 UTC
Created attachment 1470912 [details]
File: cgroup

Comment 3 Paul DeStefano 2018-07-27 00:10:18 UTC
Created attachment 1470913 [details]
File: cpuinfo

Comment 4 Paul DeStefano 2018-07-27 00:10:19 UTC
Created attachment 1470914 [details]
File: environ

Comment 5 Paul DeStefano 2018-07-27 00:10:20 UTC
Created attachment 1470915 [details]
File: mountinfo

Comment 6 Paul DeStefano 2018-07-27 00:10:21 UTC
Created attachment 1470916 [details]
File: namespaces

Comment 7 Paul DeStefano 2018-07-27 00:10:22 UTC
Created attachment 1470917 [details]
File: open_fds

Comment 8 Paul DeStefano 2018-07-27 00:54:22 UTC
autojump constantly corrupts itself.  It is reported upstream, but it doesn't seem to be making any progress.

https://github.com/wting/autojump/issues/391

This happens nearly as often during a normal reboot as during a system crash.  It's extremely frustrating.

Comment 9 Ben Cotton 2019-05-02 19:21:03 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 10 Ben Cotton 2019-05-02 21:15:09 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 11 Ben Cotton 2019-05-28 21:58:22 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.


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