Bug#954207: getting gtk3 warnings of glib version too old after update
at bottom :-
On 18/03/2020, Changwoo Ryu <cwryu@debian.org> wrote:
> Hi,
>
> 2020년 3월 18일 (수) 오후 11:24, shirish शिरीष <shirishag75@gmail.com>님이 작성:
>>
>> Package: ibus-gtk3
>> Version: 1.5.22-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> I am getting the following GTK3 warnings while running any gtk3 aware
>> app.
>>
>> (gedit:255189): Gtk-WARNING **: 19:47:32.240: GModule
>> (/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so)
>> initialization check failed: GLib version too old (micro mismatch)
>
> I don't see this warning message. This happens when your glib version
> is older than the version which ibus-gtk3 was built with. It's a
> typical compatibility check.
>
>> Could you please look into the above and fix it. I am not sure which
>> glib version to report it too if it pertains to that, whether
>> libglib2.0-0 2.62.5-1 or something else.
>
> According to buildd.d.o, ibus-gtk3:amd64 1.5.22-1 has been built with
> glib 2.64.1-1. It shouldn't print such warning with glib 2.62.5-1.
>
> Please make sure if you were really running ibus 1.5.22-1 and glib
> 2.62.5-1.
>
>> -- System Information:
>> Debian Release: bullseye/sid
>> APT prefers testing
>> APT policy: (900, 'testing'), (500, 'testing-debug'), (100,
>> 'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50,
>> 'experimental-debug')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
>> (charmap=UTF-8)
>> Shell: /bin/sh linked to /usr/bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages ibus-gtk3 depends on:
>> ii libc6 2.30-2
>> ii libglib2.0-0 2.62.5-1
>> ii libgtk-3-0 3.24.14-1
>> ii libibus-1.0-5 1.5.22-1
>> ii libpango-1.0-0 1.42.4-8
>>
>
Dear Changwoo,
Here are the details you needed -
$ apt-cache policy ibus-gtk3
ibus-gtk3:
Installed: 1.5.22-1
Candidate: 1.5.22-1
Version table:
*** 1.5.22-1 900
900 http://deb.debian.org/debian testing/main amd64 Packages
100 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy libglib2.0-0
libglib2.0-0:
Installed: 2.62.5-1
Candidate: 2.62.5-1
Version table:
2.64.1-1 100
100 http://deb.debian.org/debian unstable/main amd64 Packages
*** 2.62.5-1 900
900 http://deb.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
I hope and guess that this will go away when libglib2.0-0 2.64.1-1
migrates to testing. I am going to wait the necessary 2-3 days it will
take for the new version of libglib2.0-0 to migrate by itself.
Ideally, it should have put the package back or in non-upgradable, not
installable mode till libglib2.0-0 2.64.1-1 doesn't migrate over.
It is more annonyance rather than anything else but could have issues
with genuine users of the package.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
Reply to: