Hi, I'm using keepass2 from the Debian unstable repositories.
My system is Siduction 64bit in XFCE.
One week ago I used keepass2 in my "normal" init system. Then there was a update to systemd. Since then the auto-type is extremely slow (15 characters in ~15secs). I followed the website instructions with the shortcut on 'keepass2 --auto-type'.
I already tried several things to fix this bug. Unfortunately I cannot distinguish where the problem's source is: systemd, mono or keepass2. Hopefully you as the developer(s) can help making this more precise.
All of these steps remained unsuccessful. The ONLY way to fix this problem in my case was to reinstall sysvinit-core (and therefore uninstall systemd-sysv). Then everything was fine again.
I already asked the people from Siduction [1] and Debian-Systemd [2]. All of them weren't able to give me a hint where the root of the problem may be. Could you imagine a service or bug that may cause the slow-down of the auto-type mechanism?
Fixing this bug seems to be quite important in my opinion. Debian will move to systemd end of this/beginning of next year and Debian unstable or Arch Linux are already using it. Maybe someone can reproduce this bug so we can narrow the possible reasons.
[1] http://forum.siduction.org/index.php?topic=4540
[2] #debian-systemd on irc.oftc.net
Filing a bug report in KeePass does not seem appropriate for a Debian problem - you have identified it as such by removing systemd-sysv.
A description of the KeePass Auto-Type engine can be found here:
https://sourceforge.net/p/keepass/discussion/329220/thread/0d255d22/
http://keepass.info/news/n140203_2.25.html
cheers, Paul
I am seeing very similar behavior on an up-to-date Linux Mint 17 (based off Ubuntu 14.04) system. It looks like there are some systemd packages installed, but if I understand correctly, mint/ubuntu have not actually switched to systemd? I'm using version 2.27 of KeePass, though I've downgraded to 2.25 and experienced the same issue. I've tried both the repository version and the downloadable version from keepass.info. I have been unable to find a workaround. Any suggestions?
The Auto-Type engine in 2.25 upwards is very different from previous KeePass versions. Try KeePass 2.24 and let us know how it goes.
cheers, Paul
I tried out 2.24 and I see the same, very slow performance with auto-type.
It takes several seconds (maybe 3 to 5) to start auto-typing and then
enters about 1 to 2 characters per second. The behavior is the same
whether I use the global shortcut (thereby invoking
keepass2 --auto-type
)or select an entry manually in the interface and hit CTRL-v.
Thanks,
Nathan
Last edit: Paul 2014-08-23
Then it's a mono / linux issue and I haven't any more suggestions.
cheers, Paul
I have good news, and I have bad news.
Good news: I solved the problem.
Bad news: I don't know how exactly.
I set up my whole system from the scratch. As I already write in the initial posting, I already did this some weeks ago with the difference that I a) installed the system, b) installed keepass2 (and other programs) and c) installed all updates (including sysvinit -> systemd).
This time, I installed the system, upgraded all packages and then installed keepass2, xsel xdotool and so on - and it works like a charm.
Please don't ask me why it's successful now, I really don't know. Maybe some packages interfere with each other if installed in a sysvinit system which is going to be upgraded later on.
Maybe you want to try with your distro and environment on a seperate hard disk? My system details can be seen in the first posting here and maybe we can find some more hints for a solution.
I ended up needing to reinstall my Linux system for unrelated reasons as well. As in Max's case above, Keepass now seems to be working normally again. I am running the same system, with the same /home folder, and have re-installed most (though definitely not all) of the same packages I had installed previously. Like Max, I have no idea what is different to cause it to work again.
KeePass doesn't have anything to do with Systemd directly. Probably there was some bug elsewhere that was fixed.
Best regards,
Dominik