I have had some wired issues with my Browser Vivaldi and Discord for a long time.
I updated my Systems a few days ago and since then Discord (aur) leaves me with a hyprland dialog that is not responding and asks me if I would like to terminate it when i try to paste an image. But as soon as I try to paste an image once all copy/paste functionality goes out the window, no copy/paste in terminal or in kate, only copying and pasting in Vivaldi to Vivaldi still works. Restarting the system fixes it, until u copy another image, it’s very wired.
//
I’m running cliphist, wl-clip and wl-clipboard
my im using hyprland and a amd-gpu
I originally installed eos with i3-wm
//
I tried just straight up using pkill to kill the clipboard and tested again, but the issue still occurs.
Wiredly tho, i can still copy things in Vivaldi to vivaldi… for some reason (also aur).
I also tried reinstalling the packages and even tested if removing xclip would fix anything.. Since you’re reading this, you can guess that this didn’t work out.
Any ideas on how to fix this?
Side note:
an logs i should put here? It was text copy paste to at first but i got that fixed
Well if you can copy and paste in one program but not the other then I would guess that there is an issue with Discord. I don’t use Discord outside of this Forum which I access through my web browser.
(before reading this keep in mind that i am no expert and my finding could be explained in different ways by other people this was what i observed and figured what happened, also keep in mind that Vivaldi and copy/pasting was working as described just a few weeks ago seemingly changed by an update)
Extensive testing revealed,
Vivaldi handles its clipboard internally when started with XWayland.
Vivaldis internal clipboard breaks x-clip and xsel when copying to Wayland applications
this happened inconsistently.
x-clip and xsel can interact with Vivaldi’s internal clipboard (but if they are on the system changes nothing for Vivaldi copy and paste capabilities)
For some reason, cliphist breaks when xsel’s clipboard content (when interacting with vivaldi’s internal system) is synchronized with Chliphist’s db
(this stomped my effords to try and fix it by syncing/force syncing via a script)
the fix:
-Vivaldi won’t run under Wayland by default
-> enable experimental Wayland compatibility mode in chrome://flags
(set preferred Ozone env to Wayland)
(i opted to set other setting to experimental Linux mode too in my frustration as a shotgun method)
make sure you're only starting Vivaldi under Wayland only
(i opted to replace my aur version with the flatpak and removed its
Capabilities to access x11 and xwayland xorg fallback via flatseal as a quick fix)
When I looked through Vivaldi’s forum post it was mentioned that it defaults to x11 because Wayland is too experimental, maybe the post was old i didn’t bother to check?
But then also why did it default to x11 on my machine and wouldn’t start in Wayland while set to auto?
And I’m guessing it started under Wayland before i had the issues? Why did it stop to default to Wayland???
This hole thing is getting more wired by the second.
I went to check and you are correct it seems to launch in Xwayland by default even though it says it will launch in Wayland by default if possible. Only after you set it specically to Wayland it will launch with native Wayland.
