From je-vv at e.email Mon Oct 2 04:28:06 2023 From: je-vv at e.email (Javier) Date: Sun, 1 Oct 2023 20:28:06 -0600 Subject: [artix-general] is jami not working for other jami artix users? In-Reply-To: <8332f046-00ae-c1ab-3bd9-f9ca35abe1f3@e.email> References: <8332f046-00ae-c1ab-3bd9-f9ca35abe1f3@e.email> Message-ID: <08d9f56a-0036-4bdc-a3de-9e6f6c9a2448@e.email> 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: From je-vv at e.email Mon Oct 2 04:39:46 2023 From: je-vv at e.email (Javier) Date: Sun, 1 Oct 2023 20:39:46 -0600 Subject: [artix-general] artix-announce mailing list automation? Message-ID: <814f8881-15e8-4ca0-8d47-ab2691e0a478@e.email> Hi ! I just noticed there's a new announcement "Changes to default password hashing algorithm and umask settings", though I didn't ever receive the corresponding artix-announce mail, and I don't see it in the artix-announce September's mails archive either: https://lists.artixlinux.org/archives/artix-announce/2023-September/thread.html So it seems it was never sent through the artix-announce mailing list. Therefore I'm wondering if there's some automation involved between publishing new announcements and sending the corresponding email on artix-announce, in which case there might be something broken. If there's no automation, then it's fine, someone might have forgotten, or consider it not relevant enough given the lack of action from users. Just wondering if there's some automation broken. -- 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: From je-vv at e.email Sat Oct 7 02:50:29 2023 From: je-vv at e.email (Javier) Date: Fri, 6 Oct 2023 18:50:29 -0600 Subject: [artix-general] kvantum-theme-materia needing to change dependencies and rebuild to allow upgrading kvantum Message-ID: <0d7bd67f-9ade-445f-b437-63d9463d4bc5@e.email> > resolving dependencies... > looking for conflicting packages... > error: failed to prepare transaction (could not satisfy dependencies) > :: installing kvantum (1.0.10-2) breaks dependency 'kvantum-qt5' required by kvantum-theme-materia It seems on Arch, kvantum-theme-materia was rebuilt with different dependencies: > % pacman -Ss kvantum > world/kvantum 1.0.10-2 [installed: 1.0.10-1] > SVG-based theme engine for Qt5/6 (including config tool and extra themes) > world/kvantum-theme-materia 20220823-1 [installed] > Materia theme for KDE Plasma 5 > extra/kvantum 1.0.10-2 [installed: 1.0.10-1] > SVG-based theme engine for Qt5/6 (including config tool and extra themes) > extra/kvantum-theme-materia 20220823-3 [installed: 20220823-1] Noticed how it moved from "-2" to "-3" (and Artix is still on "-1")... And looking at the package changes on Arch: https://gitlab.archlinux.org/archlinux/packaging/packages/materia-kde/-/commit/e3ea3e908a8ac820becf39930b8d0ccd82d1ea6b Yeap, it no longer depends on "kvantum-qt5" and it depends instead on "kvantum". Thanks ! -- 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: From qontinuum at artixlinux.org Sat Oct 7 10:06:53 2023 From: qontinuum at artixlinux.org (Qontinuum) Date: Sat, 7 Oct 2023 08:06:53 +0000 Subject: [artix-general] kvantum-theme-materia needing to change dependencies and rebuild to allow upgrading kvantum In-Reply-To: <0d7bd67f-9ade-445f-b437-63d9463d4bc5@e.email> References: <0d7bd67f-9ade-445f-b437-63d9463d4bc5@e.email> Message-ID: On Fri, Oct 06, 2023 at 06:50:29PM -0600, Javier wrote: > > resolving dependencies... > > looking for conflicting packages... > > error: failed to prepare transaction (could not satisfy dependencies) > > :: installing kvantum (1.0.10-2) breaks dependency 'kvantum-qt5' required by kvantum-theme-materia > > It seems on Arch, kvantum-theme-materia was rebuilt with different dependencies: > > > % pacman -Ss kvantum > > world/kvantum 1.0.10-2 [installed: 1.0.10-1] > > SVG-based theme engine for Qt5/6 (including config tool and extra themes) > > world/kvantum-theme-materia 20220823-1 [installed] > > Materia theme for KDE Plasma 5 > > extra/kvantum 1.0.10-2 [installed: 1.0.10-1] > > SVG-based theme engine for Qt5/6 (including config tool and extra themes) > > extra/kvantum-theme-materia 20220823-3 [installed: 20220823-1] > > Noticed how it moved from "-2" to "-3" (and Artix is still on "-1")... And looking at the package changes on Arch: > > https://gitlab.archlinux.org/archlinux/packaging/packages/materia-kde/-/commit/e3ea3e908a8ac820becf39930b8d0ccd82d1ea6b > > Yeap, it no longer depends on "kvantum-qt5" and it depends instead on "kvantum". > > Thanks ! > > -- > Javier Hey Javier, Just pushed the update. It will reach the mirrors soon. -- Q -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From je-vv at e.email Sun Oct 22 04:48:53 2023 From: je-vv at e.email (Javier) Date: Sat, 21 Oct 2023 20:48:53 -0600 Subject: [artix-general] is jami not working for other jami artix users? In-Reply-To: <08d9f56a-0036-4bdc-a3de-9e6f6c9a2448@e.email> References: <8332f046-00ae-c1ab-3bd9-f9ca35abe1f3@e.email> <08d9f56a-0036-4bdc-a3de-9e6f6c9a2448@e.email> Message-ID: Now is even worse... jami doesn't even start: > % jami > Another instance is running. So now it doesn't even get to segfault. I've seen gitlab issues about multiple users on the same device with such problem, but this is not the case, just single PC user... It seems nobody uses jami on artix, :( I probably can't ask on arch, since pure arch is probably working fine, since there are no bugs filed against jami on arch, and I don't use arch, hehe. Ohh well... -- 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: