Federico Beffa <be...@ieee.org> skribis: > Yes, you are right. Yesterday I was messing around with the environment > variable GTK_MODULE. I guess that confused me. Having undefined it now I > only see reference to gtk-3:
Good. > In the mean time I've found out the existence of a simple test program > called canberra-gtk-play in the libcanberra package. With this I tested > that I can actually play a sound, but it gives the same message: > > $ canberra-gtk-play -i phone-incoming-call > Gtk-Message: Failed to load module "canberra-gtk-module" Here, on the stand-alone system, it simply fails with: --8<---------------cut here---------------start------------->8--- $ /gnu/store/nlm81g8hgsw7d01la14zjycjcgamn4qp-libcanberra-0.30/bin/canberra-gtk-play -i phone-incoming-call Failed to play sound: File or data not found --8<---------------cut here---------------end--------------->8--- Do you know where those audio samples normally come from? We seem to miss that package. I tried gnubg and pavucontrol, which both use libcanberra, but none of them tries to load canberra-gtk-module.so. Could it be something that appears in your machine’s /etc/gtk config files or something like that? (As you can see I don’t know much about these GTK+ things.) > So, I've rebuilt emacs without libcanberra, but with gtk-3 with the > attached recipe and now the message is gone: > > $ GTK_PATH=/home/beffa/.guix-profile/lib/gtk-3.0 > /gnu/store/4y7ic831rbawm96qb1n4da19x9qlwk73-emacs-gtk3-24.3/bin/emacs > GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings > will not be saved or shared with other applications. OK. > So my conclusion is: > > Given that libcanberra is built with gtk-3 and emacs builds fine with > gtk-3, I would suggest to change gtk version in the emacs package > (I've also added --with-x-toolkit=gtk3 as flag to configure. Not sure > if this is really necessary). Emacs switched back to GTK+ 2 in commit 8b0275b6, but I forgot why. Andreas, do you remember the reason? Otherwise, I have nothing against upgrading Emacs to GTK+ 3. > In addition, it would be nice not to have to define GTK_PATH. I guess > that would require some modification to either libcanberra or the gtk > package. Sure, we’ll see what it takes exactly. > On a side note, I built a couple of variants of emacs-canberra. After > a while I wanted to check which one is the most recent one with > > $ ls -l /gnu/store/*emacs-canb* > > and have found out that all files in the store have a time stamp of "1 > Jan 1970". Why is guix not producing the expected time stamps? This is done on purpose, to maximize the chances to obtain reproducible behavior, and bit-identical builds. Thanks, Ludo’.