Bug 1216263

Summary: AusweisApp2 requires wrong Qt version
Product: [openSUSE] openSUSE Tumbleweed Reporter: Tilman Vogel <tilman.vogel>
Component: X11 ApplicationsAssignee: John Paul Adrian Glaubitz <adrian.glaubitz>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: rigo
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Tilman Vogel 2023-10-16 08:24:20 UTC
I have updated Tumbleweed yesterday

[10:21:16]til@alien:~ > tumbleweed status
latest   : 20231013
target   : 20231013
installed: 20231013

and had to ignore dependencies for AusweisApp2 1.26.7, and indeed it does not
start:

[10:17:02]til@alien:~ > AusweisApp2 
AusweisApp2: /lib64/libQt6Network.so.6: version `Qt_6.5.3_PRIVATE_API' not found (required by AusweisApp2)

Current Qt version is 6.6.0 instead of 6.5.3. Seems, AusweisApp2 needs a rebuild.
Comment 1 Rigo Wenning 2023-10-18 09:38:06 UTC
This is now compiled with right QT version and installs fine. But it is not usable. It just starts and goes as a symbol to the panel, but the software cannot open any window. This means it cannot open the settings or anything to connect a phone as a smartcard reader.

I don't know whether this is a new bug or should be continued here. This is the (filtered) chatter when I start from command line.

default       2023.10.18 11:33:43.845 8811 W (unknown:0)                                                                       : QQmlApplicationEngine failed to load component
default       2023.10.18 11:33:43.845 8811 W (/qml/+desktop/main.qml:47)                                                : qrc:/qml/+desktop/main.qml:47:11: Type TitleBar unavailable
default       2023.10.18 11:33:43.845 8811 W (/qml/Governikus/TitleBar/+desktop/TitleBar.qml:116)                       : qrc:/qml/Governikus/TitleBar/+desktop/TitleBar.qml:116:5: Type TitleBarAction unavailable
default       2023.10.18 11:33:43.845 8811 W (/qml/Governikus/TitleBar/+desktop/TitleBarAction.qml:58)                  : qrc:/qml/Governikus/TitleBar/+desktop/TitleBarAction.qml:58:3: Type TintableIcon unavailable
default       2023.10.18 11:33:43.845 8811 W (/qml/Governikus/Global/TintableIcon.qml:19) 

qml           2023.10.18 11:33:43.848 8811   UIPlugInQml::onQmlObjectCreated(ui/qml/UIPlugInQml.cpp:767)                : QML engine initialization finished with fatal errors

Will try flatpak version...
Comment 2 Tilman Vogel 2023-10-18 10:44:07 UTC
(In reply to Rigo Wenning from comment #1)
> This is now compiled with right QT version and installs fine. But it is not
> usable. It just starts and goes as a symbol to the panel, but the software
> cannot open any window. This means it cannot open the settings or anything
> to connect a phone as a smartcard reader.

Indeed, there is another (runtime) problem with Qt 6.6, please see:

https://github.com/Governikus/AusweisApp2/pull/49
Comment 3 Rigo Wenning 2023-10-18 15:29:18 UTC
Flatpak version works flawlessly
Comment 4 John Paul Adrian Glaubitz 2023-10-23 08:58:43 UTC
This already fixed in Tumbleweed.
Comment 5 John Paul Adrian Glaubitz 2023-10-23 09:00:22 UTC
(In reply to Tilman Vogel from comment #2)
> (In reply to Rigo Wenning from comment #1)
> > This is now compiled with right QT version and installs fine. But it is not
> > usable. It just starts and goes as a symbol to the panel, but the software
> > cannot open any window. This means it cannot open the settings or anything
> > to connect a phone as a smartcard reader.
> 
> Indeed, there is another (runtime) problem with Qt 6.6, please see:
> 
> https://github.com/Governikus/AusweisApp2/pull/49

They already have an internal fix for that and the upstream developer provided both patches to me. They just don't want to release a new upstream version for just fixing an issue on Linux. The next upstream release is planned for November.
Comment 6 Rigo Wenning 2023-10-23 09:04:51 UTC
@John Paul

I don't understand your comment #4. Is it fully fixed in tumbleweed or do we have to wait until the new release in November (because its only linux \o/). Because if it is fully fixed, I remove the flatpak version and return to tumbleweed.
Comment 7 John Paul Adrian Glaubitz 2023-10-23 09:18:06 UTC
(In reply to Rigo Wenning from comment #6)
> I don't understand your comment #4. Is it fully fixed in tumbleweed or do we
> have to wait until the new release in November (because its only linux \o/).
> Because if it is fully fixed, I remove the flatpak version and return to
> tumbleweed.

It's fixed in Tumbleweed with the help of local patches which were cherry-picked from the upcoming new upstream release. You can switch back to the Tumbleweed version which I am using myself.
Comment 8 Rigo Wenning 2023-10-23 09:19:58 UTC
Thanks so much for your work!!
Comment 9 Tilman Vogel 2023-10-23 09:20:50 UTC
(In reply to John Paul Adrian Glaubitz from comment #5)
> They already have an internal fix for that and the upstream developer
> provided both patches to me. They just don't want to release a new upstream
> version for just fixing an issue on Linux. The next upstream release is
> planned for November.

That's cool - however, I was a bit surprised that they don't just publish smaller fixes like this on their "community" github branch. Would have saved me some debugging and fixing effort just to hear "haha, we already fixed that". If you have got a good connection to them, maybe give them a hint that this would be a bit more community friendly.
Comment 10 John Paul Adrian Glaubitz 2023-10-23 09:27:18 UTC
(In reply to Tilman Vogel from comment #9)
> That's cool - however, I was a bit surprised that they don't just publish
> smaller fixes like this on their "community" github branch. Would have saved
> me some debugging and fixing effort just to hear "haha, we already fixed
> that". If you have got a good connection to them, maybe give them a hint
> that this would be a bit more community friendly.

Upstream is aware of this issue but their focus is Windows and Mac and the Linux port is currently provided as a courtesy only.

In the future, please just ping me when you run into problems and I will try to address these as soon as possible. I'm also the maintainer of the package in Debian FWIW.