Your message dated Tue, 8 Aug 2023 10:12:15 +0100
with message-id <ZNIG7/[email protected]>
and subject line Re: Bug#1043000: libgtk-3-0: segfault if wayland compositor
does not support xdg_activation_v1
has caused the Debian Bug report #1043000,
regarding libgtk-3-0: segfault if wayland compositor does not support
xdg_activation_v1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1043000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043000
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgtk-3-0
Version: 3.24.37-2
Severity: important
Tags: upstream
X-Debbugs-Cc: [email protected]
Dear Maintainer,
On bookworm, when using a Wayland compositor that does not support
xdg_activation_v1, GTK3 applications launched through desktop entries will
immediately segfault.
One such compositor included in Debian is the enlightenment desktop. This issue
is also encountered in other environments, such as when using the "Linux apps"
feature of Chromebooks.
This bug was reported upstream at
https://gitlab.gnome.org/GNOME/gtk/-/issues/5701, and the fix is included in GTK
3.24.38.
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libgtk-3-0 depends on:
ii adwaita-icon-theme 43-1
ii hicolor-icon-theme 0.17-2
ii libatk-bridge2.0-0 2.46.0-5
ii libatk1.0-0 2.46.0-5
ii libc6 2.36-9+deb12u1
ii libcairo-gobject2 1.16.0-7
ii libcairo2 1.16.0-7
ii libcolord2 1.4.6-2.2
ii libcups2 2.4.2-3+deb12u1
ii libepoxy0 1.5.10-1
ii libfontconfig1 2.14.1-4
ii libfribidi0 1.0.8-2.1
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libglib2.0-0 2.74.6-2
ii libgtk-3-common 3.24.37-2
ii libharfbuzz0b 6.0.0+dfsg-3
ii libpango-1.0-0 1.50.12+ds-1
ii libpangocairo-1.0-0 1.50.12+ds-1
ii libpangoft2-1.0-0 1.50.12+ds-1
ii libwayland-client0 1.21.0-1
ii libwayland-cursor0 1.21.0-1
ii libwayland-egl1 1.21.0-1
ii libx11-6 2:1.8.4-2+deb12u1
ii libxcomposite1 1:0.4.5-1
ii libxcursor1 1:1.2.1-1
ii libxdamage1 1:1.1.6-1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2
ii libxi6 2:1.8-1+b1
ii libxinerama1 2:1.1.4-3
ii libxkbcommon0 1.5.0-1
ii libxrandr2 2:1.5.2-2+b1
ii shared-mime-info 2.2-1
Versions of packages libgtk-3-0 recommends:
ii libgtk-3-bin 3.24.37-2
ii librsvg2-common 2.54.5+dfsg-1
Versions of packages libgtk-3-0 suggests:
ii gvfs 1.50.3-1
Versions of packages libgtk-3-0 is related to:
pn appmenu-gtk3-module <none>
pn fcitx-frontend-gtk3 <none>
pn gcin-gtk3-immodule <none>
pn gtk-vector-screenshot <none>
pn gtk3-engines-xfce <none>
pn gtk3-im-libthai <none>
pn hime-gtk3-immodule <none>
ii ibus-gtk3 1.5.27-5
pn imhangul-gtk3 <none>
ii libcanberra-gtk3-module 0.30-10
pn libcaribou-gtk3-module <none>
pn libgtk3-nocsd0 <none>
pn maliit-inputcontext-gtk3 <none>
pn packagekit-gtk3-module <none>
pn scim-gtk-immodule <none>
pn topmenu-gtk3 <none>
pn uim-gtk3 <none>
pn uim-gtk3-immodule <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.24.38-1
On Fri, 04 Aug 2023 at 13:14:56 +1000, James Ye wrote:
> This bug was reported upstream at
> https://gitlab.gnome.org/GNOME/gtk/-/issues/5701, and the fix is included in
> GTK
> 3.24.38.
As a starting point, I'm marking this as fixed in trixie.
This does not fix the bug in bookworm, but the Debian bug tracking system
has version-tracking, so it still knows the status of the bug in bookworm.
I've added this bug to the GNOME team's list of potential fixes to include
in a future bookworm stable update, either as part of 3.24.38 or as an
individual fix (depending what the rest of 3.24.38 looks like).
Thanks,
smcv
--- End Message ---
