Whenever I launch VSCode (no matter the version, currently 1.97.1) via the desktop file, the editor froze after 1-3sec. I checked the desktop file and found that '--ozone-platform-hint=auto' is the argument that causes the issue. The last log lines, when run with --verbose: > [89808:0212/115110.614745:INFO:CONSOLE(26)] "Overwriting grammar scope name to file mapping for scope text.yaml.jinja. > Old grammar file: file:///home/apit/.vscode/extensions/samuelcolvin.jinjahtml-0.20.0/syntaxes/jinja-yaml.tmLanguage.json. > New grammar file: file:///home/apit/.vscode/extensions/wholroyd.jinja-0.0.8/syntaxes/jinja-yaml.json", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/services/textMate/browser/backgroundTokenization/worker/textMateTokenizationWorker.workerMain.js#TextMateWorker (26) > [89808:0212/115110.615388:INFO:CONSOLE(34)] "%cTRACE color: #888 CommandService#executeCommand _setContext", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (34) > [89808:0212/115110.623788:INFO:CONSOLE(34)] "%cTRACE color: #888 CommandService#executeCommand _setContext", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (34) > [89808:0212/115110.624046:INFO:CONSOLE(34)] "%cTRACE color: #888 CommandService#executeCommand _setContext", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (34) > [89808:0212/115110.670094:INFO:CONSOLE(34)] "%cTRACE color: #888 [secrets] getting secret for key: secret://vscode.loginAccount", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (34) > [89808:0212/115110.670176:INFO:CONSOLE(34)] "%cTRACE color: #888 [secrets] no secret found for key: secret://vscode.loginAccount", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (34) > [89808:0212/115110.679043:INFO:CONSOLE(34)] "%cTRACE color: #888 MainThreadFileSystemEventService#$watch(): request to start watching uncorrelated (extension: ms-python.python, path: file:///home/apit/projects/IAS/ansible, recursive: true, session: 0.442119407771022, excludes: ["**/.git/objects/**","**/.git/subtree-cache/**","**/.hg/store/**","**/.dart_tool"], includes: undefined)", source: vscode-file://vscode-app/opt/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (34) > [main 2025-02-12T10:51:11.426Z] lifecycle (main): phase changed (value: 4) > [main 2025-02-12T10:51:25.783Z] CodeWindow: detected unresponsive I also tested: '/usr/bin/vscode --enable-features=UseOzonePlatform --ozone-platform=wayland --verbose' and it crashes the same way. I'm under gui-wm/sway-1.10.1, but I have the cashes for a few months now, meaning older versions of sway should be affected, too. The issue seems to be related to https://github.com/microsoft/vscode/issues/184124 where other distros experience the same bug under wayland. If I remove the use flag, vscode works as expected.
My suggestion is to remove the flag: --ozone-platform-hint=auto for now.
Please attach emerge --info app-editors/vscode PS. Works fine under kde + wayland for me.
Created attachment 918808 [details] emerge info
Hey, you can simply disable the 'wayland' useflag to remove --ozone-platform-hint=auto from the desktop file :D Which means you will be running on XWayland I will wait for your feedback on how it went before marking this as solved
(In reply to Adel KARA SLIMANE from comment #4) > Hey, > > you can simply disable the 'wayland' useflag to remove > --ozone-platform-hint=auto from the desktop file :D Which means you will be > running on XWayland > > I will wait for your feedback on how it went before marking this as solved Hey, yeah, that did fix the desktop file. I didn't know that the wayland flag does only change the desktop file. After your comment, I checked the ebuild and agree that we can close this bug. Thank you everyone for you help.
I can confirm: when starting either logseq or vscode, since recent update, --ozone-platform-hint=auto causes the app to freeze, in the former case not even a window is displayed while the latter shows window and keeps asking me if I want to restart the window over and over (with long delay). when I removed that option it started on wrong display and with wrong window-size, but it works. same for logseq. --enable-wayland-ime is an option I left in in both cases, it does not change anything... as of last week, it still worked, so it was some update to configs or library or something that caused it, since app-editors/logseq-desktop-bin is still 0.10.9-r1, no changes to upstream...
