|
Bugzilla – Full Text Bug Listing |
| Summary: | AusweisApp2 requires wrong Qt version | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Tilman Vogel <tilman.vogel> |
| Component: | X11 Applications | Assignee: | 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
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... (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 Flatpak version works flawlessly This already fixed in Tumbleweed. (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. @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. (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. Thanks so much for your work!! (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. (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. |