GNOME Bugzilla – Bug 770886
Launching attachments not working under Flatpak
Last modified: 2017-11-15 00:23:23 UTC
Currently, when Geary is packaged for Flatpak, neither launching attachments nor View Source works. The work for Bug 765516 will switch Geary to using GAppInfo for launching attachments, which may or may not help. Either way, the View Source mechanism of creating a temp file and calling Gtk.show_uri() with a file:// URI may need to change.
Fix for attachments not being launched pushed master as commit ca3452b. The view source part is different, and maybe a Flatpak bug, so has been spun off as Bug 779311.
I've tried Geary 0.12 under Centos 7's version of Flatpak on GNOME 3.22.x and it insta-crashed everytime I would try to open an attachment, like so: Gtk-Message: Failed to load module "pk-gtk-module" Gtk-Message: Failed to load module "pk-gtk-module" *** Error in `geary': double free or corruption (fasttop): 0x00007f2af4003f40 *** ======= Backtrace: ========= /lib/libc.so.6[0x3b0a270c4b] /lib/libc.so.6[0x3b0a277026] /lib/libc.so.6[0x3b0a27781e] /lib/libglib-2.0.so.0(+0x47481)[0x7f2b12c54481] /lib/libglib-2.0.so.0(g_main_context_dispatch+0x2d0)[0x7f2b12c57450] /lib/libglib-2.0.so.0(+0x4a698)[0x7f2b12c57698] /lib/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f2b12c5774c] /lib/libgio-2.0.so.0(g_application_run+0x20d)[0x7f2b1465897d] geary(_vala_main+0x53)[0x46da03] /lib/libc.so.6(__libc_start_main+0xf1)[0x3b0a220291] geary(_start+0x2a)[0x46d8da] I don't understand why this is marked as fixed given the version number, or was it a partial fix depending on bug #779311 to work in practice?
Hey Jean-François, thanks for reporting this. (In reply to Jean-François Fortin Tam from comment #2) > I've tried Geary 0.12 under Centos 7's version of Flatpak on GNOME 3.22.x > and it insta-crashed everytime I would try to open an attachment, like so: Can you please install the Flatpak debug runtimes (org.gnome.Geary.Debug, org.gnome.Sdk.Debug and org.freedesktop.Sdk.Debug) for this to get a backtrace with symbol names, and lodge a new bug with the updated trace? > I don't understand why this is marked as fixed given the version number, or > was it a partial fix depending on bug #779311 to work in practice? The commit referenced above fixed the issue on my system (hence being resolved as fixed), and was included in the Geary 0.12 release (as indicated by the target milestone field above). Yours is the first report of an issue with this since that was released, so it would be good to open a new bug to track whatever the issues is down and fix it.