RE: How to handle required plugins and dbus services for GNOME Programs?

[Cook, Malcolm]

> On Thu, Jul 23, 2015 at 8:16 PM, Cook, Malcolm <address@hidden> wrote:
> > Hi,
> >
> > What fortune...
> >
> >> IMO, given that every GLib based program needs it, the right thing to
> >> do is to make it an implicit input of 'glib-or-gtk-build-system'.
> >>
> >> In a similar way, every GLib based program/library makes use of sound
> >> themes. For this to work it needs access to 'libcanberra'. Thus, for
> >> sound themes to work, 'libcanberra' should also be an implicit input
> >> of the build system.
> >>
> >> You may be using a desktop where no sound theme is used/configured
> >> and therefore not be seeing any message about this. But, if you use a
> >> desktop with a sound theme, e.g. GNOME, you will see the following
> >> messages:
> >> Gtk-Message: Failed to load module "canberra-gtk-module"
> >> This is taken care by setting
> >>
> >> GTK_PATH=/gnu/store/...-libcanberra-0.30/lib/gtk-3.0/modules
> >>
> >
> > ... I was at this very moment poised to ask about this very issue here, 
> > for, in
> the case of a fresh guix 0.8.3 I was witnessing:
> >
> > After `guix package --install emacs`, I find:
> >
> >         $ emacs
> >         (process:3941): Gtk-WARNING **: Locale not supported by C library.
> >                 Using the fallback 'C' locale.
> >         Gtk-Message: Failed to load module "canberra-gtk-module"
> >         Gtk-Message: Failed to load module "pk-gtk-module"
> >
> > The installed emacs v 24.5 does still start, and looks pretty snappy 
> > (despite,
> alas, being build without svg support).
> >
> > But, let me try and take your advice:
> >
> >         $ guix package -i libcanberra
> >         $ export GTK_PATH=/gnu/store/*-libcanberra*/lib/gtk-3.0/modules
> >         $ echo $GTK_PATH
> >         /gnu/store/x06vfgf5fn09yr9crqlg22rwc301jnhp-libcanberra-
> 0.30/lib/gtk-3.0/modules
> >         $ ls $GTK_PATH
> >         libcanberra-gtk3-module.la  libcanberra-gtk3-module.so
> > libcanberra-gtk-module.so
> >
> > But, upon starting emacs again, alas, I still get the same Gtk warnings and
> messages.
> >
> > Am I not following your advice, or otherwise mis-understanding it?
> 
> I had a typo, sorry: the path should stop at one level above the modules:
> 
> $GTK_PATH=/gnu/store/nlm81g8hgsw7d01la14zjycjcgamn4qp-libcanberra-
> 0.30/lib/gtk-3.0
> emacs

Thanks, but, I should have reported in the first place that I (guessing) also 
tried GTK_PATH without the final /modules directory as you suggest and got the 
same message.

I also did not report the many other errors encountered during emacs startup, 
including

(emacs-24-5:8483): Gtk-WARNING **: Could not find the icon 'document-new'. The 
'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
        http://icon-theme.freedesktop.org/releases

and others of the flavor

     (emacs-24-5:8483): GLib-GObject-CRITICAL **: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
      (emacs-24-5:8483): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
     (emacs-24-5:8483): Gdk-CRITICAL **: gdk_cairo_surface_create_from_pixbuf: 
assertion 'GDK_IS_PIXBUF (pixbuf)' failed
      (emacs-24-5:8483): Gtk-WARNING **: Error loading theme icon 
'document-new' for stock: Icon 'document-new' not present in theme gnome

Any advice from you or other lurkers much appreciated...


> 
> GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings
> will not be saved or shared with other applications.
> 
> The remaining above message is because of the missing 'dconf' (I guess we
> should add it). I'm not getting the message about "pk-gtk-module".
> I'm not sure what it refers to.

Apparently something called packageKit per 
https://bugzilla.redhat.com/show_bug.cgi?id=643129

> 
> HTH,

Thx, a bit,

!Malcolm

> Fede