Copy and paste (crtl-b/ctrl-c) of usernames/passwords works as expected.
Suddently it was no longer possible to copy and paste (crtl-b/ctrl-c) usernames/passwords. It worked before without any issue. A reboot didn't help.
As a workaround I downgraded keepassxc (from keepassxc-2.5.1-1.fc31.x86_64) to keepassxc-2.4.3-6.fc31.x86_64 and now copy/paste works again as expected.
It's interesting that is was working with 2.5.1 before. A reboot didn't help and also (re-)moving "~/.config/keepassxc" (so it was newly created) didn't help.
Operating system: Fedora 31 (gnome)
CPU architecture: x86
Kernel: 5.3.16-300.fc31.x86_64
Code wasn't touched in 2.5.2 regarding copy paste. Does it work at all (ie copy normal text from the application and paste it somewhere)
I'm am running 2.5.2 on Arch Linux KDE and I cannot reproduce. My steps are:
It works as expected.
@droidmonkey Copy and paste in general works without issues (e.g. between Firefox, Geany, Terminal)
On another system (also Fedora 31) and same version (keepassxc-2.5.1-1.fc31.x86_64) it's working as expected. So it seems, this is somehow specific to my current system. It's not really critical as I have a workaround, but I'll try to narrow it down further - might not be related to keepassxc at all...
Short recap. I only can reproduce the issue on my current system, but nowhere else. I have a workaround so I'm just curious why this happens.
Nevertheless a few more details, in case someone else is also affected. It's specific to GNOME (Wayland, default) - with GNOME (on Xorg) no problems. I encounter the problem between keepassxc and Terminal / Firefox / Geany - but it's working with e.g. Libre-Office.
My current workaround is to downgrade to "keepassxc-2.4.3-6.fc31.x86_64" or use the AppImage "KeePassXC-2.5.2-x86_64.AppImage" which works fine.
You should have said you were using Wayland.
I believe you need to install xwayland.
Installing it alone wouldn't solve the problem. You also need to force Qt to use to X11 backend. The reason why 2.4 works is that is that we disabled it for you there due to incompatibilities between Qt and Wayland. Since those issues were fixed, 2.5 enables Wayland support by default.
If you can start 2.4 at all, then XWayland is already installed and all you have to to do is start KeePassXC with the environment variable QT_QPA_PLATFORM=xcb set.
I have no idea why Copy&Paste isn't working properly on Wayland, but the whole ecosystem still feels rather alpha, which is a shame considering its 10-year history and the urgent need for X11 to die.
I'm using the flatpak build in RHEL8 (default Gnome3 with wayland) and have this same issue after the latest update.
As described in the last comment I am able to workaround the issue by setting QT_QPA_PLATFORM=xcb but it's kinda awkward to have to do this:
$ flatpak run --command=bash org.keepassxc.KeePassXC/x86_64/stable
$ QT_QPA_PLATFORM=xcb keepassxc
This is not my area of expertise but the fix has to be made in the flatpak packaging, right?
I can't paste into the KeePassXC (Fedora31, Wayland, Flatpak v2.5.2). @ptalbert's workaround works for me.
I had a similar issue that ctrl+b and ctrl+c was not working in the following scenario:
I have a record with a url, username and password
URL adresa link see screenshot first
alt+tab to go back to KeePassXC ctrl+b to copy user username (this does not copy user name, because focus is on the URL)This is works as designed, but I did not have this problem in earlier versions of KeePassXC.
I found shortcut ctrl+shift+u to open url without clicking, then my flow works as expected.
I have Lubuntu 18.04, and KeePassXC 2.5.3
Hi,
I think I'm affected by the same bug: I can paste to KeepassXC as long as I don't copy from KeepassXC. Once I've copied something from KeepassXC, I can no longer paste something to KeepassXC, it always paste the last thing I copied from KeepassXC.
I'm using KeepassXC 2.5.4 from Flathub on a Fedora 32 Silverblue system.
@ptalbert workaround (launching KeepassXC using QT_QPA_PLATFORM=xcb keepassxc) seems to solve the problem.
Welcome to Wayland...
The following seems to do the trick for me:
cp /var/lib/flatpak/exports/share/applications/org.keepassxc.KeePassXC.desktop ~/.local/share/applications/
chmod 644 ~/.local/share/applications/org.keepassxc.KeePassXC.desktop
sed -ri '/^Exec=/s/(--command=)/--env=QT_QPA_PLATFORM=xcb \1/' ~/.local/share/applications/org.keepassxc.KeePassXC.desktop
Workaround if you have KeePassXC installed as native system package is:
sudo sed -Eri 's/^Exec=(keepassxc.*)/Exec=env XDG_SESSION_TYPE=gtk \1/' \
/usr/share/applications/org.keepassxc.KeePassXC.desktop
I have the same problem here already since months. Distribution is Arch Linux, I am not on Wayland, environment is Kernel: 5.6.15-arch1-1 路 KDE-Plasma 5.18.5 路 KDE-Frameworks 5.70.0 路 Qt 5.14.2
The above mentioned workaround
QT_QPA_PLATFORM=xcb keepassxc
does not have any effect to me; can't still overtake user or password to the clipboard.
launching KeepassXC using
QT_QPA_PLATFORM=xcb keepassxc
Maybe a bit off-topic, but launching KeePassXC in this way on Fedora 32, GNOME Wayland, fixes for me also the window decorations issue 4652.
Not sure if I鈥檓 hitting this specific bug ; but my keepassxc started acting up for a few days (weeks max): I could not copy passwords out of keepass (the contents of my clipboard remain to whatever was there before that). Rebooting solved the issue.
I鈥檓 using the snap package:
keepassxc 2.6.1 1006 latest/stable keepassxreboot -
My system is
OS: Ubuntu 18.04.5 LTS x86_64
Kernel: 4.15.0-109-generic
DE: MATE
WM: Metacity (Marco)
WM Theme: Ambiant-MATE
Same here already since months. Leading QT_QPA_PLATFORM=xcb on launch didn't change anything, Version is also 2.6.1
Systeminformation:
Operating System: Arch Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.7-arch1-1
OS Type: 64-bit
For those using the Flatpak, a simple workaround:
QT_QPA_PLATFORM=xcb (as proposed in https://github.com/keepassxreboot/keepassxc/issues/4105)
Most helpful comment
I'm using the flatpak build in RHEL8 (default Gnome3 with wayland) and have this same issue after the latest update.
As described in the last comment I am able to workaround the issue by setting
QT_QPA_PLATFORM=xcbbut it's kinda awkward to have to do this:This is not my area of expertise but the fix has to be made in the flatpak packaging, right?