Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1037023: blueman: missing dependency (Failed to load module "xapp-gtk3-module")

293 views
Skip to first unread message

Marc Lehmann

unread,
Jun 1, 2023, 5:00:05 PM6/1/23
to
Package: blueman
Version: 2.3.5-2+b1
Severity: normal

Dear Maintainer,

when gir1.2-xapp-1.0 is not installed, bluerman-manager displays the following message and immediately exits:

Gtk-Message: 22:49:13.732: Failed to load module "xapp-gtk3-module" |

-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (990, 'testing-security'), (990, 'testing'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.30-schmorp (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 blueman depends on:
ii adwaita-icon-theme 43-1
ii bluez 5.66-1
ii bluez-obexd 5.66-1
ii dbus 1.14.6-1
ii dbus-user-session [default-dbus-session-bus] 1.14.6-1
ii dbus-x11 [dbus-session-bus] 1.14.6-1
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4
ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii gir1.2-glib-2.0 1.74.0-3
ii gir1.2-gtk-3.0 3.24.37-2
ii gir1.2-nm-1.0 1.42.4-1
ii gir1.2-pango-1.0 1.50.12+ds-1
ii gnome-icon-theme 3.12.0-5
ii libbluetooth3 5.66-1
ii libc6 2.36-9
ii libpulse-mainloop-glib0 16.1+dfsg1-2+b1
ii librsvg2-common 2.54.5+dfsg-1
ii lxqt-notificationd [notification-daemon] 1.2.0-1
ii mate-icon-theme 1.26.0-1
ii mate-notification-daemon [notification-daemon] 1.26.0-1
ii notification-daemon 3.20.0-4+b1
ii plasma-workspace [notification-daemon] 4:5.27.5-2
ii polkitd 122-3
ii python3 3.11.2-1+b1
ii python3-cairo 1.20.1-5+b1
ii python3-gi 3.42.2-3+b1
ii python3-gi-cairo 3.42.2-3+b1
ii xfce4-notifyd [notification-daemon] 0.7.3-1

Versions of packages blueman recommends:
ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1

blueman suggests no packages.

-- no debconf information

Christopher Schramm

unread,
Jun 2, 2023, 4:20:04 AM6/2/23
to
Hi Marc,

blueman-manager works fine for me without that package and blueman does
not have anything to do with xapp.

Could it be that you're referring to the module in
~/.config/gtk-3.0/settings.ini or similar? Do other GTK 3 apps work fine?

Cheers

Marc Lehmann

unread,
Jun 2, 2023, 9:00:05 AM6/2/23
to
On Fri, Jun 02, 2023 at 09:30:13AM +0200, Christopher Schramm <deb...@cschramm.eu> wrote:
> blueman-manager works fine for me without that package and blueman does not
> have anything to do with xapp.

Interesting - probably some action at a distance thing then. Weird that
only blueman did output this message, though.

> Could it be that you're referring to the module in
> ~/.config/gtk-3.0/settings.ini or similar? Do other GTK 3 apps work fine?

Can't see anything (see below), and other gtk-3 programs (such as
xfce4-panel) did not complain when started similarly (i.e. same terminal
instance).

Here are the contents of ~/.config/gtk-3.0/settings.ini

[Settings]
gtk-cursor-theme-name=breeze_cursors
gtk-font-name=Noto Sans 10
gtk-theme-name=Breeze
gtk-icon-theme-name=breeze
gtk-fallback-icon-theme=gnome
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-menu-images=1
gtk-button-images=1
gtk-primary-button-warps-slider=0
gtk-application-prefer-dark-theme=0

Christopher Schramm

unread,
Jun 2, 2023, 9:50:05 AM6/2/23
to
I can easily reproduce the message e.g. by setting
GTK3_MODULE=xapp-gtk3-module while not having libxapp-gtk3-module
installed. The package's configuration file
/etc/X11/Xsession.d/80xapp-gtk3-module also sets that for the Xsession.

However... i) I can influence the message independent of
gir1.2-xapp-1.0. If it's referenced in $GTK3_MODULE and
libxapp-gtk3-module is installed, the message does not show up even if
gir1.2-xapp-1.0 is not installed. ii) It's harmless. blueman-manager
does not terminate in any way.

Actually, what return code do you get? In case of a crash, could you get
a backtrace? Otherwise, try blueman-manager --loglevel debug to find why
it exits.
0 new messages