Package Details: vscodium-bin 1.95.3.24321-3

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: sperg512 (Icelk)
Last Packager: Icelk
Votes: 311
Popularity: 6.11
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2024-11-26 20:34 (UTC)

Pinned Comments

sperg512 commented on 2021-05-12 00:31 (UTC) (edited on 2024-06-04 15:14 (UTC) by sperg512)

@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 .. 25 Next › Last »

jronald commented on 2024-10-17 03:13 (UTC) (edited on 2024-10-17 03:25 (UTC) by jronald)

If add "~/.config/codium-flags.conf" with contents as below, everything is ok

--enable-wayland-ime

jronald commented on 2024-10-16 09:52 (UTC)

@Icelk without ime, i.e. without option "--enable-wayland-ime", everything is ok, as far as I see.

Icelk commented on 2024-10-15 08:09 (UTC)

@jronald just to confirm, that option doesnt mess things up for users not using IMEs?

jronald commented on 2024-10-15 03:42 (UTC) (edited on 2024-10-15 04:34 (UTC) by jronald)

It needs to add "--enable-wayland-ime" for input method (fcitx5 in my case) in codium-wayland to work.

But after adding "--enable-wayland-ime" to "codium-wayland.desktop" as below,

--enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland --enable-wayland-ime %F

"Open With VSCodium - Wayland" in context menu of KDE Dolphin doesn't work. Without "--enable-wayland-ime", it works.

jronald commented on 2024-10-15 03:29 (UTC)

vscdoium-wayland startup param not available, as in "/usr/share/applications/codium-wayland.desktop"

$ codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

see2night commented on 2024-09-28 02:47 (UTC) (edited on 2024-09-28 02:50 (UTC) by see2night)

The fcitx5 input method cannot be used in native wayland vscodium. The --enable-wayland-ime flag dose not worked

Icelk commented on 2024-08-28 06:19 (UTC)

@jongeduard It's my understanding that the -debug packages are almost never used. AUR helpers don't install them. I have no clue about why conflicts arise nor do I have the time to investigate. If someone can point me to a resource or do the investigation that'd be appreciated.

jongeduard commented on 2024-08-13 17:11 (UTC) (edited on 2024-08-16 11:24 (UTC) by jongeduard)

Edit: Disabling debug package generation by default in makepkg.conf works around this problem, if you don't need those packages (I believe I don't so it's fine). However, I still think is surprising that things can conflict this way.

Hi! I am suddenly facing a very strange problem with a conflict between 2 completely unrelated AUR packages, although they're both Electron apps (not certain if that's related in any way though, but if it is, possibly a lot more people are going to have troubles), namely:

  • threema-desktop-bin-debug

  • vscodium-bin-debug (the one here)

Here is the output, I am just running makepkg -Ccsi here (and with the LANG set to C for English instead of Dutch):

eduard@eduard-desktop ~/Software/AUR/vscodium-bin (git)-[master] % LANG=C makepkg -Ccsi
==> WARNING: A package has already been built, installing existing package...
==> Installing package vscodium-bin with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...

Package (2)         New Version     Net Change

vscodium-bin        1.92.1.24225-1  341.87 MiB
vscodium-bin-debug  1.92.1.24225-1    8.02 MiB

Total Installed Size:  349.89 MiB

:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring                                                                                                                                                   [##############################################################################################################] 100%
(2/2) checking package integrity                                                                                                                                                 [##############################################################################################################] 100%
(2/2) loading package files                                                                                                                                                      [##############################################################################################################] 100%
(2/2) checking for file conflicts                                                                                                                                                [##############################################################################################################] 100%
error: failed to commit transaction (conflicting files)
vscodium-bin-debug: /usr/lib/debug/.build-id/04/e9960947a38ced0a87421a6f198b9caf43dc3f exists in filesystem (owned by threema-desktop-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/04/e9960947a38ced0a87421a6f198b9caf43dc3f.debug exists in filesystem (owned by threema-desktop-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/37/851ad3790029c78d20ee4b4761055d5ad5dab6 exists in filesystem (owned by threema-desktop-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/37/851ad3790029c78d20ee4b4761055d5ad5dab6.debug exists in filesystem (owned by threema-desktop-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/68/3278eba471e7069eeddf5a8270d9a201ea88da exists in filesystem (owned by threema-desktop-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/68/3278eba471e7069eeddf5a8270d9a201ea88da.debug exists in filesystem (owned by threema-desktop-bin-debug)
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).
==> Cleaning up...
14 eduard@eduard-desktop ~/Software/AUR/vscodium-bin (git)-[master] %

If I remove the other debug package, I can install this one and installing the other one will give the same errors. So it seems actually a mutual conflict.

The issue is that I have a self-written automated script to update all my installed AUR packages (I am not even using an actual AUR helper, but I can imagine that those AUR helpers will run into the same problem).

jongeduard commented on 2024-07-07 00:16 (UTC) (edited on 2024-07-07 00:17 (UTC) by jongeduard)

@Icelk Ok, thanks for confirming. Never mind. I see that none of my other Arch installations have issues with it. So then I assume you're right. :)

Icelk commented on 2024-07-06 20:06 (UTC)

@jongeduard Ok. The change was just a normal commit, so I believe it's on your part.

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