Created attachment 1724405 [details] Start keepass via the gnome-shell Description of problem: After copying the password of the selected entry in keepass (ctrl-c) end exit the keepass program, the password is coied into the journalctl Version-Release number of selected component (if applicable): 2.46 (but also its predecessor) How reproducible: Start keepass via the gnome-shell (see attachment) (the bug does not occur when starting keepass from the commandline!) and copy a password from a selected item in the keepass windows. The password, which is in memory for a short time will appear in journalctl when closing keepass Steps to Reproduce: 1.Start keepass via the gnome-shell (the bug does not occur when starting keepass from the commandline!) 2. Select an entry 3. Choose Copy password from the right-click menu or via ctrl-c 4. Exit keepass (Ctrl-Q or via Menu->Exit) Actual results: After step 4, the copied plain password is in plain text available in journalctl. You can check this in the terminal via 'journalctl' en scroll to the last several lines. One of these contains the line keepass.desktop entry like this: keepass.desktop[]: <password appears here in plaintext!> Expected results: After exiting keepass, all that was in the clipboard must not appear in plaintext in the journalctl
You can get a similar effect without quitting KeePass by copying before the previous copy timer has expired. In this case, the PID that appears in the journal is of `/usr/bin/xsel --input --clipboard --nodetach`, which is used by KeePass set the clipboard. Curiously, it’s not the PID of the process that has just exited, but of the process that exited the previous time that the clipboard was cleared, even though the timestamp is current. It’s not clear to me how a process that no-longer exists can write a message to the journal.
This bug is present in Fedora 32 on X11, but not in Fedora 31 with the same versions of KeePass and xsel. Clutching at straws, could this be related to Gnome's clipboard manager?
It turns out that people have been seeing this issue on Wayland since at least Fedora 27: https://sourceforge.net/p/keepass/discussion/329220/thread/33d6afdc/
*** Bug 1909485 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 2053691 has been marked as a duplicate of this bug. ***
As a workaround for this issue, I have retired KeePass in Rawhide and Fedora 36.
@Peter: perhaps you want to orphan the package, so that it becomes clear to the community that we are not going to keep maintaing it. I did not touch the EPEL branch for years, and I am personally using KeePassXC for some time now. I don't have permissions to retire keepass at https://src.fedoraproject.org/rpms/keepass
sorry, typo, I meant: I don't have permissions to orphan keepass
I'm using KeePassXC too. I have set the main admin for "orphan", and I understand that that will cause the EPEL branches to be retired in six weeks.