Open ebassi opened 4 years ago
Can you replicate this with the latest code build from source? There have been quite some changes since the 1.9.1 release you use, including GTKD updates. Instead of trying to shove some third party binary RPM of an older release into a Flatpak container I think it would be better to try a source build first and then update the Flatpak to build directly from source.
Instead of trying to shove some third party binary RPM of an older release into a Flatpak container
Ideally, I agree; sadly, this is how Silverblue works at the moment—take the existing distro packages and creating a run time and an application bundle; unless somebody takes Tilix and publishes a Flatpak build on Flathub, of course.
I can test an actual Flatpak build, but it's unlikely I'll be able to run the Tilix build from scratch, as I have no experience of programming in D.
I had tilix working in the fedora flatpak via Silverblue. It dependant on fedora's flatpak repo, and was the only on still running Fedora 33. When I tried to update all my flatpaks it was this app the gave an X11 error. I imagine it would work better if it was running via flathub. Either way, I uninstalled the flatpak and reinstalled it as a rpm-ostree layer.
@phw Related issues : https://github.com/gnunn1/tilix/issues/1997, https://github.com/gnunn1/tilix/issues/2038
It crashes with any version, including 1.9.4 crashes with below:
[📦 com.gexperts.Tilix tilix]$ tilix -v
Versions
Tilix version: 1.9.4
VTE version: 0.66
GTK Version: 3.24.30
Tilix Special Features
(tilix:18): GLib-GObject-WARNING **: 20:10:12.257: invalid (NULL) pointer instance
(tilix:18): GLib-GObject-CRITICAL **: 20:10:12.257: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Notifications enabled=1
Triggers enabled=0
Badges enabled=1
[📦 com.gexperts.Tilix tilix]$ tilix --new-process
(tilix:21): GLib-GObject-WARNING **: 20:10:21.696: invalid (NULL) pointer instance
(tilix:21): GLib-GObject-CRITICAL **: 20:10:21.696: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(tilix:21): GLib-CRITICAL **: 20:10:21.702: g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed
(tilix:21): GLib-CRITICAL **: 20:10:21.702: g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed
(tilix:21): GLib-CRITICAL **: 20:10:21.702: g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed
2022-01-03T20:10:21.705 [warning] terminal.d:2958:hostCommandExitedCallback **********COLLECT**********
(tilix:21): GLib-CRITICAL **: 20:10:21.707: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
The problem must be with HostCommand/flatpak-spawn
With 1.9.1 version it spawns first terminal on host without an error. Second split screen/spawn works but throws the error with COLLECT Spawning third terminal throws segfault. Or, spawning second shell in tab or split screen and waiting roughly 5 minutes without doing anything will also cause segfault.
2022-01-03T23:02:43.302 [warning] terminal.d:2969:hostCommandExitedCallback **********COLLECT**********
(tilix:120): GLib-CRITICAL **: 23:02:43.303: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:43.303: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:43.303: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:43.303: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:43.303: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:43.303: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
2022-01-03T23:02:54.344 [warning] terminal.d:2969:hostCommandExitedCallback **********COLLECT**********
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
(tilix:120): GLib-CRITICAL **: 23:02:54.345: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Thread 1 "tilix" received signal SIGSEGV, Segmentation fault.
0xffffffff00000000 in ?? ()
(gdb)
With 1.9.4 version it doesn't open at all and crashes straight away with **********COLLECT**********
error but not SIGSEGV
This can probably be closed, works fine now on Fedora Silverblue 36
EDIT: nevermind, crashed when trying to open the Preferences
Same behaviour on my Silverblue 36 machine.
The flatpak is generated by Fedora from the RPM packages.
Output of
tilix --version
:Launching from the terminal, I get:
Here's the full stack trace from the first critical warning:
It seems something is attempting to release a reference on a GVariant that has already been destroyed.