Bug 1954742
| Summary: | KeepassXC should always use xWayland under Wayland | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | alfxs |
| Component: | keepassxc | Assignee: | Germano Massullo <germano.massullo> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 34 | CC: | germano.massullo, jgrulich, jreznik, kde-sig, lupinix.fedora, nonamedotc, rdieter, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | keepassxc-2.6.4-2.fc34 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-07 01:02:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
alfxs
2021-04-28 17:43:46 UTC
Some GNOME+Wayland users have already reported some quirks, but this is the response from keepassxc upstream developers [00:53] <droidmonkey[m]> This should be brought up with Qt [00:53] <droidmonkey[m]> We don't control platform integration that is Qt via xcb platform or qwayland platform [00:54] <droidmonkey[m]> I suspect that Fedora is on the bleeding edge, or stuck on a bad version, of qwayland [00:54] <droidmonkey[m]> Numerous reported issues with keepassxc on Fedora 33 and 34 [00:54] <droidmonkey[m]> But no other platform On my side instead, there is nothing I can do, I can just forward this report to Qt maintainers (In reply to Germano Massullo from comment #1) > Some GNOME+Wayland users have already reported some quirks, but this is the > response from keepassxc upstream developers > > [00:53] <droidmonkey[m]> This should be brought up with Qt > [00:53] <droidmonkey[m]> We don't control platform integration that is Qt > via xcb platform or qwayland platform > [00:54] <droidmonkey[m]> I suspect that Fedora is on the bleeding edge, or > stuck on a bad version, of qwayland > [00:54] <droidmonkey[m]> Numerous reported issues with keepassxc on Fedora > 33 and 34 > [00:54] <droidmonkey[m]> But no other platform > > On my side instead, there is nothing I can do, I can just forward this > report to Qt maintainers Is it possible to set the command line arguments in the .desktop file at least (-platform xcb)? Or would this break things for non-wayland users? yeah, adding to desktop will probably break for non-wayland users. I would prefer to not do that. (In reply to Mukundan Ragavan from comment #3) > yeah, adding to desktop will probably break for non-wayland users. I would > prefer to not do that. Why do you think that? I can start keepassxc -platform xcb on X11 (KDE) too. Well, I thought wrong. :) I just tested it in Xfce and no problems using `-platform xcb` This comment clarified why we are experiencing these problems. I will release a fix soon https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3BVLBS4B3XHJEXFVGD7RK2ZMXZG6JQZT/ FEDORA-2021-bedff8f66e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bedff8f66e FEDORA-2021-bedff8f66e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-bedff8f66e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-bedff8f66e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. (In reply to Fedora Update System from comment #7) > FEDORA-2021-bedff8f66e has been submitted as an update to Fedora 34. > https://bodhi.fedoraproject.org/updates/FEDORA-2021-bedff8f66e Can you please test and provide feedback? It is very important since we are discussing on the mailing list about the xcb problem and there are people that instead say that the Qt bug was already fixed like https://bugreports.qt.io/browse/QTBUG-88293?focusedCommentId=548882&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-548882 Thank you I have been using the new build of keepassxc and it works perfectly for me. It solves all the issues I have been experiencing. I am on GNOME wayland. (In reply to Alexandre Fernandez from comment #10) > I have been using the new build of keepassxc and it works perfectly for me. > It solves all the issues I have been experiencing. I am on GNOME wayland. Thank you (In reply to Germano Massullo from comment #9) It is very important since we are > discussing on the mailing list about the xcb problem and there are people > that instead say that the Qt bug was already fixed like > https://bugreports.qt.io/browse/QTBUG-88293?focusedCommentId=548882&page=com. > atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-548882 I was wrong, that comment was not related to xcb but to another bug concerning MIME types FEDORA-2021-bedff8f66e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |