@jokrebel
As far as I can tell, nothing has been updated in 5.118 to address the updates available issue. See https://github.com/dustinkirkland/byobu/blob/master/usr/lib/byobu/updates_available#L86
I would not expect the latest version to fix this.
Can you try clearing the byobu cache related to the updates available and then test my proposed fix in updates_available? https://github.com/jksinton/byobu/blob/master/usr/lib/byobu/updates_available#L90
As I mentioned above, you can clear the cache for screen implementations using commands similar to this:
rm /dev/shm/byobu-<user>-<XXXXXXXX>/cache.screen/updates-available rm /dev/shm/byobu-<user>-<XXXXXXXX>/cache.screen/updates-available.lock
If you don't feel comfortable deleting the cache, just rename the files (e.g., mv updates-available updates-available.bak).
Use this command to find your particular cache files: find /dev/shm -name 'updates-available*'
@jokrebel
As far as I can tell, nothing has been updated in 5.118 to address the updates available issue. See https:/ /github. com/dustinkirkl and/byobu/ blob/master/ usr/lib/ byobu/updates_ available# L86
I would not expect the latest version to fix this.
Can you try clearing the byobu cache related to the updates available and then test my proposed fix in updates_available? /github. com/jksinton/ byobu/blob/ master/ usr/lib/ byobu/updates_ available# L90
https:/
As I mentioned above, you can clear the cache for screen implementations using commands similar to this:
rm /dev/shm/ byobu-< user>-< XXXXXXXX> /cache. screen/ updates- available byobu-< user>-< XXXXXXXX> /cache. screen/ updates- available. lock
rm /dev/shm/
If you don't feel comfortable deleting the cache, just rename the files (e.g., mv updates-available updates- available. bak).
Use this command to find your particular cache files: available* '
find /dev/shm -name 'updates-