Great. It seems to be back to normal.
Awesome work debian devs.
On Fri, Feb 12, 2021 at 2:12 AM Unit 193 wrote:
> Howdy,
>
> I just tried the glib2.0 2.66.7-1 which was just uploaded and it fixed the
> problem for me. Can you give it a try and see if you can confirm this?
>
>
> Thanks!
>
>
Howdy,
I just tried the glib2.0 2.66.7-1 which was just uploaded and it fixed the
problem for me. Can you give it a try and see if you can confirm this?
Thanks!
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
On Sun, 7 Feb 2021, Gökalp Çelik wrote:
I tested with 2.66.4 package from bullseye
* Gökalp Çelik [2021-02-10 15:50]:
> I tested with 2.66.4 package from bullseye and package-update-indicator
> came back however those older packages also suffer from a vulnerability
> that later sid packages don't. So it seems that there is a problem with
> package-update-indicator
I tested with 2.66.4 package from bullseye and package-update-indicator
came back however those older packages also suffer from a vulnerability
that later sid packages don't. So it seems that there is a problem with
package-update-indicator implementation as well.
On Sun, Feb 7, 2021 at 1:15 AM
Howdy,
The exact error message seen is:
GLib-ERROR **: 17:08:39.264: ../../../glib/gmem.c:112: failed to allocate
93955162462643 bytes
This actually started happening with an update of glib2.0 to 2.66.6-1, though
2.67.3-1 is also affected. To work around such problem, I have downgraded the
Package: package-update-indicator
Version: package-update-indicator 7
package-update-indicator stopped working under debian sid 2 days ago. When
I tried to launch it from command line this error message is thrown.
❯ package-update-indicator
(package-update-indicator:4430): GLib-ERROR **:
6 matches
Mail list logo
