Package Details: vscodium-bin 1.116.02821-1

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Conflicts: vscodium
Provides: codium, vscode, vscodium
Submitter: ckatri
Maintainer: Icelk
Last Packager: Icelk
Votes: 377
Popularity: 9.43
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2026-04-27 15:00 (UTC)

Pinned Comments

<deleted-account> commented on 2021-05-12 00:31 (UTC)

@Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 30 Next › Last »

Icelk commented on 2025-11-10 16:07 (UTC)

@terashy

Not from me at least. Do you have vscodium-bin-features installed? It seemed to cause problems. Otherwise, try with downloading the binary from the vscodium github and report back :)

willker commented on 2025-11-04 18:46 (UTC) (edited on 2025-11-04 18:57 (UTC) by willker)

Hi, could you modify the launch script so that lines in codium-flags.conf support shell variable expansion (like $HOME)? Currently, variables are passed literally and not expanded, which limits flexibility.

Thanks!（sorry for using AI translate）

terashy commented on 2025-11-04 11:13 (UTC) (edited on 2025-11-04 11:19 (UTC) by terashy)

Is there an official fix for Extensions not showing in Extensions? I experience the same issue now. The problem leads addition to not be able to add or remove Extensions.

Post from jongeduard: ` jongeduard kommentierte 2025-10-26 13:15 (CET) (geändert am 2025-10-26 13:19 (CET) von jongeduard) Something seems wrong with the latest update.

Extensions are broken. Nothing is shown and it keeps searching forever.

When I downgrade to a previous version, everything works again. `

Icelk commented on 2025-11-03 09:02 (UTC)

@jongeduard

Great idea! I must have misremembered about the vscodium-bin-features, sorry!

jongeduard commented on 2025-11-02 19:49 (UTC) (edited on 2025-11-02 19:50 (UTC) by jongeduard)

@Icelk

Thanks for your reply. :)

I've posted a question about it in vscodium-features (without the 'bin'), which is supposed to be working with vscodium-bin but which turns out not to (error on install).

The last notification e-mail I've found from vscodium-bin-features is from March this year, so that's much shorter than 2 years ago.

Icelk commented on 2025-11-01 15:47 (UTC)

@jongeduard

Nice that you solved it :) I don't believe there's anything I can do; I think that package was removed at least 2 years ago.

jongeduard commented on 2025-10-31 12:23 (UTC) (edited on 2025-10-31 12:25 (UTC) by jongeduard)

@Icelk Thanks. I think I have found the source of the problem: I had vscodium-bin-features installed and that is currently breaking functionality. It isn't even on the AUR anymore as it seems.

After removing that from my system everything works fine again.

Self-built vscodium works fine as well.

Icelk commented on 2025-10-29 15:47 (UTC)

@jongeduard Does this also occurr when downloading vscodium and building it yourself / installing it directly from the VSCodium Github? Or is it specific to this binary package?

jongeduard commented on 2025-10-26 12:15 (UTC) (edited on 2025-10-26 12:19 (UTC) by jongeduard)

Something seems wrong with the latest update.

Extensions are broken. Nothing is shown and it keeps searching forever.

When I downgrade to a previous version, everything works again.

Icelk commented on 2025-06-19 18:29 (UTC)

:)

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 30 Next › Last »