Bug 879975

Summary: [abrt] ranger-1.2.2-3.fc17: ui.py:92:suspend:error: nocbreak() returned ERR
Product: [Fedora] Fedora Reporter: Patrick Ooooeee <patrick0000eee>
Component: rangerAssignee: Ben Boeckel <fedora>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6d9f446a6d7c3dedc64b8466ab27476b7f4b55c4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 03:35:37 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: executable
none
File: environ
none
File: smolt_data
none
File: core_backtrace none

Description Patrick Ooooeee 2012-11-25 19:03:44 UTC 
Description of problem:
I tried to change the name of a file, and ranger said "permission denied" even though I'm running it as the same user that is the owner of the file. PCManFM has been doing the same since an update a few days ago.

Version-Release number of selected component:
ranger-1.2.2-3.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        /usr/bin/python -O /bin/ranger
kernel:         3.6.7-4.fc17.x86_64

backtrace:
:ui.py:92:suspend:error: nocbreak() returned ERR
:
:Traceback (most recent call last):
:  File "/bin/ranger", line 56, in <module>
:    sys.exit(main())
:  File "/usr/lib/python2.7/site-packages/ranger/__main__.py", line 232, in main
:    fm.ui.destroy()
:  File "/usr/lib/python2.7/site-packages/ranger/gui/ui.py", line 117, in destroy
:    self.suspend()
:  File "/usr/lib/python2.7/site-packages/ranger/gui/ui.py", line 92, in suspend
:    curses.nocbreak()
:error: nocbreak() returned ERR
:
:Local variables in innermost frame:
:self: <ranger.gui.defaultui.DefaultUI object at 0x2306090>
Comment 1 Patrick Ooooeee 2012-11-25 19:03:47 UTC 
Created attachment 651610 [details]
File: executable
Comment 2 Patrick Ooooeee 2012-11-25 19:03:49 UTC 
Created attachment 651611 [details]
File: environ
Comment 3 Patrick Ooooeee 2012-11-25 19:03:52 UTC 
Created attachment 651612 [details]
File: smolt_data
Comment 4 Patrick Ooooeee 2012-11-25 19:03:53 UTC 
Created attachment 651613 [details]
File: core_backtrace
Comment 5 Fedora End Of Life 2013-07-04 00:09:49 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 6 Fedora End Of Life 2013-08-01 03:35:40 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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