[artix-general] is jami not working for other jami artix users?

[Javier]

Jami keeps not working till now...  At least now there's more info about the failing library:

> Thread 1 "jami" received signal SIGSEGV, Segmentation fault.
> 0x00007ffff517c145 in QObjectData::dynamicMetaObject() const () from /usr/lib/libQt6Core.so.6
> (gdb)

And the BT:

> (gdb) bt
> #0  0x00007ffff517c145 in QObjectData::dynamicMetaObject() const () at /usr/lib/libQt6Core.so.6
> #1  0x00007ffff6c69e86 in  () at /usr/lib/libQt6Qml.so.6
> #2  0x00007ffff6cbc6bb in QQmlJavaScriptExpression::clearActiveGuards() () at /usr/lib/libQt6Qml.so.6
> #3  0x00007ffff6cc1b35 in QQmlJavaScriptExpression::~QQmlJavaScriptExpression() () at /usr/lib/libQt6Qml.so.6
> #4  0x00007ffff6cfc998 in  () at /usr/lib/libQt6Qml.so.6
> #5  0x00007ffff518e773 in QtPrivate::QPropertyBindingData::~QPropertyBindingData() () at /usr/lib/libQt6Core.so.6
> #6  0x00007ffff5181fc7 in QObjectPrivate::~QObjectPrivate() () at /usr/lib/libQt6Core.so.6
> #7  0x00007ffff6d0ebd3 in  () at /usr/lib/libQt6Qml.so.6
> #8  0x00007ffff6bd0f20 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () at /usr/lib/libQt6Qml.so.6
> #9  0x00007ffff6baa9e0 in QV4::Lookup::getterQObject(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6
> #10 0x00007fffcfff8b8f in  ()
> #11 0x00007fffffff10d0 in  ()
> #12 0x0000000000000007 in  ()
> #13 0x0000555558c440d0 in  ()
> #14 0x0000000000000000 in  ()

I can confirm what gdb signals as seg faulting at first is qt6-base:

> % pacman -Qo /usr/lib/libQt6Core.so.6
> /usr/lib/libQt6Core.so.6 is owned by qt6-base 6.5.3-1

Also:

> % pacman -Qo /usr/lib/libQt6Qml.so.6
> /usr/lib/libQt6Qml.so.6 is owned by qt6-declarative 6.5.3-1

So, this whole jami mess seems to be something about qt6...  Any discrepancy with respect to Arch qt6 packages?  On Arch, it seems people is not having issues, and the only open bug I see on Arch is:

https://bugs.archlinux.org/task/78299

Which is totally unrelated.  And for qt6 the only unrelated bug:

https://bugs.archlinux.org/task/78132

I don't see related issues on jami-daemon, jami-qt or opendht either on Jami's gitlab instance...

The issue seems qt6 related on Artix, rather than jami related.  Also when changing to use the jami-daemon from Arch, jami seg faults the same way.  It only seg faults upon trying to get into a particular chat, otherwise jami can remain open with no issues, but it's worthless without getting into chats...

No other Artix users having issues while using jami?


-- 
Javier

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20231001/556afd47/attachment-0001.sig>