Been using keepassxc for years under X.org. Haven’t had a problem in years.
Yesterday I decided it’s time to use a full DE, and switch to wayland at the same time.
Setting up my newly installed CachyOS, I’m having weirdly inconsistent troubles with keepassxc’s autotype feature:
Sometimes it just works, sometimes not.
Typing into terminal windows seems to be particularly tricky, but I also noticed inconsistencies between Falkon and Firefos.
Sorry if it’s a bit vague, I can’t really pinpoint the issue (yet).
I remember that typing into other app windows is more restricted on wayland (as is right) and I even vaguely remember that Plasma has settings for allowing certain apps…?
I’ve also been reading keepassxc issues and it seems there will be a new feature coming out soon that deals with this elegantly, but not on my version, which is 2.7.12.
TIA
edit1:
Keepassxc’s AutoType is indeed not fully equipped for wayland, but there’s a new release in the pipeline that fixes this. The brave can compile it from the development branch.
edit2:
Hmm, no, still difficult. Now trying to get kepassxc and kdewallet to talk to each other, but that’s tricky too.
The edits suggested in that thread made Plasma go into a login loop :(
After undoing that I’m just using keepssxc 2.8 (compiled from -git) and hoping it works well enough.
edit3:
Here’s another pitfall: for keepassxc 2.7. to run under wayland it needs qt5-wayland which isn’t installed under Plasma, which runs on qt6. This isn’t even an optional dependency. So keepassxc 2.7 then defaults to run under Xorg, i.e. xwayland and you don’t even notice.
Hey, the official documentation is here: https://github.com/keepassxreboot/keepassxc/blob/develop/docs/topics/AutoType.adoc
Essentially, KeepassXC Autotype is fully supported on KDE Plasma 6, and all configuration is done within the app itself. The KDE settings you may be thinking of was in 5, but that is no longer the case when running on 6.0+.
It uses XDG Desktop Portals when run under Wayland; it should all be set up already if Auto-Type is working but essentially you need XDG Desktop Portal and the xdg-desktop-portal-kde package to allow it to integrate with the desktop.
The limitations on wayland are that it can’t match to a specific window title and can’t track when the keyboard focus changes between windows (due to how wayland works). The overview does note that certain other input methods can conflict with Auto-Type. But other than that it should be working fluidly without issue.
The only other consideration I can think of is are you running KeyPassXC natively or as a flatpak? Flatpak can sometimes be more locked down than needed for some apps. You could install Flatseal and ensure KeePassXC has the right permissions to access services outside of it’s sandbox.
Hey, the official documentation is here: https://github.com/keepassxreboot/keepassxc/blob/develop/docs/topics/AutoType.adoc
Thanks for that link! It points, however, to the development branch. While that entry is already 3 months old, the latest release is 6 months old and features none of the wayland-specific stuff mentioned.
My guess is that a new release is imminent, but I’ve compiled keepassxc-git for now. It’s generally working, the info you linked makes sense now, and I guess it will fix at least some of my problems.
On KDE Plasma you dont need flatseal, the integrated settings are better
Interesting apparently this already works?
There was a 500k€ donation of the sovereign tech agency to Flatpak which includes development of portals for password managers and spelling correction. Lets see how long that takes and then it needs to be adopted by desktops and apps. KDE will be really fast here, but KeepassXC devs are still working on the Qt6 port, so this might take a while.
You kinda answered your own question.
What you should do:
- report it on github
- wait for updates
There may be some quick and dirty workaround, but I didn’t find one when searching online.
