Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#75093 - [jami-qt] SIGABRT after Qt upgrade
Attached to Project:
Community Packages
Opened by Oleksandr Natalenko (post-factum) - Thursday, 16 June 2022, 20:56 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 16 June 2022, 21:31 GMT
Opened by Oleksandr Natalenko (post-factum) - Thursday, 16 June 2022, 20:56 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 16 June 2022, 21:31 GMT
|
DetailsSince recently jami-qt doesn't start any more:
Name : jami-qt Version : 20220511-2 Name : qt6-base Version : 6.3.1-1 [~]> jami-qt Qt build version mismatch! 6.3.0 fish: Job 1, 'jami-qt' terminated by signal SIGABRT (Abort) It seems like it needs a rebuild against new Qt? |
This task depends upon
Closed by Antonio Rojas (arojas)
Thursday, 16 June 2022, 21:31 GMT
Reason for closing: Fixed
Additional comments about closing: jami-qt 20220511-3
Thursday, 16 June 2022, 21:31 GMT
Reason for closing: Fixed
Additional comments about closing: jami-qt 20220511-3
Comment by Oleksandr Natalenko (post-factum) -
Thursday, 16 June 2022, 21:11 GMT
And I can confirm that rebuilding the package against newer Qt version fixes the issue.