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

Package:
blueman
Source:
blueman
Description:
Graphical bluetooth manager
Submitter:
Marc Lehmann
Date:
2023-06-02 13:45:02 UTC
Severity:
normal
#1037023#5
Date:
2023-06-01 20:52:53 UTC
From:
To:
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"                          |

#1037023#10
Date:
2023-06-02 07:30:13 UTC
From:
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

#1037023#15
Date:
2023-06-02 12:36:46 UTC
From:
To:
Interesting - probably some action at a distance thing then. Weird that
only blueman did output this message, though.

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

#1037023#20
Date:
2023-06-02 13:42:29 UTC
From:
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.