I've recently moved full-time to wayland using sway, and in need of a clipboard manager, started using copyq compiled from the wayland branch mentioned here. See Sway and Wayland Support.įirst of all, thanks for the amazing work on copyq, and in particular on the wayland support! var maxChars = 16 var initialDelay = 100 var delayBeetweenKeystrokesMs = 10 var notificationTimeoutMs = 8000 function typeText(slice) " Icon=\xf2d2Įdit (): I've added the updated command to copyq-commands repository. Command= " copyq: // Safely types item text or encrypted item without using clipboard (simulates key presses). PS - If you ever want a Wayland enviro to test to on, you can always download virtualbox and just install an Ubuntu 17.10 or KDE neon iso on it. No worries, I'm happy to give you a hand in any way I can. Good news is that they're working on it at nVidia but it's probably going to be a while before it's stable. I have another machine with an nVidia card on it and I wouldn't run Wayland on it either. I'm still not using Wayland because of some issues (mainly: having unfriendly NVidia graphics card on one machine, screen sharing for video conferencing doesn't work). I just made a Hotkey in Gnome's Keyboard prefs for: copyq show - it works beautifully. EDIT: Good news! The focus worked perfectly. I can test the focusing issue and let you know. It just means now that you need an extra step after you've selected the clip: Ctrl-V. It will get sent to clipboard just as in X and the clipboard monitoring will still work as it did before. So you can still bring up CopyQ, peruse and select the clip you want. That being said, there would be no restrictions on manipulating the clipboard. The restriction on injecting text happens at the destination Window and not at the source app. Yeah, I would expect that injecting text directly into a Window would be a problem but I don't think that would be affected by CopyQ running natively in Wayland or not. Surprisingly, this still works on OS X and Windows Unfortunately, injecting keystrokes is what CopyQ does to be able to paste directly to target window. I'm really happy you're looking into Wayland. The command itself doesn't tell the system that it's focusing given window, it just sends a message to main application to show the window. The question is how much Wayland (or a window manager) restricts window focusing or prevents focus stealing. This already works with copyq show and similar. The easiest work around for that would be to have a copyq daemon that can be given commands to show CopyQ via terminal Surprisingly, this still works on OS X and Windows. app A can see exactly what's on app B's gui, capture it's keystrokes, audio, as well inject keystrokes into it. The Turla espionage operation also infected Linux systems with Thanks for the detailed description.Īpp A and app B both on the X.org. Ubuntu’s Snap packages aren’t yet as secure as Canonical’s marketing claims (X11) Your Linux PC isn't as secure as you think it is Best of luck and let me know if you need a Beta tester on Wayland. This is by far my favorite clipboard manager and the prospect of being able to use it again makes me really happy. We can then go to our Desktop Environments and set the hotkeys for these commands manually or CopyQ can even use the gsettings (or it's KDE equivalent) to register the hotkeys with the Desktop Environment. The easiest work around for that would be to have a copyq daemon that can be given commands to show CopyQ via terminal, for example: copyqd -showclipboard or copyqd showsnippets etc. In most cases that's not a big deal but for some people it is because they may be sandboxing an untrusted app on X11 across a restricted account, for example, a video game running off of steam or GOG which is running on X and they don't know or trust the author.Īs for hotkeys on Wayland, the in app hotkeys that are used when the CopyQ window is focused work fine but the global hotkeys that CopyQ relies on to show and hide it do not work due to Wayland's restriction on keystroke capture. I left some articles below but to summarize these issues: suppose you have app A and app B both on the X.org. I've tested CopyQ on Gnome-Shell Wayland:ĬopyQ does work under Wayland via the XWayland compatibility layer (that term just means that it sends it off to X11) but it would be ideal if it worked natively on Wayland due to the massive security vulnerabilities present in X11 and the delicate nature of the information being handled by this application.
0 Comments
Leave a Reply. |