Debian Bug report logs - #1100576
libadwaita-1-0: Applications based on libadwaita-1-0 do not start

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Thomas Renard <cybaer42@web.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: libadwaita-1-0: Applications based on libadwaita-1-0 do not start

Date: Sat, 15 Mar 2025 16:30:36 +0100

Package: libadwaita-1-0
Version: 1.7~rc-1
Severity: normal

Dear Maintainer,

with version 1.7~rc-1 applications depending on libadwaita-1-0 do not
start anymore.

- start an application, e. g. ptyxis, gnome-control-center,
  gnome-contacts...

expected:

Application starts

actual:

e. g. gnome-contacts:

gnome-contacts: symbol lookup error: /lib/aarch64-linux-gnu/libadwaita-1.so.0: undefined symbol: gtk_widget_set_limit_events

going back to 1.7~beta-2 and every application start

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.13.7-asahi-2-cy8aer0 (SMP w/10 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libadwaita-1-0 depends on:
ii  libappstream5      1.0.4-1
ii  libc6              2.41-4
ii  libfribidi0        1.0.16-1
ii  libglib2.0-0t64    2.84.0-1
ii  libgraphene-1.0-0  1.10.8-5
ii  libgtk-4-1         4.17.5+ds-3
ii  libpango-1.0-0     1.56.1-1

libadwaita-1-0 recommends no packages.
libadwaita-1-0 suggests no packages.

-- no debconf information

Message #10 received at 1100576@bugs.debian.org (full text, mbox, reply):

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Thomas Renard <cybaer42@web.de>, 1100576@bugs.debian.org

Subject: Re: Bug#1100576: libadwaita-1-0: Applications based on libadwaita-1-0 do not start

Date: Sat, 15 Mar 2025 12:37:28 -0400

On Sat, Mar 15, 2025 at 12:15 PM Thomas Renard <cybaer42@web.de> wrote:
> gnome-contacts: symbol lookup error: /lib/aarch64-linux-gnu/libadwaita-1.so.0: undefined symbol: gtk_widget_set_limit_events

Did you build GTK4 locally on your computer a while ago?
libadwaita-1-0 depends on libgtk-4-1 (>= 4.17.5). gtk4 4.17.5
introduced gtk_widget_set_limit_events.

You may have an older version of GTK4 installed to something like
/usr/local/lib/

Thank you,
Jeremy Bícha

Message #15 received at 1100576@bugs.debian.org (full text, mbox, reply):

From: cybaer42@web.de

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1100576@bugs.debian.org

Subject: Re: Bug#1100576: libadwaita-1-0: Applications based on libadwaita-1-0 do not start

Date: Sat, 15 Mar 2025 17:49:55 +0100

Hi Jeremy,

unfortunally- yes. I have some gtk artifact in /usr/local/lib. Deleted 
and worked again. No debian problem, you can close the bug.

Sorry

Thomas

Am 15.03.25 um 17:37 schrieb Jeremy Bícha:
> On Sat, Mar 15, 2025 at 12:15 PM Thomas Renard <cybaer42@web.de> wrote:
>> gnome-contacts: symbol lookup error: /lib/aarch64-linux-gnu/libadwaita-1.so.0: undefined symbol: gtk_widget_set_limit_events
> 
> Did you build GTK4 locally on your computer a while ago?
> libadwaita-1-0 depends on libgtk-4-1 (>= 4.17.5). gtk4 4.17.5
> introduced gtk_widget_set_limit_events.
> 
> You may have an older version of GTK4 installed to something like
> /usr/local/lib/
> 
> Thank you,
> Jeremy Bícha

Message #20 received at 1100576-done@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: 1100576-done@bugs.debian.org

Subject: Re: Bug#1100576: libadwaita-1-0: Applications based on libadwaita-1-0 do not start

Date: Sat, 15 Mar 2025 19:02:43 +0000

On Sat, 15 Mar 2025 at 17:49:55 +0100, cybaer42@web.de wrote:
>Am 15.03.25 um 17:37 schrieb Jeremy Bícha:
>>On Sat, Mar 15, 2025 at 12:15 PM Thomas Renard <cybaer42@web.de> wrote:
>>>gnome-contacts: symbol lookup error: /lib/aarch64-linux-gnu/libadwaita-1.so.0: undefined symbol: gtk_widget_set_limit_events
>>
>>You may have an older version of GTK4 installed to something like
>>/usr/local/lib/

(In my experience, this failure mode nearly always turns out to have 
this as its root cause: Debian's versioned dependency tracking is 
usually good enough to prevent it from happening any other way)

>unfortunally- yes. I have some gtk artifact in /usr/local/lib. Deleted 
>and worked again. No debian problem, you can close the bug.

Thanks, closing the bug.

    smcv

Send a report that this bug log contains spam.