Bug 1761153

same issue in F31(Beta) and in F32(Rawhide). F30 is fine

possible duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1759158

tested F32 (Beta). the issue is still there:

- it is an issue in Firefox and not in Chrome for reasons explained in https://bugzilla.redhat.com/show_bug.cgi?id=1759158 (comment #3)
- separate copy and paste of username and password works

I propose to raise the severity to urgent because it is a security issue. with this I support comment 19 on the related bug https://bugzilla.redhat.com/show_bug.cgi?id=1759158

meanwhile I have been using keepass in F32 for more than one week in production and my comment is based on the following experience

on several occasions the clipboard did not clear at all and keepass froze. I could only fix this (keepass frozen) by rebooting the machine (database was unharmed luckily). I know that the clipboard did not clear because I could paste the contents (before rebooting) into another application without problem. the freezing happened only when I was modifying the database. it did not happen in normal operation (copy and paste of username and password)

As I understand it, no-one's yet figured out how to do auto-type reliably to Wayland applications.

I've sent a patch upstream to document the current behaviour.  https://sourceforge.net/p/keepass/patches/123/

I've also made a feature request that auto-type be supported on Wayland in the future.  https://sourceforge.net/p/keepass/feature-requests/2564/

(In reply to Peter Oliver from comment #5)
> As I understand it, no-one's yet figured out how to do auto-type reliably to
> Wayland applications.
> 
> I've sent a patch upstream to document the current behaviour. 
> https://sourceforge.net/p/keepass/patches/123/
> 
> I've also made a feature request that auto-type be supported on Wayland in
> the future.  https://sourceforge.net/p/keepass/feature-requests/2564/

thank you

(In reply to Peter Oliver from comment #5)
> As I understand it, no-one's yet figured out how to do auto-type reliably to
> Wayland applications.
> 
> I've sent a patch upstream to document the current behaviour. 
> https://sourceforge.net/p/keepass/patches/123/
> 
> I've also made a feature request that auto-type be supported on Wayland in
> the future.  https://sourceforge.net/p/keepass/feature-requests/2564/

are they not saying this is a Wayland issue and it makes more sense to fix it there when it affects other applications as well
of course if they fix it, there is a big chance the solution can be adapted for other applications as well

Yes, I believe that someone is saying that, but I’m not sure whether he’s a KeePass developer, and I’m not sure that he and I have entirely the same understanding of the situation.

Wayland is not a drop-in replacement for the X Window System: it intentionally has different features and capabilities.  Desktop applications and libraries will require some adaptation.

So, I don’t think it would be fair to say “this is a bug in Wayland that needs to be fixed in Wayland”.  However, it might be fair to say “we’re not going to be able to do this unless a Wayland expert designs a solution for us”, and I suppose in practical terms that amounts to the same thing.

I am using fedora32, debian buster and opensuse tumbleweed - all with the gnome desktop. on buster autotype still works (probably because it is not on wayland yet) but wayland will be default on debian soon. then wayland will be the standard

the developer of xdotool said he did not consider wayland https://github.com/jordansissel/xdotool/issues/282#
googling brings up evemu https://fedoramagazine.org/simulate-device-input-evemu/

as a user I can only say: KeePass (the original one by Dominik Reichl) is a very important software. because it provides security it must not be compromised. I am not sure (it surpasses my knowledge) if the clipboard is protected with wayland. maybe that is the first thing to establish