AutoType not available when using Wayland

[ganomi46]

Expected Behavior

AutoType should be available as under X.

Current Behavior

AutoType not available in Wayland

Steps to Reproduce (for bugs)

Login to Plasma Wayland
Open KeePassXC
You will there are no auto login options

Operating system: OS
Debian SID amd64

[droidmonkey]

Are you referring to AutoType??

[ganomi46]

Hi.Yes, thatbis whatnI meant.-JiriOn 12 Sep. 2018 2:14 am, Jonathan White <notifications@github.com> wrote:Are you referring to AutoType?? —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

[Whompithian]

I can confirm lack of Auto-Type options using Plasma Wayland.

OS: 4.14.65-gentoo x86_64
plasma-5.46.0
wayland-1.15.0

[phoerious]

Auto-Type cannot work on Wayland due to security restrictions for which we haven't found a solution yet.

[rockihack]

I implemented autotype for wayland, still needs some work though.

https://github.com/rockihack/keepassx/blob/wayland-autotype/wayland.txt
https://github.com/rockihack/keepassx/tree/wayland-autotype/src/autotype/wayland

[apollo13]

It might be worth to look what https://gitlab.gnome.org/ofourdan/gnome-ponytail-daemon does. I seems to allow writing arbritrary key sequences to windows.

[tmccombs]

fwiw, there is a keepass plugin that supports this (https://keepass.info/help/kb/autotype_wayland.html), it does require access to /dev/uinput though.

For wlroots based compositors (such as sway) the input-method protocol (https://github.com/swaywm/wlroots/blob/master/protocol/input-method-unstable-v2.xml) or possibly the virtual-keyboard protocol (https://github.com/swaywm/wlroots/blob/master/protocol/virtual-keyboard-unstable-v1.xml) may allow implementing AutoType

[curiosityseeker]

I'm using KeePassXC on Arch Linux with Wayland (on KDE) in combination with ydotool, specifically ydotool-git in the AUR. And voilà - Autotype works flawlessly!

So perhaps it's possible to integrate ydotool's approach in KeePassXC directly?

[droidmonkey]

Oh nice!!

[apollo13]

Mhm, seems like it has a client/server structure because it uses /dev/uinput which requires (usually) root permission. Still better than no autotype I guess :D

[curiosityseeker]

Yes, it seems to be similar to how KeePass does it with KPUInput.

[apollo13]

https://gitlab.com/dogtail/dogtail/ seems to use the accessibility features in gnome and kde to send text to applications without the need of uinput and as such without any extra daemon.

[apollo13]

Ok, dogtail uses ponytail on wayland which I linked above already. Seems to be a rather heavy solution :/

[droidmonkey]

I think I'll opt for #2281 (comment) solution

[phoerious]

Using the DE's accessibility features is the only correct way to implement it. I only wish there were some kind of standard interface and not several largely incompatible ones, like there always is on Linux.

[MAFLO321]

I'm not very familiar with Wayland in deep, but can text-input-v3 protocol be used to solve the virtual-input problem?
KDE Plasma's and Gnome's Compositors both support it.

already mentioned by #2281 (comment)

[phoerious]

Perhaps, need to check. Thanks for the pointer.

[ztNFny]

I'm using KeePassXC on Arch Linux with Wayland (on KDE) in combination with ydotool, specifically ydotool-git in the AUR. And voilà - Autotype works flawlessly!

So perhaps it's possible to integrate ydotool's approach in KeePassXC directly?

Could you elaborate on that? How can KeePassXC be configured to use ydotool? I thought to just use it with cmd://, but then the input just goes .. no idea where.

[sam9032]

I don't have KDE Plasma to test right now, but under Gnome 40 with wayland it works ootb. Is this issue still present in plasma?

[vimpostor]

I don't have KDE Plasma to test right now, but under Gnome 40 with wayland it works ootb. Is this issue still present in plasma?

I just tested in Plasma and it doesn't work there. Neither global autotype nor manually choosing autotype from Keepass itself are working.
I am curious, does anyone know how this is working in Gnome? As far as I can see in the codebase, there is no implementation merged for Wayland yet, so I don't get why this is working in Gnome ootb for you.

Tested on Plasma 5.21.4 on Arch btw.

[droidmonkey]

Registering a global shortcut, but that might be covered by existing Wayland api. Most likely not, which would make it desktop env specific. /dev/uinput is not an option, requires root.

[rusty-snake]

Registering a global shortcut, but that might be covered by existing Wayland api. Most likely not, which would make it desktop env specific.

FWIW flatpak/xdg-desktop-portal#624

[ibahnasy]

This is also affected in Gnome (Ubuntu 22.10).

[cskr]

Auto-type from context menu used to work fine when running Firefox under xwayland, but even this has stopped working since 2.7.0.

[dasistwas]

Ubuntu 22.04 Beta, Keepassxc 2.7.0:

• Auto-Type window selection working for: Signal, Chromium,
• Not working for: Firefox, Terminal, Thunderbird

[tmccombs]

@dasistwas that is likely because Signal and Chromium are using XWayland, but Firefox, Terminal, and Thunderbird are using native wayland.

[dasistwas]

Update from Ubuntu 22.04 Beta: Suddenly auto-type started to work. But version of keepassxc did not change. It is still 2.7.1

[ourichermath]

I'd like to request the documentation at:

https://keepassxc.org/docs/KeePassXC_UserGuide.html#_auto_type

be added to. I'm on Fedora (Wayland) and it was really difficult to figure out where and how to change either the command line (-platform xcb) for my KeepassXC that was set to Autorun or the environment variable (QT_QPA_PLATFORM=xcb). Some mention of where and how would be nice.

Also, the documentation isn't clear in what KPXC is looking for with AutoType to work with applications. For instance, when I try to set it up to work with the password entry in the Virtual Machine Manager or for Grsync, the window names don't show up in KPXC's Advanced > Windows dropdown. And, no matter what I manually type in for a Window name, it doesn't work.

[foobar13372]

Ubuntu 22.04 + snap version of Firefox (Ubuntu 22.04 upgrademigrates FF to the snap version automatically): autotype works again. Did not test other programs since I only need keepass for Firefox.

[ibahnasy]

Wayland is disabled by default in 22.04 because of a bug, may be that's why autotype is working?

…

------- Original Message -------

On Friday, April 22nd, 2022 at 8:39 AM, foobar13372 ***@***.***> wrote: Ubuntu 22.04 + snap version of Firefox (Ubuntu 22.04 upgrademigrates FF to the snap version automatically): autotype works again. Did not test other programs since I only need keepass for Firefox. — Reply to this email directly, [view it on GitHub](#2281 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEUEU2JRXMER3MP2KS75ZNLVGJCRPANCNFSM4FUMUHSQ). You are receiving this because you commented.Message ID: ***@***.***>

[dasistwas]

Wayland is disabled by default in 22.04 because of a bug, may be that's why autotype is working?

no, I am on Wayland. But just realized seems only Firefox and xwayland programs do work with autotype. Terminal does not for example.

[tmccombs]

only Firefox and xwayland programs
is firefox using xwayland?

[dinotheextinct]

Is there any news to this? I am on sway and would like to know how I can get autotype working for firefox. Setting the xcb plattform, enables autotype, but hitting the configured shortcut from keepassxc for autotype doesnt open anything.

[Zocker1999NET]

but hitting the configured shortcut from keepassxc for autotype doesnt open anything.

As I know it, Sway does not allow other applications to apply global shortcuts themselves and also I do not know of any Wayland protocol which would implement this. It might be required to configure the shortcut on Sway manually and trigger AutoType on KeePassXC using a command / D-Bus (which is not possible yet?)

[siccovansas]

I recently installed Ubuntu 22.04 and ran into this issue.

Firefox and Chromium apparently use XWayland, so KeePasXC's Global Auto-Type works there.

My main other use of Auto-Type is in the terminal for which I use the Terminator terminal. I use the following (hopefully temporary) workarounds to run Terminator using XWayland when using the Ctrl + Alt + T shortcut and when starting Terminator via its icon in the launcher:

• In Ubuntu's Settings > Keyboard > Keyboard Shortcuts add this Custom Shortcut:
  • Name: Terminator with XWayland (to support KeePassXC)
  • Command: sh -c 'WAYLAND_DISPLAY=no /usr/bin/terminator'
  • Shortcut: Ctrl + Alt + T
• Create the file ~/bin/terminator with this code

  • #!/bin/sh
    
    # Catches calls to run 'terminator' (as this executable is in ~/bin and thus
    # listed earlier in PATH) and run it with XWayland which makes KeePassXC work
    # (via https://askubuntu.com/a/923393/54352)
    export WAYLAND_DISPLAY=no
    exec /usr/bin/terminator "$@"
    

  • Make it executable: chmod +x ~/bin/terminator

[dinotheextinct]

Not sure if this is some Gnome garbo, but under KDE Wayland, KeepassXC doesnt even offer the Autotype option??

[rusty-snake]

keepassxc/docs/topics/AutoType.adoc

Line 10 in 861fe2e

WARNING: Auto-Type will be disabled when run with a Wayland compositor on Linux. To use Auto-Type in this environment, you must set `QT_QPA_PLATFORM=xcb` or start KeePassXC with the `-platform xcb` command-line flag.

[dinotheextinct]

So I got the autotype option back, but when hitting the shortcut, there is no popup on wayland, when using it for firefox...

[ibahnasy]

I can confirm that auto typing is currently working in Wayland normally after the past system updates released in the past few weeks.

[dasistwas]

I can confirm that auto typing is currently working in Wayland normally after the past system updates released in the past few weeks.

Did you test autotype with the terminal as well? Only xwayland programs seem to work. All wayland windows do not trigger the autotype dialogue when using the global autotype shortcut.

[ibahnasy]

I can confirm that auto typing is currently working in Wayland normally after the past system updates released in the past few weeks.

Did you test autotype with the terminal as well? Only xwayland programs seem to work. All wayland windows do not trigger the autotype dialogue when using the global autotype shortcut.

It doesn't work with the terminal.
Triggering the autotype from the KPXC window or using the keyboard key combination, it works fine with some GUI apps like Google Chrome, but apps like FIrefox or Nautilus doesn't work.

[pio2398]

I can confirm that auto typing is currently working in Wayland normally after the past system updates released in the past few weeks.

Did you test autotype with the terminal as well? Only xwayland programs seem to work. All wayland windows do not trigger the autotype dialogue when using the global autotype shortcut.

It doesn't work with the terminal. Triggering the autotype from the KPXC window or using the keyboard key combination, it works fine with some GUI apps like Google Chrome, but apps like FIrefox or Nautilus doesn't work.

It's just can't work with wayland app. Could you read at least few comment back before posting? #2281 (comment)

[bigdiff]

Would it be possible to implement a workaround for now till xdg-desktop-portals implements a global shortcut portal.

I was thinking about making keepassxc launch with a --auto-type flag. Adding that to the list of custom shortcuts in gnome-control-panel would resolve the issue for now.

name: KeePassXC Auto-Type
command: keepassxc --auto-type

[vimpostor]

Would it be possible to implement a workaround for now till xdg-desktop-portals implements a global shortcut portal.

Can you guys at least read through the thread before pushing this again. Even if you fix the shortcut registering, you still can't find out the title of the window.

And again, the easiest way to move this issue forward is to move the already existing upstream proposals forward:

• https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/56
• Global keyboard shortcut portal flatpak/xdg-desktop-portal#624

Why are people pushing this issue every week but not the real underlying issue in the upstream protocols? This is all so backwards.
Quite frankly, this issue should be closed as "Won't fix" or locked until this mess is fixed in Wayland.
Originally back in 2013 Wayland was meant to cut out the "useless" middleman, ironically now we end up with even more useless middlemen just to deal with basic stuff like negotiating shortcut registering or server side decorations.

[droidmonkey]

This information was provided by @GalaxySnail

Currently, we have the global keyboard shortcut portal and libei, which should be good enough for auto-type.

For enumerating windows, there is a foreign toplevel list protocol.