| Summary: | [abrt] iotop: ui.py:452:refresh_display:_curses.error: addwstr() returned ERR | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | bitchecker <ciro.deluca> | ||||||
| Component: | iotop | Assignee: | Adel Gadllah <adel.gadllah> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 24 | CC: | adel.gadllah, ciro.deluca, mhlavink | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/e502a0461c30285b65ca2c04e5415b5ead51c593 | ||||||||
| Whiteboard: | abrt_hash:e30ae6727e54574409b35724fcd5a9fa8e459c82; | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-08 17:28:04 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 1202428 [details]
File: backtrace
Created attachment 1202429 [details]
File: environ
Hi, you've reported several similar abrt crashes. They are all caused by curses module. It does not have proper error codes/messages so it's difficult to say what went wrong. Most often these are false positives. It happens when you run iotop in a terminal and close that terminal. In that case, iotop is still running, it tries to write output to terminal which does not exist and crash is reported. Is it your case too? Did abrt pop up after you've closed the terminal? Or did it really crash? Can you reproduce this problem? (In reply to Michal Hlavinka from comment #3) > Hi, > you've reported several similar abrt crashes. They are all caused by curses > module. It does not have proper error codes/messages so it's difficult to > say what went wrong. Most often these are false positives. It happens when > you run iotop in a terminal and close that terminal. In that case, iotop is > still running, it tries to write output to terminal which does not exist and > crash is reported. Is it your case too? Did abrt pop up after you've closed > the terminal? Or did it really crash? Can you reproduce this problem? no, terminal is running but iotop stop running. yes, abrt notify me that iotop is crashed. Are you able to reproduce this? How long iotop runs before it crashes? What terminal do you use? (In reply to Michal Hlavinka from comment #5) > Are you able to reproduce this? How long iotop runs before it crashes? What > terminal do you use? no, i'm not able to reproduce it at the moment. run time is different, not always the same. i'm using xfce4-terminal with tmux running correctly on top. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. |
Version-Release number of selected component: iotop-0.6-10.fc24 Additional info: reporter: libreport-2.7.2 cmdline: /usr/bin/python3 -s /usr/sbin/iotop --only executable: /usr/sbin/iotop kernel: 4.7.3-200.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: ui.py:452:refresh_display:_curses.error: addwstr() returned ERR Traceback (most recent call last): File "/usr/sbin/iotop", line 17, in <module> main() File "/usr/lib/python3.5/site-packages/iotop/ui.py", line 631, in main main_loop() File "/usr/lib/python3.5/site-packages/iotop/ui.py", line 621, in <lambda> main_loop = lambda: run_iotop(options) File "/usr/lib/python3.5/site-packages/iotop/ui.py", line 508, in run_iotop return curses.wrapper(run_iotop_window, options) File "/usr/lib64/python3.5/curses/__init__.py", line 94, in wrapper return func(stdscr, *args, **kwds) File "/usr/lib/python3.5/site-packages/iotop/ui.py", line 501, in run_iotop_window ui.run() File "/usr/lib/python3.5/site-packages/iotop/ui.py", line 155, in run self.process_list.duration) File "/usr/lib/python3.5/site-packages/iotop/ui.py", line 452, in refresh_display self.win.addstr(i, 0, s[:self.width]) _curses.error: addwstr() returned ERR Local variables in innermost frame: self: <iotop.ui.IOTopUI object at 0x7ff5a3302160> pid: ' TID' titles: [' TID', ' PRIO', ' USER', ' DISK READ', ' DISK WRITE', ' SWAPIN', ' IO', ' COMMAND'] lines: [] s: 'Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 109.12 K/s' i: 1 first_time: False total: (0, 356352) summary: ['Total DISK READ : 0.00 B/s | Total DISK WRITE : 316.46 K/s', 'Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 109.12 K/s'] duration: 1.0996739864349365 actual: (0, 122880)