Hi Jack: Am 31.01.19 21:19 schrieb(en) Jack via balsa-list:
Sorry to be contrary again, but it works fine for me. Could be a build difference? Is there somewhere to look at installed files, or is this only during build time?
Hmmm, strange… I tried on two clean (mostely) VM's (with Debian Jessie and Stretch), both using the master branch as of commit 03bf588a429818baf3a4bfc989a09256fd2da37f, and I can reproduce the effect on *both* machines. E.g. on Jessie: test@debian:~/balsa$ ls -al $(which balsa-ab) -rwxr-xr-x 1 root staff 337520 Jan 31 21:34 /usr/local/bin/balsa-ab test@debian:~/balsa$ /usr/local/bin/balsa-ab get_main_menu error: The resource at '/org/desktop/BalsaAb/ab-main.ui' does not exist Speicherzugriffsfehler test@debian:~/balsa$ ./src/balsa-ab get_main_menu error: The resource at '/org/desktop/BalsaAb/ab-main.ui' does not exist Speicherzugriffsfehler Running from the Balsa menu works fine on both. Are you sure there is no other copy of balsa-ab (from a package, old build, …) installed? Again on the VM: test@debian:~/balsa$ sudo locate balsa-ab /home/test/balsa/src/balsa-ab /home/test/balsa/src/balsa-ab-resources.c /home/test/balsa/src/balsa-ab-resources.o /home/test/balsa/src/.deps/balsa-ab-resources.Po /home/test/balsa/ui/balsa-ab.gresource.xml /usr/local/bin/balsa-ab Or maybe a special issue with the installed libs? Best, Albrecht.
pgpgTQexWP5UX.pgp
Description: PGP signature
_______________________________________________ balsa-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/balsa-list
