Samuel
Samuel
I encountered the same panic, it only happens if the receiver was created in a different process, so a workaround is to create the channel in the process the receiver...
Looks like Cargo.lock gen was removed in https://github.com/rustsec/audit-check/pull/20. I worked around this by adding a `- run: cargo generate-lockfile` step.
I worked around the issue by not using harfbuzz_rs to query
Command `heroic --enable-features=UseOzonePlatform --ozone-platform=x11` works for me too. Thanks for the workaround.
VSCode is an Electron app and it works fine for me. Could be the Electron version?
I have it installed directly from MS repo, I believe I followed [these instructions](https://code.visualstudio.com/docs/setup/linux), it has been a while, I remember that it was blurry at some point and I...
Same Electron. I will try to find the configs I changed.
I found the config I changed, in `~/.vscode/argv.json` I have `"disable-hardware-acceleration": true`, if I remove this vscode does not open on Wayland, but it still opens if I force x11...
I guess Code is doing too many custom things with Electron. I believe https://github.com/electron/electron/issues/44607 is tracking this bug on Electron, I'm surprised they are taking so long to fix this...
I'm not sure how it is on Arch, for me I created a replacement desktop file in `~/.local/share/applications/heroic.desktop` ``` [Desktop Entry] Name=Heroic Games Launcher Exec=/opt/Heroic/heroic --enable-features=UseOzonePlatform --ozone-platform=x11 %U Terminal=false Type=Application...