5.126 is in cosmic, marking this bug as fix released.
** Changed in: byobu (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not
5.126 is in cosmic, marking this bug as fix released.
** Changed in: byobu (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
It was merged and will appear in byobu 5.126
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after updates
To manage notifications about this bug go
Hi,
Awesome. I submitted a pull request for this on GitHub:
https://github.com/dustinkirkland/byobu/pull/26
Perhaps Dustin will see it and use it, or make another fix/change in his
own words.
thx so much for byobu and everyone's help,
-mark
--
You received this bug notification because you
All fine ;-) since I put in the update_available from #73 into my
/usr/lib/byobu the problem seems ti be fixed (at that system i have done
that ;-)
greate Work! And release it to all you can do as quick as possible.
For now is si noct even in Debian Sid i think
best regards
jokrebel
--
You
Hi,
I have not seen the problem for a while now.
Is it still ok with you ?
take care,
-mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after
Hi and thanks; great work!
didn't occur for about 20 updates till now. Looks fine :-)
best regards
Achim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update
Hi and thanks; great work!
didn't occur for about 20 updates till now. Looks fine :-)
[the "updates_available" from post #73 seems to do the best job]
best regards
Achim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Any update ? I have not had the problem now for about a month.
I hope its ok with you also ?
-mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update
...just for now a status report:
worked fine for 10 updates - no fault :-)... I hope it stays that
way
thanks for the work
jokrebel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
OK - then the next try with #73 file
the one before (you deleted it?) worked for 7 times and failed just
today at the 8th try/update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Hi,
Attached is another update. This one adds an additional time check to run the
update_cache once an hour. Save it to /usr/lib/byobu/updates_available, and
make sure it is executable, just like before.
a). cd /usr/lib/byobu
b). cp/save the new updates_available file you downloaded
** Attachment removed: "updates_available"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5043276/+files/updates_available
** Attachment removed: "updates_available"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5043277/+files/updates_available
** Patch removed:
ok, attached is a new, complete updates_available script. Save it to
/usr/lib/byobu/updates_available, and make sure it is executable, just like
before.
a). cd /usr/lib/byobu
b). cp/save the new updates_available file you downloaded into this dir
c). sudo chmod 755 updates_available
Hi,
I've got a fix :-)
Let me test it more tomorrow and then I'll post a new updates_available
script
-mark
On Sat, Feb 10, 2018 at 9:00 AM M Kelly wrote:
> Hi,
>
> Yes it helped thanks. Thinking on it.
>
> -mark
>
> On Sat, Feb 10, 2018, 8:54 AM jokrebel
Hi,
Yes it helped thanks. Thinking on it.
-mark
On Sat, Feb 10, 2018, 8:54 AM jokrebel <1604...@bugs.launchpad.net>
wrote:
> Just confirmed the same issue at an other machine with actual siduction
>
> after "update && full-upgrade" still got red "93!" in the byobu panel
>
> update once more
Just confirmed the same issue at an other machine with actual siduction
after "update && full-upgrade" still got red "93!" in the byobu panel
update once more did not clear it.
"cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available" tells "93"
hope to help for findig the problem
--
You
Yes, you are right i think (my english is not so good)
1) there was a red 7!! in the bottom line
2) I checked "cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available" and
got "7 1"
3) did "sudo apt update && sudo apt full-upgrade && sudo apt autoremove" (apt
tells all 0)
4) waited a few
Hi,
Just to be complete, for example, my system shows a 4! in red this morning.
My cache file shows 4 1
I do an:
sudo apt-get update
sudo apt-get upgrade
and then for about 5 seconds my cache file still shows 4 1 and the red 4!,
but after 5 seconds it automatically changes to 0 0 and the Red 4!
good morning,
thanks for your detailed explanation.
It just occured again. Before and also afterwards i got a 7 1 after
using
cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
have a nice day
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
I would just cat that file, as in:
cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
On my system this is what it I do:
% cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
0 0
So I can see the file has just "0 0" in it at this moment.
You could also use less, more, nano,
Hi Mark,
yes - there is a file /usr/lib/update-notifier/apt-check
but where/how to check the cache file when it will occur next time i got
no idea with your line
$BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
The most used computer over mosh/ssh with byobu and exclusively updated
over
Hi,
Can you verify you have this file ?
/usr/lib/update-notifier/apt-check
The extra logic I added was only for when this file is on your system and I
just want to confirm if this is true for you.
thanks,
-mark
On Mon, Feb 5, 2018 at 7:31 PM M Kelly wrote:
> Hi,
>
>
Hi,
Yes, the cache file is at:
$BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
-mark
On Mon, Feb 5, 2018 at 1:29 AM jokrebel <1604...@bugs.launchpad.net>
wrote:
> Hi again,
>
> "Next time it happens, before you issue the --reinstall command, can you
> check the cache file and tell me if
Hi again,
"Next time it happens, before you issue the --reinstall command, can you
check the cache file and tell me if it has the 2 2 (or whatever the
number your status shows) or a 0 0 in it ?"
of cause i will do, but can you tell me exactly the name of the file and
the path where to find?
Hi,
It's ok - I learned something from this and I will keep going and
eventually solve :-)
Next time it happens, before you issue the --reinstall command, can you
check the cache file and tell
me if it has the 2 2 (or whatever the number your status shows) or a 0 0 in
it ?
I want to see if the
Sorry, bad news
after 3 updates where the counter went away immediately the 4th failed
:-(
There is still a red " 6!" after 2 "sudo apt update& apt full-
upgrade& apt autoremove" that tells "0 aktualisiert, 0 neu
installiert, 0 zu entfernen und 0 nicht aktualisiert."
After doing a "sudo apt
Thanks again for your time :-)
yes, I did some modifications (see the older posts from me in this
thread since May 2017) hoping to get a fix for the problem which is only
sometimes occurring!
for now i put Your
1.) updates_available file from #50 into /usr/lib/byobu (after backuo the old)
and
Hi,
The patch method expects the updates_available file is in its original
condition and to be the same as mine. Have you modified it before this or
perhaps its older or from a different version of byobu/Ubuntu ? If so that is
probably the reason it failed.
Which is why I also posted the
Hello again,
tryed Way 2 but got:
sudo patch < updates_available.patch
patching file updates_available
Hunk #1 FAILED at 50.
Hunk #2 FAILED at 85.
2 out of 2 hunks FAILED -- saving rejects to file updates_available.rej
:/
--
You received this bug notification because you are a member of
Hi.
Either of 1). or 2) will do it -
1). save complete updates_available file in post #50 then do:
a). cd /usr/lib/byobu
b). sudo cp updates_available updates_available.orig
c). save the new updates_available file from post #50 here
d). sudo chmod 755 updates_available
or using
Sorry for a noob question. I have no idea how to use that
"updates_available.patch" out of post #52 - for me that file is only a
cryptical unreadable (maybe) code. Would be nice to get a guide how and
where to place/add/whatever
thanks a lot for your work again
--
You received this bug
The attachment "updates_available.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Scratch, that, previous upload was a just diff file, here is a correct patch
file:
thx
** Patch added: "updates_available.patch"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5045007/+files/updates_available.patch
--
You received this bug notification because you are a member
I also uploaded a patch file for this if that is easier to apply
Just curious if the small difference in update method and time window solves
the problem.
thx
** Patch added: "updates_available.patch"
I attached my modified updates_available file here.
** Attachment added: "updates_available"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5043277/+files/updates_available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
If you want/can, can you try this version of the updates_available script ?
It is attached, and it goes in file: /usr/lib/byobu/updates_available
Just save the existing file as .orig or something and put this new one
there, making sure it is chmod 755 executable.
I am assuming your dist goes
Hi,
Yes, good idea, thanks for that info.
-mark
On Thu, Jan 25, 2018 at 1:05 PM bsy wrote:
> for apt, why not use something like apt list --upgradeable | wc -l to
> determine whether updates are needed / the number of upgradeable
> packages? apt list output is not
Hi,
Q: when the status bar incorrectly shows 2! (or whatever the count is) when
you know there are no more updates to do, does your updates-available cache
file show "2 2" or "0 0" ?
The cache file is located in:
BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
-mark
On Fri, Jan 19, 2018
for apt, why not use something like apt list --upgradeable | wc -l to
determine whether updates are needed / the number of upgradeable
packages? apt list output is not stable yet, but should be soon, one
hopes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi,
I think the easiest work-around is to remove the cache file -
rm -f $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
-mark
On Sun, Jan 7, 2018 at 8:54 AM M Kelly wrote:
> Hi,
>
> Happy New Year to you.
> Yes, thx, I agree, I have seen it happen a few times
Hi,
Happy New Year to you.
Yes, thx, I agree, I have seen it happen a few times myself and some apt
cmds get it to resolve.
If I find some time I will try to look at it more, it is annoying.
take care,
On Sun, Jan 7, 2018 at 4:55 AM jokrebel <1604...@bugs.launchpad.net>
wrote:
> Hi again,
>
>
Hi again,
error still happens on different distros randomly. The workaround to wait some
time after
"apt update && apt full-upgrade"
bevor pressing "y" (for getting it go) works mostly but also not allways.
If not; my dirty workaround for the workaround *urks* if the red "!xy"
notfication
** Changed in: byobu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after updates
To manage
Hi,
Thanks. I have had it happen only two times in a few months after that
patch fix, so like you it still happens but I put up with it and didn't
bother to spend time to fix for sure.
But yes it is a 'timing' issue and the script should do something like loop
and re-check for when dpkg.log does
Hello again,
since I do "sudo apt update && sudo apt full-upgrade && sudo apt
autoremove" and then first wait at least 1 minute _before_ I press the
"y" for start it, the bug did no more occur for me.
Not a solution - but a workaround ;-)
HTH
jokrebel
--
You received this bug notification
With the proposed fix, today my status bar showed a 1! and after an
update && upgrade, for the first time in a while the 1! is still
present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
@mckub1 I've been running the proposed fix for Ubuntu for about 7 months
now. I've only seen it fail to update the updates_available value once
during an upgrade. The failure with the proposed fix was running under a
virtual instance of Ubuntu on my MacBook Pro (13-inch, Late 2016), which
screamed
After a few weeks of use, I have to say the fix -
[ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt
"$mycache" ] || [ "/var/log/dpkg.log" -nt "$mycache" ]
to the /usr/lib/byobu/updates_available script has worked well for me on two
different systems (both Ubuntu 16.04 with
PS - I set my status interval with a setting in my ~/.byobu/.tmux.conf
file -
set -g status-interval 10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update
[Update] just occured on a third not quite as old computer (core2) with a
siduction64 linux.
3 times update/full-upgrade did not clear the wrong "214!" (had to be "0" after
the first time). It cleared after starting "apt autoremove"
--
You received this bug notification because you are a
@mckub1
Hi once more,
first thanks a lot for your interest on my problem. After some new
updates on several installations now i can tell some more.
i never changed the setting of the interval (don't even know where i
could). Think it should be something between 1 an 3 seconds (looks
like).
On
@jokrebel, hi
What is your status-interval set to (how many seconds between status bar
updates) ?
When you still have a red 3! (or whatever the number) after an upgrade - can
you press the F5 key a few times to see if the red 3! update goes away ?
The additional check for if the cache file is
@mckub1 thanks once mor for your time. Yes there is a file:
lrwxrwxrwx 1 root root12 Mär 28 00:36 apt-check -> apt_check.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu
@jokrebel, hi
Just to confirm, do you have this file on your system ?
/usr/lib/update-notifier/apt-check
-thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing
@jokrebel, hi
ok, sorry. I will post another patch soon and we can see if that helps fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after
Hi once more,
in the /usr/lib/byobu/updates_available? I did this some days bevor.
I posted this in #15 an #16 but it solved the problem not.
It still occurs from time to time (not always)
but nevertheless thanks for your time
--
You received this bug notification because you are a
@jokrebel, hi
The patch I used is this: (changing one line)
# orig:
# [ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt
"$mycache" ]
# new:
[ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt
"$mycache" ] || [ "/var/log/dpkg.log" -nt "$mycache" ]
So far
[UPDATE] ...after about 10 more "sudo apt update& apt full
upgrade&& full-upgrade& apt autoremove" the red number is gone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not
Hi all,
just had the same temporarily problem occured at a ubuntu 17.10.
After "sudo apt update& apt full upgrade&& full-upgrade& apt
autoremove"
byobu statusline shows me "53!" in red.
Same line called several more times tells me "... 0 nicht aktualisiert" but the
red number does not
Maybe this dbg output from updates_available helps reveal the issue:
___update_needed() entr 2017-04-19 17:57:22:332517641
___update_needed(): mycache= 2017-04-19 17:56:55:299087230
___update_needed(): /var/lib/apt = 2017-04-19 17:57:20:275457556
___update_needed():
I will confirm this happens to me sometimes also on 16.04 on several different
machines.
I have debugged as well and will also confirm it has to do with the file dates
and how long an update takes, so it is not easily reproducible. But the logic
flow shows how it can happen.
I have patched the
Thanks a lot for the time you all spent to try reproduce it.
it's not allways (not after each update that is aviailiable).
And yes, on other Ubuntu installations i own it has never happend to me too.
I have no idea what's going wrong with that 1 installation.
May be i get time and install the
Hi @jokrebel --
I've also tried this on ubuntu Xenial and can't reproduce. Seems like
it might be flaky for you. Until it gets clear reproduction steps in
ubuntu, I'll mark it as incomplete. This is not saying it's not a
problem, just that it lacks a clear way to reproduce (thus lacks a clear
@jksinton
I went back to byobu version 5.106 with tmux 2.1 and than tried your
tip:
changed line 88 (as i tested before) into:
[ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt "$mycache" ] ||
[ "/var/log/dpkg.log" -nt "$mycache" ]
and deleted
I just tried today on a xenial long-running container that I have and
there was one update available: vlan. byobu correctly flagged it with a
red "1!" in the status bar after a few seconds.
I then upgraded (dist-upgrade), and a few seconds later (less than 10)
then "1!" disappeared.
byobu
I just tried today on a xenial long-running container that I have and
there was one update available: vlan. byobu correctly flagged it with a
red "1!" in the status bar after a few seconds.
I then upgraded (dist-upgrade), and a few seconds later (less than 10)
then "1!" disappeared.
byobu
@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
Sorry. No good news. With byobu version 5.118 the problem still exists.
Just did 3 Updates. Now I have:
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
but in byobu still there is the red backgrounded "3!"
:-(
just trying with the PPA "sudo add-apt-repository ppa:byobu/ppa"
byobu -v
byobu version 5.118
tmux 2.1
...hope will do a better job at update notification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[UPDATE:] ...sorry - seems not to work proper. (Or be the wrong
workaround)
...after a few times it worked...
Just did 3 Updates, but the red "3!" for "Updates available" still in
the bottom line :-(
Did update/full-upgrade for 3 more times. No Updates to do! But Byobu
still claims it.
Any
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: byobu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
** Package changed: ubuntu => byobu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after updates
To manage notifications about this bug go
73 matches
Mail list logo