Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCodium AppImage will not run after latest update #854

Closed
2 tasks done
iSmashButtons opened this issue Sep 28, 2021 · 14 comments
Closed
2 tasks done

VSCodium AppImage will not run after latest update #854

iSmashButtons opened this issue Sep 28, 2021 · 14 comments
Labels
bug Something isn't working

Comments

@iSmashButtons
Copy link

iSmashButtons commented Sep 28, 2021

Describe the bug
VSCodium AppImage conflicts with packages on Manjaro and will not run. Trying to execute AppImage from GUI results in no action. Executing AppImage from terminal reveal error:

codium: symbol lookup error: /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

Please confirm that this problem is VSCodium-specific

  • This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
    Tested this by installing Code-OSS from Arch community repository
    Also set up new Manjaro installation on another computer and tried running the AppImage there. Had the same result.

Please confirm that the issue/resolution isn't already documented

To Reproduce
Steps to reproduce the behavior:

  1. Run Manjaro VM
  2. Update packages to latest version
  3. Execute VSCodium AppImage

Expected behavior
Application should run

Desktop (please complete the following information):

  • OS: Manjaro Linux
  • Architecture: x86_64
  • Version: n/a

Additional context
After updating my system packages yesterday, trying to execute the AppImage as normal (from GUI/rofi) resulted in no action. Executing AppImage from the terminal produced this error:

codium: symbol lookup error: /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

Found this Arch forum post with a similar problem for a different AppImage

Patched VSCodium AppImage with glib2 version 2.68.4.

When executing the patched AppImage a similar error occurs, but now it is a different library/package:

codium: symbol lookup error: /usr/lib/libtracker-sparql-3.0.so.0: undefined symbol: sqlite3_expanded_sql

@iSmashButtons iSmashButtons added the bug Something isn't working label Sep 28, 2021
@Z35hLy48k
Copy link

I had the exact same error,
Patched VSCodium with glib2 version 2.70.0

When I executed the patched Appimage, i got this error :
codium: error while loading shared libraries: libffi.so.8: cannot open shared object file: No such file or directory

However you can install the aur vscodium-bin (pamac install vscodium-bin) package which works fine on Manjaro (at least for me)

@daiyam
Copy link
Member

daiyam commented Dec 17, 2021

Can you try VSCodium-1.63.2-1639774037.glibc2.17-x86_64.AppImage.zip?
I've been able to make it run under Arch and Fedora 34/35 while being built on Ubuntu 18.04.
The changes I've made can be found at #944.

@pkve
Copy link

pkve commented Dec 19, 2021

Can you try VSCodium-1.63.2-1639774037.glibc2.17-x86_64.AppImage.zip?

It also works on my OpenSUSE Tumbleweed. Thanks!

@TheAssassin
Copy link

See AppImage/AppImageKit#1162. Looks like something that needs to be fixed over at AppImageKit. Rebuilding the AppImage then should fix the issue.

@daiyam
Copy link
Member

daiyam commented Dec 31, 2021

The issue is due to the libraries libgmodule-2.0.so and libsqlite3.so. (AppImageCommunity/pkg2appimage#494 (comment))

@daiyam daiyam changed the title VSCodium AppImage will not run on Manjaro after latest update VSCodium AppImage will not run after latest update Dec 31, 2021
@nuno-silva
Copy link

I'm having this issue using VSCodium-1.63.2-1639700424.glibc2.17-x86_64.AppImage.

/tmp/.mount_codeeXHAOK/usr/share/codium/codium --unity-launch: symbol lookup error: /usr/lib64/libgio-2.0.so.0: undefined symbol: g_module_open_full

Using Gentoo Linux amd64 with glib-2.70.2.

Worked around it by downgrading to glib-2.68.4.

@daiyam
Copy link
Member

daiyam commented Feb 2, 2022

@nuno-silva Have you tried :

Can you try VSCodium-1.63.2-1639774037.glibc2.17-x86_64.AppImage.zip?

@nuno-silva
Copy link

@daiyam sorry mate, I can only run official releases from this repo. I see your PR #944 was already merged, so I'll wait until the next release :) thank you for your work.

@daiyam
Copy link
Member

daiyam commented Feb 4, 2022

The AppImage for 1.64 is working. Can you confirm? Thx

@nuno-silva
Copy link

Just confirmed VSCodium-1.64.0-1643956064.glibc2.17-x86_64.AppImage is working for me with both glib-2.68.4 and glib-2.70.2. Thank you

@eightfiftytwo
Copy link

eightfiftytwo commented Mar 4, 2022

Seems like it's happening again with VSCodium-1.65.0-1646384533.glibc2.17-x86_64.AppImage on Fedora Workstation 35.

sed: /tmp/.mount_VSCodiEfUYOJ/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by sed)
codium: /tmp/.mount_VSCodiEfUYOJ/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib64/libgio-2.0.so.0)
codium: /tmp/.mount_VSCodiEfUYOJ/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib64/libmount.so.1)
codium: /tmp/.mount_VSCodiEfUYOJ/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib64/libkrb5support.so.0)
codium: symbol lookup error: /lib64/libgobject-2.0.so.0: undefined symbol: g_date_copy

@daiyam
Copy link
Member

daiyam commented Mar 4, 2022

Yep! I have the same error...

@daiyam
Copy link
Member

daiyam commented Mar 4, 2022

I'm regenerating the AppImage with the fix.

@eightfiftytwo
Copy link

It's working! Thanks.

@daiyam daiyam closed this as completed Mar 5, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants