Team KeePassXCkeepassxc@fosstodon.org
Oct 13, 2026, 6:38 PM@bbuk @eltonfc @ni @taschenorakel Which thread is that?
Replies
bbukbbuk@mastodon.socialOct 13, 2026, 6:48 PM@keepassxc @eltonfc @ni @taschenorakel https://github.com/keepassxreboot/keepassxc/issues/2973
Whether the debug that landed me there was the result of the crash or not I don't know.
All I was after was a dead simple cli passkey manager, the GTK layout was tiny fonts/widgets and too enterprisey. Sadly the cli package doesn't support passkeys for reasons I'm not informed enough to understand. The whole browser integration concerns me though. I think I'm just opposed to the complexity of the architecture of passkeys.
- Team KeePassXCkeepassxc@fosstodon.orgOct 13, 2026, 6:59 PM
@bbuk @eltonfc @ni @taschenorakel That thread is 8 years old. Back then, Qt had very buggy Wayland support. KeePassXC 2.7.12 and 2.8.0 are much more stable in that regard, as they use Qt 5.15 and Qt6, respectively. You may have come there with the "Wayland does not support QWindow::requestActivate()" message, but that's just a Qt-internal warning, not an error. We don't know of any "lid-close" crashes at the moment, so we'd need more info to help you.
- Team KeePassXCkeepassxc@fosstodon.orgOct 13, 2026, 7:01 PM
@bbuk @eltonfc @ni @taschenorakel Passkeys are not supported by the CLI, because they require an established browser connection, and thus a permanent background session. Since the CLI doesn't provide that, it cannot support passkeys.
- bbukbbuk@mastodon.socialOct 13, 2026, 7:18 PM
@keepassxc @eltonfc @ni @taschenorakel Well I feel that speaks to the over-complexity of the architecture (of passkeys, not your app). What kind of session, DBUS? ssh-agent seems to play nice with seahorse or whatever the gnome passphrase dialog is, is that kind of capability not usable?
And sorry if I'm over-tagging people, just using the defaults, believe it or not I'm new to mastodon and social media in general.
- Team KeePassXCkeepassxc@fosstodon.orgOct 13, 2026, 7:21 PM
@bbuk @eltonfc @ni @taschenorakel KeePassXC needs to be running in the background to respond to requests for passkeys. A CLI application doesn't do that, typically. We have an interactive CLI mode, but it doesn't have passkey support at the moment, as that would duplicate a lot of functionality.
Oct 13, 2026, 7:22 PM@keepassxc @bbuk @eltonfc @taschenorakel could you please stop mentioning me, I’m not interested in this debugging. :3
thanks. ^^- bbukbbuk@mastodon.socialOct 13, 2026, 7:13 PM
@keepassxc @eltonfc @ni @taschenorakel No worries, maybe it got OOMed, maybe I've got bad RAM, thanks for providing a passkey solution anyway. The AI use here is the big no for me though. I'm fine with passwords and 2FA, KISS FTW. And the last comment was 2024, so the issue appeared to me to be still relevant and ongoing for 8 years.
- Team KeePassXCkeepassxc@fosstodon.orgOct 13, 2026, 7:16 PM
@bbuk @eltonfc @ni @taschenorakel The last comments are only about cosmetic mismatches between a KDE6 desktop and the Qt5 app.
As for AI use, see https://keepassxc.org/blog/2025-11-09-about-keepassxcs-code-quality-control/ - bbukbbuk@mastodon.socialOct 13, 2026, 7:26 PM
@taschenorakel I'm sorry, that statement does nothing to allay my fears. I don't accept that AI for code is inevitable, necessary, stable between releases, deterministic, or particularly useful. I'll prefer code that is developed only by humans even if it takes a little longer. It has worked fine for 70 years. I don't believe you will draw the line correctly, or that that line will stay in place, be honoured by all developers, or that those developers will remain as competent because of it.