** Description changed: To recreate: * I'm running Ubuntu Server 16.04.1 LTS (no GUI). * I'm using byobu `5.106-0ubuntu1`. * I press F1, then enable the "disk_io" notification, then choose "Apply". * While doing nothing at the command prompt, I watch the status line. What I expected to happen: * I expected Byobu disk_io report to fluctuate in obvious (or at least believable) ways corresponding to my activity on the system. What I found to happen: * Byobu's reports of disk_io did not correspond to the commands I was typing, nor reports from `iotop`. - Here are two examples: + Notes: - * Example 1: On my system, "->372kB/s" (disk writing) remains on the - status bar for an extended period. + * I am using a freshly installed system. + * I don't have many other processing running. I installed PostgreSQL, OpenSSH, and basic development tools. - My system is freshly installed, so I would be quite surprised if that - exact amount of disk IO is happening for an extended period. + For example, typing `dd -h` results in "<-72kB/s" (disk reading) + remaining on the status bar for an extended period. I've waited for what + seems to be several minutes but the status is not cleared. - * Example 2: On my system, "<-912kB/s" (disk reading) remains on the - status bar for an extended period. + I would be quite surprised if that exact amount of disk IO is happening + for an extended period. I ran `iotop` to see what processes might be causing an ongoing disk activity. Nothing seemed to correspond. Theory / Possible Explanation: * It would appear that when disk activity changes from a non-zero value to zero, the previous value is not cleared out. * This could be a simple matter of the TUI (text user interface) having a stale output, perhaps due to a rendering bug.
** Description changed: To recreate: * I'm running Ubuntu Server 16.04.1 LTS (no GUI). * I'm using byobu `5.106-0ubuntu1`. - * I press F1, then enable the "disk_io" notification, then choose "Apply". - * While doing nothing at the command prompt, I watch the status line. + * I pressed F1, then enable the "disk_io" notification, then choose "Apply". + * I did various things on the command line. For example, I did nothing for several minutes. Then I ran `dd -h` at the command prompt. All the while, I watched the status line. What I expected to happen: * I expected Byobu disk_io report to fluctuate in obvious (or at least believable) ways corresponding to my activity on the system. What I found to happen: * Byobu's reports of disk_io did not correspond to the commands I was typing, nor reports from `iotop`. + * In particular, running `dd -h` resulted in "<-72kB/s" (disk reading) + remaining on the status bar for an extended period. I waited for what + seems to be several minutes but the status is not cleared. I would be + quite surprised if that exact amount of disk IO is happening for an + extended period. I ran `iotop` to see what processes might be causing an + ongoing disk activity. Nothing seemed to correspond. + Notes: * I am using a freshly installed system. * I don't have many other processing running. I installed PostgreSQL, OpenSSH, and basic development tools. - For example, typing `dd -h` results in "<-72kB/s" (disk reading) - remaining on the status bar for an extended period. I've waited for what - seems to be several minutes but the status is not cleared. - - I would be quite surprised if that exact amount of disk IO is happening - for an extended period. - - I ran `iotop` to see what processes might be causing an ongoing disk - activity. Nothing seemed to correspond. - Theory / Possible Explanation: * It would appear that when disk activity changes from a non-zero value to zero, the previous value is not cleared out. * This could be a simple matter of the TUI (text user interface) having a stale output, perhaps due to a rendering bug. ** Description changed: To recreate: * I'm running Ubuntu Server 16.04.1 LTS (no GUI). * I'm using byobu `5.106-0ubuntu1`. * I pressed F1, then enable the "disk_io" notification, then choose "Apply". * I did various things on the command line. For example, I did nothing for several minutes. Then I ran `dd -h` at the command prompt. All the while, I watched the status line. What I expected to happen: * I expected Byobu disk_io report to fluctuate in obvious (or at least believable) ways corresponding to my activity on the system. What I found to happen: * Byobu's reports of disk_io did not correspond to the commands I was typing, nor reports from `iotop`. * In particular, running `dd -h` resulted in "<-72kB/s" (disk reading) remaining on the status bar for an extended period. I waited for what - seems to be several minutes but the status is not cleared. I would be + seems to be several minutes but the status was not cleared. I would be quite surprised if that exact amount of disk IO is happening for an extended period. I ran `iotop` to see what processes might be causing an ongoing disk activity. Nothing seemed to correspond. Notes: * I am using a freshly installed system. * I don't have many other processing running. I installed PostgreSQL, OpenSSH, and basic development tools. Theory / Possible Explanation: * It would appear that when disk activity changes from a non-zero value to zero, the previous value is not cleared out. * This could be a simple matter of the TUI (text user interface) having a stale output, perhaps due to a rendering bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626218 Title: Stale status notification for disk_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1626218/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
