I had this problem, and it turned out that the gconf key mentioned by
ivan90112 and paalfe was set to false, and changing it fixed the
problem.
Is there any reason to disable the touchpad (apparently) by default?
--
[10.04] Touchpad stops working after login
https://bugs.launchpad.net/bugs/54972
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 numbers
** 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: "up
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 in
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 updat
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 a
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 t
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
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,
>
> e
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 number
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 HWE)
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
Titl
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,
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,
>
> Yes, the cache file is
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, v
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! go
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 di
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 <1604...@bugs.launchpad.net> wrote:
>
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 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 myself and some apt
> cmds
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 stable yet, but should be so
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 at
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 t
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 Ubuntu
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"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5045005/+files/updates_available.p
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 o
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 pa
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 compl
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 sta
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
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(): /var/lib/apt/
@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
@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 upd
@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 upd
@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 new
I too have this problem. XRDP Worked fine with 11.04, and now that I
have upgraded I can only see either the back ground, or a cut down
version of some windows, but I am unable to move them. All very strange!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
36 matches
Mail list logo
