clients icon indicating copy to clipboard operation
clients copied to clipboard

Clipboard not cleared when closing the application

Open ioqy opened this issue 2 years ago • 2 comments

Steps To Reproduce

  1. Go to a login item
  2. Click on copy usrname, password or website button
  3. Close the application

Expected Result

Clearing of the clipboard, like the timer or locking of the vault does.

Actual Result

The copied usrname, password or website stays in the clipboard

Screenshots or Videos

No response

Additional Context

The windows clipboard history is not active. The clipboard is cleared like expected when the timer runs out or the vault is locked either automatically or manually via the menu or the keyboard shortcut.

Operating System

Windows

Operating System Version

Windows 10 Pro 21H2

Installation method

Microsoft Store

Build Version

Version 2022.6.2, Shell 16.2.7, Renderer 96.0.4664.174, Node 16.9.1, Architecture ia32

ioqy avatar Jul 15 '22 07:07 ioqy

Put another way: The "Actual Result" is that if the app is closed before the clipboard timer has expired, the clipboard is never cleared (e.g., if exiting the app with 1 second left on a 5-min timer, the clipboard contents are preserved). An alternative "Expected Result" might be that a running clipboard timer should be honored even after quitting the app, although it might be more straightforward to just clear the clipboard on exit, any time there is a running clipboard timer. On the other hand, if the "copy value" buttons have not been used, or if the clipboard timeout is set to "Never", then the clipboard should not be cleared on exiting the app (as it may contain data copied from outside the app).

bwbug avatar Jul 17 '22 04:07 bwbug

Hi @ioqy, thank you for raising issue and @bwbug for giving more context around issue. The team will reproduce this and we'd make time to take a look.

dbosompem avatar Jul 28 '22 13:07 dbosompem

Happens on Flatpak version as well (as of commit b19643bd4712fff3b562310d8420a284b93844c653d59753e2dfac15e8e24c64)

giladwo avatar Jan 02 '23 20:01 giladwo

Any news?

It's been nearly 1 year and the bug is still in version 2023.5.1.

ioqy avatar Jun 27 '23 11:06 ioqy