You are not logged in.
Hi,
skrooge 2.33.0-1 has been crashing on startup for about a week (last update before which it worked was on november 24 and during that update many qt5 libs were updated to version 5.15.16 but skrooge was not updated).
When launched from terminal in a wayland session I get
% skrooge
##WARNING: KServiceTypeTrader: serviceType "ThumbCreator" not found
##WARNING: Another action already registered for identifier edit_copy
##WARNING: Another action already registered for identifier edit_expandall
##WARNING: Another action already registered for identifier edit_collapseall
##WARNING: Another action already registered for identifier edit_copy
##WARNING: Another action already registered for identifier edit_expandall
##WARNING: Another action already registered for identifier edit_collapseall
##FATAL: Cannot mix incompatible Qt library (5.15.15) with this library (5.15.16)
21 -- exe=/usr/bin/skrooge
17 -- platform=wayland
16 -- appname=skrooge
17 -- apppath=/usr/bin
9 -- signal=6
10 -- pid=50645
18 -- appversion=2.33.0
20 -- programname=Skrooge
31 -- bugaddress=submit@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = skrooge path = /usr/bin pid = 50645
KCrash: Arguments: /usr/bin/skrooge
##WARNING: The Wayland connection experienced a fatal error: Mauvais descripteur de fichierNow a new skrooge version 2.33.0-4 exists in the testing-extra repository since november 23.
Downloading this version and installing it with pacman -U solves the problem.
I suppose this is a packaging bug but I haven't got an account to file a bug report.
Is it usual for a package to remain more than a week in the testing-extra repository ?
(This is genuine question not a disguised criticism : thanks go to the maintainer and let him take whatever time it takes.)
According to the package description on the arch linux gitlab, it was rebuilt on november 23 to be compatible with QT 5.15.16 so I am quite surprised such a minor package (in the sense that it is unlikely to break the system) stays so long in testing. Actually, I would have thought (after reading the wiki on repositories) that such a package would have been uploaded directly to the main repository, not to testing.
Thanks for any comment that would enable me to understand what happened here.
Last edited by daysfled (2024-12-01 19:07:19)
Offline
That was a packaging bug, fixed now.
Offline
Thank you.
Offline