Red Hat Bugzilla – Bug 1468389
[abrt] iotop: refresh_display(): ui.py:454:refresh_display:_curses.error: wmove() returned ERR
Last modified: 2018-05-29 07:21:48 EDT
Description of problem:
iotop has been running in a tmux session with several open panes
gnome terminal crashed and I had to start it again
when I re attached to the tmux session iotop showed this error message
Version-Release number of selected component:
cmdline: /usr/bin/python3 -s /sbin/iotop -o
runlevel: N 5
ui.py:454:refresh_display:_curses.error: wmove() returned ERR
Traceback (most recent call last):
File "/sbin/iotop", line 17, in <module>
File "/usr/lib/python3.6/site-packages/iotop/ui.py", line 631, in main
File "/usr/lib/python3.6/site-packages/iotop/ui.py", line 621, in <lambda>
main_loop = lambda: run_iotop(options)
File "/usr/lib/python3.6/site-packages/iotop/ui.py", line 508, in run_iotop
return curses.wrapper(run_iotop_window, options)
File "/usr/lib64/python3.6/curses/__init__.py", line 94, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/lib/python3.6/site-packages/iotop/ui.py", line 501, in run_iotop_window
File "/usr/lib/python3.6/site-packages/iotop/ui.py", line 155, in run
File "/usr/lib/python3.6/site-packages/iotop/ui.py", line 454, in refresh_display
_curses.error: wmove() returned ERR
Local variables in innermost frame:
s: 'Actual DISK READ: 47.49 M/s | Actual DISK WRITE: 7.64 M/s'
titles: [' TID', ' PRIO', ' USER', ' DISK READ', ' DISK WRITE', ' SWAPIN', ' IO', ' COMMAND']
pid: ' TID'
actual: (62590976, 10076160)
total: (58257408, 20914176)
summary: ['Total DISK READ : 44.20 M/s | Total DISK WRITE : 15.87 M/s', 'Actual DISK READ: 47.49 M/s | Actual DISK WRITE: 7.64 M/s']
self: <iotop.ui.IOTopUI object at 0x7f5c08428e80>
Potential duplicate: bug 1376111
Created attachment 1295094 [details]
Created attachment 1295095 [details]
Created attachment 1295096 [details]
Created attachment 1295097 [details]
Created attachment 1295098 [details]
Created attachment 1295099 [details]
Created attachment 1295100 [details]
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.