Keepassxc bug where it copies last entry from clipboard instead

Hello World,

I use keepassxc and while Initially it seemed to work fine, I noticed a weird bug/behavior? where after a while if I ctrl+c to get a password from it the little progress bar that shows it will only be in memory for 15 secs starts but when I go to ctrl+v it somewhere I instead end up pasteing the last entry from the clipboard app(the standard one that comes installed with KDE Plasma, I didn’t add anything extra)…
If I click the clipboard icon on the taskbar and clear history then keepassxc works for a while untill sooner or later then the same thing happens again.

Any ideas how I could even begin to diagnose and hopefully fix this pretty please?!

Thank you.

P.S. I’d like to mention that I used the same program and KDE Plasma in EndeavourOS(arch based) and there it worked fine.

P.P.S. I have keepassx installed from fedora linux, but I’ll give the flatpak one a shot too and report back if it behaves the same.

Image

Based on the image you posted on the other thread, I would assume the correct option is the last one since its different from the rest, just like the one I have. I used to have lots of problems with KeePassXC and after installing that version Its all gone.

Hahahaha, well in my case it seems to be the complete opposite, the last one was crappy, while the middle one(so far at least, still testing) seems good. :clown_face:

There might be issues with the browser not detecting KeePassXC, I solved it by installing that version from that Repo. Did you test the clipboard issue ?

Well, it’s been several hours now and the flathub version still works fine… :thinking:

The only problem now beeing that I can’t use the workaround of editing /usr/share/applications/org.keepassxc.KeePassXC.desktop and changing the value of Exec to keepassxc -platform xcb in order to enable autotype on wayland because that file doesn’t appear anymore! :confounded::angry::face_with_symbols_over_mouth:

Oh well, guess I’ll leave the thread open for another dar or two before marking it solved, so if anyone figures out/has any suggestions for a solution to the autotype workaround that would be great!

If not, I suppose it’s something I could learn to live without, in the end… :face_with_diagonal_mouth: After all even with it enabled it’s still buggy and annoying as hell because of:

that appears pretty much every time you try to use it and have thus far been unable to find a way to make it stop asking me…

KeepassXC Flatpak from Flathub works just fine.

I am on Kinoite here and use that, the clipboard works normally.

Might be some edge case KDE bug?

Hahaha lol

  1. You can use the same method, but flatpak desktop entries are in /var/lib/flatpak/export/share/applications I think
  2. You dont need to. Just open the KDE Flatpak settings, edit KeepassXC’s settings, and remove the Wayland option. Automatically uses XWayland

Normally these dialogs should have an option to set the permission permanently. File a bug please, bugs.kde.org

Component: plasmashell

Mention that this is the input portal and when uses with KeepassXC it doesnt keep its state and you need to constantly allow it.

KDE Connect uses the same portal and that setting persists awesomely

I thoughts using the same OS means having the same errors :skull:, Since I had a browser issues with it and I am not the only one.

Hahahaha, yeah, you’d think so right?! :crazy_face:

  1. Yaaay, it’s there, at least I can change it’s taskbar icon now, been really bugging me, thank you!! :grin:
  2. Now before I go do anything else let me just try to make myself clear, because judging by your replies I’m not sure we’re talking about the same thing:

a) I don’t use x11, I hate x11, I use/like wayland;

b) the reason for modifying Exec is that without that the Auto-Type options panel doesn’t even appear inside the keepassxc program…
Not even gonna pretend I understand why, but here is a pic with default Exec:

And now with modified Exec:

Thoughts?

P.S. Cool, I’ll see about letting the kde bug hunting people know, thanks. :slightly_smiling_face:

yes I know.

Flatpak apps “see” the available display protocol thingy. If you disable Wayland for that app, it automatically switches to X11 which is XWayland.

Not sure if you also need to set your browser into XWayland mode.

Which would mean that those 2 apps can transparently see and manipulate each other.

A Wayland implementation will be way better, but may need time

Ohhh, I see, well here’s hoping for the future!

“Wayland, wayland, sure it can,
If it can’t do it…”

uuuummm, a little help finishing that rhyme? :wink: