Arch Linux

413x1nkp

Member

Registered: 2024-05-02

Posts: 2

[SOLVED] VSCodium doesn't open the files properly

Whenever i double-click a file in thunar, or click `Open With>VSCodium` The VSCodium's window does indeed start, but the file isn't opened in it.
If a VSCodium window is already open, then double-clicking a file will create a new empty VSCodium window...

I believe this started to occur after i tried to fix my terminal, kitty, from being selected as a default way of opening a directory. This was quite annoying for me, clicking on "Show in folder" in the browser on a downloaded file only to be led to an open terminal window. So I did some research and most people recommended using `xdg-mime` for this.
I simply typed in

xdg-mime default thunar.desktop inode/directory

to make Thunar handle opening of a directory, however this somehow have led to odd consequences with VSCodium described above.

I tried resetting the inode/directory mimetype to a previous value of kitty.desktop, but this did not help.
I tried to wipe off all of the user-overrides that i've ever made to the mimetype handling by modifying `~/.local/share/applications/mimeinfo.cache`, alas this also did nothing.
I tried re-installing VSCodium, kitty and Thunar; no results out of this either. (i just ran `yay -R kitty thunar vscodium && yay -S thunar kitty vscodium` so i might've did this wrong somehow?)
I tried using vscodium-uri-handler.desktop for handling mimetypes, and even though now there would just be one VSCodium window at a time even if you open a new file (as it is supposed to be), the file itself would not open in the VSCodium. So just the window is created. Command i used is `xdg-mime default vscodium-uri-handler.desktop text/plain`

Before you ask, i did look at the wiki but i couldn't yield any information about how changing a single mimetype handling could affect mimetype handling of a whole, unrelated application like VSCodium.

I'm at a loss here to be honest... Not sure what to do.

Packages mentioned with their versions:

vscodium 1.89.0.24127-1
thunar 4.18.10-2
kitty 0.33.1-4
kitty-shell-integration 0.33.1-4
kitty-terminfo 0.33.1-4

PC Specifics:

OS: Arch Linux x86_64
Kernel: 6.8.9-arch1-1
WM: Hyprland (Wayland)

Last edited by 413x1nkp (2024-05-08 20:23:09)

resu_xunilhcrA

Member

Registered: 2024-05-08

Posts: 6

Re: [SOLVED] VSCodium doesn't open the files properly

I believe this started to occur after i tried to fix my terminal, kitty

It happens to me two days ago, when I updated vscodium (to version 1.89.0.24126) : unlike you, I didn't do anything particular (i.e. it worked good , I updated, it didn't work anymore).

Get back to version 1.88.1.24104-1 and wait for future update that correct this bad behavior (that's what I did).

Edit : found this : https://github.com/VSCodium/vscodium/issues/1865

Last edited by resu_xunilhcrA (2024-05-08 12:45:01)

413x1nkp

Member

Registered: 2024-05-02

Posts: 2

Re: [SOLVED] VSCodium doesn't open the files properly

I believe this started to occur after i tried to fix my terminal, kitty

It happens to me two days ago, when I updated vscodium (to version 1.89.0.24126) : unlike you, I didn't do anything particular (i.e. it worked good , I updated, it didn't work anymore).

Get back to version 1.88.1.24104-1 and wait for future update that correct this bad behavior (that's what I did).

Edit : found this : https://github.com/VSCodium/vscodium/issues/1865

Yeah, i downgraded. It did, indeed work.
I guess the solution was much simpler than i expected..

Thank you.

resu_xunilhcrA

Member

Registered: 2024-05-08

Posts: 6

Re: [SOLVED] VSCodium doesn't open the files properly

One can also edit the file ~/.local/share/applications/codium.desktop (or /usr/share/applications/codium.desktop) and remove the --unity-launch flag (works with version 1.89.1.24130-1)