OK, I have a temp and very ugly workaround in mind, but first a summary of the situation. But I am pretty sure tomboy-ng would not open the gtk3 ones. Open("/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so", O_RDONLY|O_CLOEXEC) = 4īut, again, your GTK3 one will be different. I ran an strace on it and it appears that on my system, canberra is searched for, found and opened. Or I send you a binary with a whole lot of debug stuff. If we don't make any progress, I'll need to bring up a VM with U18.04 and see what we get there. I did test against other GTK3 systems but not for awhile. But the widget set targets GTK2 so, the issue might be that your GTK3 system does not have the GTK2 stuff it should have. If you are running mainstream Ubuntu, its GTK3. usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libcanberra-gtk3-module.so usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libcanberra-gtk-module.so usr/lib/x86_64-linux-gnu/libcanberra-0.30/libcanberra-pulse.so usr/lib/x86_64-linux-gnu/libcanberra-0.30/libcanberra-alsa.so Just in case, as canberra is only hint we have, do make sure it is installed, in my case, I can find it like this (slow but positive). So, tomboy-ng keeps running at that stage ? Yes, it looks to me that the message about canberra is just a GTK warning, I take it if you start tomboy without the '&' at the end, you don't get a command prompt back ? (until, eg, you do ctrl C).