You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
After enabling the "Move to Top" function, rapid clicks will cause the item to disappear, whereas slow clicks will result in no issues #3368
Describe the bug
As stated in the title, I will upload a video to demonstrate the effect. When the "Move to Top" setting is enabled, rapid clicks—whether using single-click or double-click mode—will cause the item to disappear, whereas slightly slower clicks will not trigger this issue. I have disabled all scripts and settings under F6, so there are no other interfering factors.
Version, OS and Environment
CopyQ 剪贴板管理器 13.0.0
Qt: 6.8.3
KNotifications: 6.12.0
Compiler: MSVC
Arch: x86_64-little_endian-llp64
OS: Windows 11 Version 25H2
This might be a Windows specific problem, I cannot reproduce this on Linux. No idea what can cause this.
A workaround could be to disallow removing any items if a keyboard modifier (e.g. Shift) is not pressed with the following commands (here is how to add the command to CopyQ):
[Commands]
1\Command=" global.onItemsRemoved = function() { if ( queryKeyboardModifiers().length === 0 ) { fail(); } }"
1\Icon=
1\IsScript=true
1\Name=Allow Delete only with a Keyboard Modifier
2\Command=" copyq: ItemSelection().current().removeAll();"
2\Icon=
2\InMenu=true
2\Name=Delete Items
2\Shortcut=shift+del
size=2
I did not notice this, using CopyQ 13.0.0 on Windows 11 25H2. Please follow that checklist, in particular steps 10 to 13, to clarify. I suggest focusing on the single-click mode.
By “the "Move to Top" function”, do you mean the “Move item to the top” preference in the History tab?
License
This comment and any other from myself on this ticket is offered under the terms of CC0 1.0.
This might be a Windows specific problem, I cannot reproduce this on Linux. No idea what can cause this.
A workaround could be to disallow removing any items if a keyboard modifier (e.g. Shift) is not pressed with the following commands (here is how to add the command to CopyQ):
[Commands]
1\Command="
global.onItemsRemoved = function() {
if ( queryKeyboardModifiers().length === 0 ) {
fail();
}
}"
1\Icon=
1\IsScript=true
1\Name=Allow Delete only with a Keyboard Modifier
2\Command="
copyq:
ItemSelection().current().removeAll();"
2\Icon=
2\InMenu=true
2\Name=Delete Items
2\Shortcut=shift+del
size=2
Hello, thank you for your instructions. Unfortunately, even after I enabled this command, the item still disappears. It seems that it isn’t being deleted, but rather hidden in some form.
I did not notice this, using CopyQ 13.0.0 on Windows 11 25H2. Please follow that checklist, in particular steps 10 to 13, to clarify. I suggest focusing on the single-click mode.
By “the "Move to Top" function”, do you mean the “Move item to the top” preference in the History tab?
License
Hello, I’m also on Windows 11 25H2 and updated to the latest version 15.0 for further testing. I used the single-click option and also selected the “Move item to the top” preference in the History tab. The behaviour is still exactly the same as in the GIF I recorded — unless I press and hold the left mouse button for a while, the item simply disappears on a quick click. This issue did not exist before version 7.1, which is why I have been downgrading and using an older version all this time.
Update: I tested double-click as well, and it's the same — as long as the "Move item to the top" setting is enabled, even a double-click causes the item to disappear. Both of my computers can reproduce this bug, so it's unlikely to be caused by my local configuration. Could it possibly be related to the system language settings?
Thank you very much for reporting @tiger-git2022
I have not managed to reproduce on 2 CopyQ 15.0.0.17 installs on 2 Windows 11 25H2 installs out of 2 tested. Are you able to reproduce this on a fresh Windows profile (session)? If so, it would help if you could list the minimal steps needed to reproduce on a fresh Windows account, once CopyQ is opened for the first time.
Are there any errors or warnings in logs (F12 shortcut from the main window)?
Hey, thanks for the heads-up, I found the issue! I do have the sync feature enabled, and that folder is a OneDrive synced folder. I just created a new tab that doesn't use the sync feature, and in this new tab everything works perfectly — the items no longer disappear. So the cause is very likely a bug triggered by a folder synced to a cloud drive. No wonder both of my computers had this problem, because I was using the sync feature.
Thank you very much for reporting @tiger-git2022 I have not managed to reproduce on 2 CopyQ 15.0.0.17 installs on 2 Windows 11 25H2 installs out of 2 tested. Are you able to reproduce this on a fresh Windows profile (session)? If so, it would help if you could list the minimal steps needed to reproduce on a fresh Windows account, once CopyQ is opened for the first time.
Hey, thanks for the heads-up, I found the issue! I do have the sync feature enabled, and that folder is a OneDrive synced folder. I just created a new tab that doesn't use the sync feature, and in this new tab everything works perfectly — the items no longer disappear. So the cause is very likely a bug triggered by a folder synced to a cloud drive. No wonder both of my computers had this problem, because I was using the sync feature.
@tiger-git2022: Thank you, but it remains unclear why the speed of clicks would influence the results. Can you answer Lukas’s question about logs? Does disabling your network connection change the results?
@tiger-git2022: Thank you, but it remains unclear why the speed of clicks would influence the results. Can you answer Lukas’s question about logs? Does disabling your network connection change the results?
wait, i will check with no network. this is the log for with network and with cloud sync, i use test1-6 to test:
[2026-05-18 16:11:17.673] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 1154 ms
[2026-05-18 16:11:17.809] Note : info:: url: test2
[2026-05-18 16:11:17.810] Note : info:: url: test1
[2026-05-18 16:11:17.815] Note : info:: url: test3
[2026-05-18 16:11:17.816] Note : info:: url: test2
[2026-05-18 16:11:17.816] Note : info:: url: test3
[2026-05-18 16:11:17.818] Note : info:: url: test4
[2026-05-18 16:11:17.819] Note : info:: url: test4
[2026-05-18 16:11:19.932] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 990 ms
[2026-05-18 16:11:20.953] Note : info:: url: test5
[2026-05-18 16:11:20.954] Note <cmd/onClipboardChanged-15296>: Command "Fetch Image": Finished in 3122 ms
[2026-05-18 16:11:21.924] Note : info:: url: test4
[2026-05-18 16:11:21.926] Note : info:: url: test5
[2026-05-18 16:11:21.926] Note <cmd/onClipboardChanged-19992>: Command "Fetch Image": Finished in 4092 ms
[2026-05-18 16:11:21.927] Note <cmd/onClipboardChanged-2248>: Command "Fetch Image": Finished in 4093 ms
[2026-05-18 16:11:22.945] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 965 ms
[2026-05-18 16:11:22.999] Note <cmd/onClipboardChanged-15296>: Command "Save Images": Finished in 2042 ms
[2026-05-18 16:11:23.007] Note <cmd/onClipboardChanged-19992>: Command "Save Images": Finished in 1078 ms
[2026-05-18 16:11:23.008] Note <cmd/onClipboardChanged-2248>: Command "Save Images": Finished in 1079 ms
[2026-05-18 16:11:24.973] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 945 ms
[2026-05-18 16:11:25.024] Note : info:: url: test5
[2026-05-18 16:11:25.025] Note : info:: url: test6
[2026-05-18 16:11:26.990] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 976 ms
[2026-05-18 16:11:36.435] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 944 ms
[2026-05-18 16:11:42.107] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 930 ms
[2026-05-18 16:12:07.212] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 958 ms
[2026-05-18 16:12:30.346] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 916 ms
[2026-05-18 16:12:30.549] Warning <cmd/provideClipboard-32704>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:32.266] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:32.466] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:32.497] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:32.656] Note : info:: url: test6
[2026-05-18 16:12:36.973] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 1001 ms
[2026-05-18 16:12:37.307] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:38.793] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:39.006] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:39.037] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:39.157] Note : info:: url: test5
[2026-05-18 16:12:41.368] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 996 ms
[2026-05-18 16:12:41.390] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:41.615] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:41.681] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:41.714] Note : info:: url: test3
[2026-05-18 16:12:43.879] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 967 ms
[2026-05-18 16:12:45.813] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:47.732] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 944 ms
[2026-05-18 16:12:47.755] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:47.951] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:47.998] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:50.474] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:52.076] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 992 ms
[2026-05-18 16:12:52.100] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:52.303] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:52.345] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
Can you test this development build with the OneDrive synchronization? I think OneDrive may be locking the files for some reason (for reading or writing/deletion). The fix should print a warning in logs and try to work around the issue.
Activity
hluk commentedon Jan 24, 2026
This might be a Windows specific problem, I cannot reproduce this on Linux. No idea what can cause this.
A workaround could be to disallow removing any items if a keyboard modifier (e.g. Shift) is not pressed with the following commands (here is how to add the command to CopyQ):
Chealer commentedon Mar 10, 2026
Thank you for reporting
I did not notice this, using CopyQ 13.0.0 on Windows 11 25H2. Please follow that checklist, in particular steps 10 to 13, to clarify. I suggest focusing on the single-click mode.
By “the "Move to Top" function”, do you mean the “Move item to the top” preference in the History tab?
License
This comment and any other from myself on this ticket is offered under the terms of CC0 1.0.tiger-git2022 commentedon May 15, 2026
Hello, thank you for your instructions. Unfortunately, even after I enabled this command, the item still disappears. It seems that it isn’t being deleted, but rather hidden in some form.
tiger-git2022 commentedon May 15, 2026
Hello, I’m also on Windows 11 25H2 and updated to the latest version 15.0 for further testing. I used the single-click option and also selected the “Move item to the top” preference in the History tab. The behaviour is still exactly the same as in the GIF I recorded — unless I press and hold the left mouse button for a while, the item simply disappears on a quick click. This issue did not exist before version 7.1, which is why I have been downgrading and using an older version all this time.
tiger-git2022 commentedon May 15, 2026
Update: I tested double-click as well, and it's the same — as long as the "Move item to the top" setting is enabled, even a double-click causes the item to disappear. Both of my computers can reproduce this bug, so it's unlikely to be caused by my local configuration. Could it possibly be related to the system language settings?
Chealer commentedon May 15, 2026
Thank you very much for reporting @tiger-git2022
I have not managed to reproduce on 2 CopyQ 15.0.0.17 installs on 2 Windows 11 25H2 installs out of 2 tested. Are you able to reproduce this on a fresh Windows profile (session)? If so, it would help if you could list the minimal steps needed to reproduce on a fresh Windows account, once CopyQ is opened for the first time.
hluk commentedon May 16, 2026
Do you use Synchronization plugin in CopyQ - i.e. synchronize items in a tab into a directory?
Are there any errors or warnings in logs (F12 shortcut from the main window)?
tiger-git2022 commentedon May 16, 2026
Hey, thanks for the heads-up, I found the issue! I do have the sync feature enabled, and that folder is a OneDrive synced folder. I just created a new tab that doesn't use the sync feature, and in this new tab everything works perfectly — the items no longer disappear. So the cause is very likely a bug triggered by a folder synced to a cloud drive. No wonder both of my computers had this problem, because I was using the sync feature.
tiger-git2022 commentedon May 16, 2026
Hey, thanks for the heads-up, I found the issue! I do have the sync feature enabled, and that folder is a OneDrive synced folder. I just created a new tab that doesn't use the sync feature, and in this new tab everything works perfectly — the items no longer disappear. So the cause is very likely a bug triggered by a folder synced to a cloud drive. No wonder both of my computers had this problem, because I was using the sync feature.
Chealer commentedon May 16, 2026
Thank you very much Lukas
@tiger-git2022: Thank you, but it remains unclear why the speed of clicks would influence the results. Can you answer Lukas’s question about logs? Does disabling your network connection change the results?
tiger-git2022 commentedon May 18, 2026
wait, i will check with no network. this is the log for with network and with cloud sync, i use test1-6 to test:
[2026-05-18 16:11:17.673] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 1154 ms
[2026-05-18 16:11:17.809] Note : info:: url: test2
[2026-05-18 16:11:17.810] Note : info:: url: test1
[2026-05-18 16:11:17.815] Note : info:: url: test3
[2026-05-18 16:11:17.816] Note : info:: url: test2
[2026-05-18 16:11:17.816] Note : info:: url: test3
[2026-05-18 16:11:17.818] Note : info:: url: test4
[2026-05-18 16:11:17.819] Note : info:: url: test4
[2026-05-18 16:11:19.932] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 990 ms
[2026-05-18 16:11:20.953] Note : info:: url: test5
[2026-05-18 16:11:20.954] Note <cmd/onClipboardChanged-15296>: Command "Fetch Image": Finished in 3122 ms
[2026-05-18 16:11:21.924] Note : info:: url: test4
[2026-05-18 16:11:21.926] Note : info:: url: test5
[2026-05-18 16:11:21.926] Note <cmd/onClipboardChanged-19992>: Command "Fetch Image": Finished in 4092 ms
[2026-05-18 16:11:21.927] Note <cmd/onClipboardChanged-2248>: Command "Fetch Image": Finished in 4093 ms
[2026-05-18 16:11:22.945] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 965 ms
[2026-05-18 16:11:22.999] Note <cmd/onClipboardChanged-15296>: Command "Save Images": Finished in 2042 ms
[2026-05-18 16:11:23.007] Note <cmd/onClipboardChanged-19992>: Command "Save Images": Finished in 1078 ms
[2026-05-18 16:11:23.008] Note <cmd/onClipboardChanged-2248>: Command "Save Images": Finished in 1079 ms
[2026-05-18 16:11:24.973] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 945 ms
[2026-05-18 16:11:25.024] Note : info:: url: test5
[2026-05-18 16:11:25.025] Note : info:: url: test6
[2026-05-18 16:11:26.990] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 976 ms
[2026-05-18 16:11:36.435] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 944 ms
[2026-05-18 16:11:42.107] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 930 ms
[2026-05-18 16:12:07.212] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 958 ms
[2026-05-18 16:12:30.346] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 916 ms
[2026-05-18 16:12:30.549] Warning <cmd/provideClipboard-32704>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:32.266] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:32.466] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:32.497] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:32.656] Note : info:: url: test6
[2026-05-18 16:12:36.973] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 1001 ms
[2026-05-18 16:12:37.307] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:38.793] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:39.006] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:39.037] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:39.157] Note : info:: url: test5
[2026-05-18 16:12:41.368] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 996 ms
[2026-05-18 16:12:41.390] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:41.615] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:41.681] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:41.714] Note : info:: url: test3
[2026-05-18 16:12:43.879] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 967 ms
[2026-05-18 16:12:45.813] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:47.732] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 944 ms
[2026-05-18 16:12:47.755] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:47.951] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:47.998] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:50.474] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:52.076] Note : [copyq.plugin.itemsync.filewatcher] Files listed in 992 ms
[2026-05-18 16:12:52.100] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
[2026-05-18 16:12:52.303] Warning <cmd/monitorClipboard-10780>: Aborting clipboard cloning: Clipboard changed again
[2026-05-18 16:12:52.345] Warning <cmd/monitorClipboard-10780>: [qt.qpa.mime] Retrying to obtain clipboard.
hluk commentedon May 18, 2026
Can you test this development build with the OneDrive synchronization? I think OneDrive may be locking the files for some reason (for reading or writing/deletion). The fix should print a warning in logs and try to work around the issue.
Fix ItemSync data loss from transient file errors on cloud/SMB dirs
Fix ItemSync data loss from transient file errors on cloud/SMB dirs
Fix ItemSync data loss from transient file errors on cloud/SMB dirs
Fix ItemSync data loss from transient file errors on cloud/SMB dirs
Fix ItemSync item disappearance with cloud-synced directories
Fix ItemSync data loss from transient file errors on cloud/SMB dirs
Fix ItemSync item disappearance with cloud-synced directories (#3605)