Bug 1299827

Summary: [abrt] autojump: autojump:120:save:IOError: [Errno 28] No space left on device
Product: [Fedora] Fedora Reporter: Allan Poulsen <apo>
Component: autojumpAssignee: Thibault North <thibault.north>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: relrod, thibault.north, ttomecek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e42dd9e62bfecf48a56eaa19473c687c4a055050
Whiteboard: abrt_hash:5828076d721adf72fdbd7362cbce53cfbdcbb407;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 17:59:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Allan Poulsen 2016-01-19 10:57:26 UTC
Version-Release number of selected component:
autojump-21.7.1-5.fc23

Additional info:
reporter:       libreport-2.6.3
cmdline:        /usr/bin/python /usr/bin/autojump -a /home/apo/programs
executable:     /usr/bin/autojump
kernel:         4.2.6-301.fc23.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
autojump:120:save:IOError: [Errno 28] No space left on device

Traceback (most recent call last):
  File "/usr/bin/autojump", line 525, in <module>
    sys.exit(main())
  File "/usr/bin/autojump", line 471, in main
    config = parse_arg(parse_env(set_defaults()))
  File "/usr/bin/autojump", line 287, in parse_arg
    db.add(decode(args.add))
  File "/usr/bin/autojump", line 159, in add
    self.save()
  File "/usr/bin/autojump", line 120, in save
    temp.write((unico("%s\t%s\n" % (weight, path)).encode("utf-8")))
IOError: [Errno 28] No space left on device

Local variables in innermost frame:
path: u'/home'
self: <__main__.Database instance at 0x7fe0095f1560>
temp: <open file '<fdopen>', mode 'w+b' at 0x7fe0018e3300>
weight: 22.360679775

Potential duplicate: bug 1262727

Comment 1 Allan Poulsen 2016-01-19 10:57:32 UTC
Created attachment 1116138 [details]
File: backtrace

Comment 2 Allan Poulsen 2016-01-19 10:57:33 UTC
Created attachment 1116139 [details]
File: environ

Comment 3 Fedora End Of Life 2016-11-24 15:03:02 UTC
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'
of '23'.

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.

Comment 4 Fedora End Of Life 2016-12-20 17:59:58 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.