Really bizarre Chrome bug that Largange seems to trigger
Not sure if this is something exotic on my system or what, so I'm posting here where people are likely to be using both Largange and Chrome to see if anyone can replicate it...
Ubuntu, 24.04. When I copy text from Largange to paste in Chrome -- just about anywhere -- Chrome freezes.
When I paste it into gedit, and copy it from there instead, Chrome has no complaints.
Any guesses as to what's going on?
P.S. Further digging seems to indicate a likelihood that Chrome chokes on mime type metadata of the paste. Which would be text/gemini, and thus something Chrome doesn't know about.
P.P.S. It took forcing Chrome to use X11 to stop this from happening, (`google-chrome --ozone-platform=x11`) which, potentially, might indicate an actual Largrange bug... they keep pointing fingers at each other, though.
P.P.P.S. ...and unfortunately, VSCode also has the same problem. Le sigh...
Mar 22 · 7 weeks ago
3 Comments ↓
Lagrange Copy/Paste is weird in my Ubuntu setup. The middle-button copy is not supported at all, and I often have to go back and forth a few times to copy.
🌆 skyjake [mod...] · Mar 22 at 21:25:
The X11/Wayland clipboard handling in SDL2 is not great. They've improved it greatly for SDL3, so when I eventually upgrade, the copy/paste behavior should improve.
I have no clue about what's going on with this Chrome glitch, though.
I have a similar problem with vim. If I copy from Lagrange to vim, vim gives me an error. If I copy to gedit then to vim it works fine.
I assumed it was something weird with SDL (which seems to be the case as @skyjake said above)