[artix-general] jami-qt seg faulting, :(

[artist]

As it happens an update was built in staging - so consider it 
experimental for now.

You can try it using eg.

pacman -U 
https://mirror.clarkson.edu/artix-linux/repos/galaxy-goblins/os/x86_64/jami-daemon-20220722-8-x86_64.pkg.tar.zst

artist

On a bended knee, or systemd, you will never live free

On 3/20/23 09:20, Javier wrote:
>> [New Thread 0x7fff367fc6c0 (LWP 25043)]
>> [New Thread 0x7fff35ffb6c0 (LWP 25044)]
>> [New Thread 0x7fff317fa6c0 (LWP 25045)]
>> Daemon is running
>> No migration required
>> [Thread 0x7fff317fa6c0 (LWP 25045) exited]
>> [New Thread 0x7fff30ff96c0 (LWP 25046)]
>>
>> Thread 34 "jami-qt" received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 0x7fff537fe6c0 (LWP 25016)]
>> 0x0000000000000000 in ?? ()
>> (gdb) bt
>> #0  0x0000000000000000 in  ()
>> #1  0x00007fffeb8564e8 in  () at /usr/lib/libjami.so.13
>> #2  0x00007fffeb756ed3 in  () at /usr/lib/libjami.so.13
>> #3  0x00007fffeb0d72c3 in std::execute_native_thread_routine(void*) 
>> (__p=0x55555630f900) at 
>> /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:82
>> #4  0x00007fffeae9ebb5 in start_thread (arg=<optimized out>) at 
>> pthread_create.c:444
>> #5  0x00007fffeaf20d90 in clone3 () at 
>> ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
>
> Note that **/usr/lib/libjami.so.13** is owned by jami-daemon:
>
>> % pacman -Qo /usr/lib/libjami.so.13
>> /usr/lib/libjami.so.13 is owned by jami-daemon 20220722-7
>
> Weird enough, it's seg faulting whether using the artix jami-daemon 
> (galaxy) or the one from arch (community).
>
> Anyone aware?  Not sure if a rebuild is required, since it's too weird 
> the back trace shows a failure on stdc++...
>
> Thanks !
>
>