AppImageLauncher: Segmentation fault in last continuous build
I installed appimagelauncher_1.0.3-travis495.git20190129.ebfd906.bionic_amd64.deb from the continous build release, and I found the following error when trying to launch an .appimage that I just downloaded. (I also tried it with another appimage program, with identical result). It ends with a Segmentation Fault error.
I use Ubuntu 18.04 amd64, by the way.
user@laptop-TM1703:~/Downloads$ ./digikam-6.0.0-beta3-20181228T114626-x86-64.appimage
(AppImageLauncher:5102): GLib-GIO-CRITICAL **: 14:54:01.480: g_converter_convert: assertion 'outbuf_size > 0' failed
(AppImageLauncher:5102): Gtk-CRITICAL **: 14:54:01.481: Unable to load resource for composite template for type 'GtkDialog': No s'ha pogut descomprimir el recurs «/org/gtk/libgtk/ui/gtkdialog.ui»
(AppImageLauncher:5102): Gtk-CRITICAL **: 14:54:01.481: gtk_widget_class_bind_template_child_full: assertion 'widget_class->priv->template != NULL' failed
(AppImageLauncher:5102): Gtk-CRITICAL **: 14:54:01.481: gtk_widget_class_bind_template_child_full: assertion 'widget_class->priv->template != NULL' failed
(AppImageLauncher:5102): Gtk-CRITICAL **: 14:54:01.481: gtk_widget_class_bind_template_child_full: assertion 'widget_class->priv->template != NULL' failed
(AppImageLauncher:5102): Gtk-CRITICAL **: 14:54:01.481: gtk_widget_class_bind_template_child_full: assertion 'widget_class->priv->template != NULL' failed
(AppImageLauncher:5102): Gtk-CRITICAL **: 14:54:01.481: gtk_widget_class_bind_template_callback_full: assertion 'widget_class->priv->template != NULL' failed
(AppImageLauncher:5102): GLib-CRITICAL **: 14:54:01.980: g_file_test: assertion 'filename != NULL' failed
Violació de segment (s'ha bolcat la memòria)
user@laptop-TM1703:~/Downloads$
I then tried with the release build 1.0.3 and it worked just fine, but I was told to report the bug in case it was a regression. Tell me if you need some help with the error messages, as I see some text in my language.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 49 (29 by maintainers)
We’ve pushed a little fix that should fix the issue permanently. Can you please check if the issue persists?