DietPi-Software | VSCodium

[ravenclaw900]

Status: Ready

Reference: #4267

Commit list/description:

• DietPi-Software | Add VSCodium install option
• DietPi-Software | Make VSCodium require desktop
• DietPi-Software | Also make VSCodium require git

[ravenclaw900]

Well, that was simple.

[MichaIng]

Lol a pretty simple naked install, but that is all fine when the package-contained setup is good. Good to have this as an alternative to VSCode after #4083.

[Joulinar]

and the good thing, version provided via apt package is same as available on GitHub. 👍

From install test
Setting up codium (1.55.2-1618361277) ...

on GitHub same version 1.55.2 is available https://github.com/VSCodium/vscodium/releases

[Joulinar]

I guess it's an issue of VSCodium but not sure. Could be as well me doing something wrong. At least I get an error while connecting to GitHub using the official GitHub Pull Request extension.

[MichaIng]

Please try to install/enable dbus:

apt install dbus
systemctl enable --now dbus

EDIT: Ah no that cannot be the reason as it's installed and enabled automatically with all desktop installs.

[ravenclaw900]

It looks like gnome-keyring is required, as after that I get no error.

[MichaIng]

When I try to sign into GitHub from VSCodium, in that status bar, it shows "Signing in to github.com..." forever, while it should show a login prompt, as far as I understand. I was thinking that it might be due to missing default browser, but making Firefox the default browser doesn't change anything 🤔.

Btw, we should add the application icon to the desktop?

---

EDIT: Tried to install gnome-keyring, but doesn't change something here. LXDE btw.

[Joulinar]

You would need to click on Signing in to github.com... to open the field where you can enter GitHub token

[MichaIng]

Ahhh, I didn't recognised that at the top.
EDIT: Worked for me without gnome-keyring as well.

[Joulinar]

@MichaIng

EDIT: Worked for me without gnome-keyring as well.

You don't have the error message at the bottom?

[MichaIng]

Nope.

[Joulinar]

Hmm I need to do another test. Which extension you used?

[MichaIng]

The official GitHub PR and Issues extension. I'll retry to be sure.

[MichaIng]

Okay, it was still required on a fresh setup. I think that daemon is needed to create a new keyring with credentials, while accessing an existing one does not require it, or so.

I'm not sure whether there is an alternative to that package, other issues indicate it, but I couldn't find one when searching packages with -keyring ending at least.

Shall we add it by default or add a note to the docs instead? The package is small, but it's an additional daemon/process running.

[Joulinar]

depends on what people will use it for. I guess this is dedicated to GitHub? Or does it might be related to other plugins as well?

[ravenclaw900]

I think that it would probably be best to add it, as you will probably need it for signing in to Microsoft accounts as well. However, we could probably configure the keychain automatically with the global software password.

[MichaIng]

I guess so. Cannot imagine that this extension uses its very own credentials/authentication method but that it's an API of codium that is use by other extensions as well.

[MichaIng]

Little research, gnome-keyring provides a backend daemon for the "Secrets API", described here: https://freedesktop.org/wiki/Specifications/secret-storage-spec/
Aside of the KDE wallet with GUI, there do not seem to be any relevant alternatives currently. Found https://github.com/grawity/secretsd, but it does not encrypt passwords, is hence more an experiment, I'd say.

Good to know about this in general, as other desktop applications might use that API as well to store or receive passwords, and also good to know that this is a central storage, hence you do not only trust the application like VSCodium here (which stores the master password) to safely store your GitHub token or other credentials but the Gnome keyring and API developers as well. Usually not relevant, but quite an important details for security enthusiasts 😉.

[ravenclaw900]

Hm, bash doesn't seem to be expanding the second home/* glob when uninstalling, and treating it literally.

[MichaIng]

Hmm , generally works fine here:

# bash -c 'rm -v /{root,home/*}/test'
rm: cannot remove '/root/test': No such file or directory
removed '/home/test/test'

I'll try it with VSCodium uninstall as well.

[ravenclaw900]

As a comparison:

# bash -c 'rm -v /{root,home/*}/test'
rm: cannot remove '/root/test': No such file or directory
rm: cannot remove '/home/*/test': No such file or directory

I'll try with a fresh VM.
Edit: It seems the glob only expands when the file/directory it's looking for exists, otherwise it prints it out literally.

[MichaIng]

It seems the glob only expands when the file/directory it's looking for exists, otherwise it prints it out literally.

Ah yes of course. Taking the glob literal is basically part of the expansion. * matches the literal * as well. What we want is to hide "file not found" errors: 02c8bb8

[Joulinar]

going to approve the PR from inside vscodium