SEGV in phosh_util_escape_markup
What problem did you encounter
Phosh crashes often on Debian/Mobian testing, coredumpctl
How to reproduce
It may happen during interaction but maybe also without.
What is the (wrong) result?
coredumpctl is filled with stack traces like this
Stack trace of thread 19196:
#0 0x00000055772fd8cc phosh_util_escape_markup (phosh + 0xed8cc)
#1 0x0000005577309e40 n/a (phosh + 0xf9e40)
#2 0x0000007f9a2f1f70 n/a (libffi.so.8 + 0x6f70)
#3 0x0000007f9a2f1500 n/a (libffi.so.8 + 0x6500)
#4 0x0000007f9b93ead4 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x17ad4)
#5 0x0000007f9b93e2f8 g_closure_invoke (libgobject-2.0.so.0 + 0x172f8)
#6 0x0000007f9b953224 n/a (libgobject-2.0.so.0 + 0x2c224)
#7 0x000000557728f290 n/a (phosh + 0x7f290)
#8 0x0000007f9baef078 n/a (libgio-2.0.so.0 + 0x146078)
#9 0x0000007f9bad3078 n/a (libgio-2.0.so.0 + 0x12a078)
#10 0x0000007f9b82b584 g_main_context_dispatch (libglib-2.0.so.0 + 0x56584)
#11 0x0000007f9b82b950 n/a (libglib-2.0.so.0 + 0x56950)
#12 0x0000007f9b82bc74 g_main_loop_run (libglib-2.0.so.0 + 0x56c74)
#13 0x0000007f9c12a6c0 gtk_main (libgtk-3.so.0 + 0x2676c0)
#14 0x0000005577258d70 main (phosh + 0x48d70)
#15 0x0000007f9b01d2fc __libc_start_call_main (libc.so.6 + 0x272fc)
#16 0x0000007f9b01d3cc __libc_start_main_impl (libc.so.6 + 0x273cc)
#17 0x0000005577258ef0 _start (phosh + 0x48ef0)What is the expected behaviour?
Context
Which version did you encounter the bug in?
-
I used the precompiled Debian package (e.g. by running a prebuilt image). Please paste the output oof dpkg -s phoshbelow.
Source: phosh (0.21.0-1)
Version: 0.21.0-1+b1How are you running phosh?
-
PureOS amd64 qemu image -
Mobile phone (model: PP1.2 , operating system version: Mobian with Linux 5.17) -
Librem5 devkit -
nested compositor. If so please give the full command you start phosh with. -
other (please elaborate)