-
Notifications
You must be signed in to change notification settings - Fork 209
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
libgvfscommon.so: undefined symbol: g_task_set_name #536
Comments
It's been a long time, and I forgot what I wanted to express at the beginning. Pay attention to see: "Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so" The plugin works with the gio library, vim.appimage comes bundled with libgio, but the gio plugin is missing. So the gio plugin on the host will call the libgio.so file bundled with vim.appimage. |
Well, we certainly cannot expect users to uninstall anything before running the appimage, right?
I tried packaging gio modules in chrisbra/vim-appimage-1@560ae43 but that did not fix it. However, Are you saying we should rather blacklist what, libgio? Which one exactly? Thanks for helpful comments! |
I think it's the environment variables. Try GIO_MODULE_DIR |
Oh, that seems to work: But now i noticed, that this error isn't critical, it's just an error. The actual problem is the
Which seems to come from the appimage gvim unable to load some of my icon signs Anyhow, it works now when removing this plugin and I can live without the signs plugin. It should be fine and is no issue for this repo here. So let me also package the gio plugins and close this issue here. Thanks! |
https://gitlab.gnome.org/GNOME/gtk/-/blob/main/docs/reference/gtk/running.md Maybe you must package gdk modules : GDK_PIXBUF_MODULE_FILE |
Hey,
I am seeing the following behaviour when downloading the Vim-Appimage on my Debian Bullseye system:
Over at vim/vim-appimage#32 they mention this is a packaging error, missing files
/usr/lib/x86_64-linux-gnu/gio/modules/*
could that be?The text was updated successfully, but these errors were encountered: