1

I have VSCode installed using snap for a while, but since yesterday It's not showing up in apps/search.

I narrowed down the issue /var/lib/snapd/desktop/applications/code_code.desktop contains --force-user-env as in Exec=/snap/bin/code --force-user-env %F. If I remove --force-user-env it shows up fine and works as usual. The issue is, with every reboot --force-user-env comes back.

If I copy the desktop file to ~/.local/share/applications then the shortcut I have (Super+2) to launch VSCode, instead of going to the running instance, always opens a new window so I loose the ability to switch.

1 Answer 1

0

I had the exact same issue on Debian trixie. VS Code had been pinned to my taskbar and suddenly vanished. The ~/.local workaround brought it back, and the super keys were working normally for me.

I upgraded everything again today, and now it works without the ~/.local file. The .desktop file looks the same, so I assume it was a Gnome issue.

3
  • 1
    So you're saying the solution that didn't work for the user in question is working for you? Could you explain how to solve the issue described in the question? Since you also made an update that seems to have resolved the issue (so that the non-functional workaround is no longer needed), you may want to mention the exact versions of the involved packages. Commented Nov 22 at 8:26
  • The OP's workaround worked for me, yes. The solution for me on Debian trixie was sudo snap refresh and apt -U upgrade. Now I have VS code 1.106.2 and gnome-session 48.0-1+deb13u1, although I don't see anything relevant in the changelog. Commented Nov 23 at 9:47
  • Yes, this was fixed in some update few weeks back. Now no need to edit the .desktop file. Commented Nov 28 at 9:20

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.