Open necrosisy opened 1 year ago
I am having the same/quite similar issue, on KDE Plasma.
For me, setting the environment variable NO_CHROME_KDE_FILE_DIALOG=1
provides a simple workaround.
Same issue here with latest AppImage on Slackware 15.0 with KDE Plasma
(codium:6977): Gtk-WARNING **: 08:54:09.416: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
[main 2023-08-03T05:54:09.891Z] update#ctor - updates are disabled as there is no update URL
[main 2023-08-03T05:54:10.936Z] vscode-file: Refused to load resource /tmp/.mount_VSCodiclrmjz/usr/share/codium/resources/app/extensions/theme-seti/icons/seti.woff from vscode-file: protocol (original URL: vscode-file://vscode-app/tmp/.mount_VSCodiclrmjz/usr/share/codium/resources/app/extensions/theme-seti/icons/seti.woff)
(codium:6977): Gtk-WARNING **: 08:54:12.602: Could not find the icon 'document-open-recent-symbolic-ltr'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
http://icon-theme.freedesktop.org/releases
**
Gtk:ERROR:../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Aborted
Using NO_CHROME_KDE_FILE_DIALOG=1
doesn't work for me.
Same on Ubuntu 23.10
Same on Manjaro KDE Plasma,
$ cat /etc/lsb-release
DISTRIB_ID="ManjaroLinux"
DISTRIB_RELEASE="23.0.4"
DISTRIB_CODENAME="Uranos"
DISTRIB_DESCRIPTION="Manjaro Linux"
$ vscodium --version
1.83.1
36d13de33ac0d6c684f10f99cff352e2f58228b3
x64
$ uname -a
Linux {REDACTED} 6.1.55-1-MANJARO #1 SMP PREEMPT_DYNAMIC Sat Sep 23 12:13:56 UTC 2023 x86_64 GNU/Linux
$ sudo pacman -Syyu
[sudo] password for {REDACTED}:
:: Synchronizing package databases...
core 144.7 KiB 433 KiB/s 00:00 [######################] 100%
extra 8.6 MiB 16.4 MiB/s 00:01 [######################] 100%
community 29.0 B 966 B/s 00:00 [######################] 100%
multilib 145.1 KiB 3.54 MiB/s 00:00 [######################] 100%
:: Starting full system upgrade...
there is nothing to do
Using NO_CHROME_KDE_FILE_DIALOG=1
does not work for me.
This crashes on both folder and file opening -- usually when I try to navigate to the home folder in the dolphin dialog box.
Same issue here (think it is a sudden issue as I used this before without issue)
OpenSuse Tumbleweed on Plasma 5 with the package installed from the VSCodium repos (not sure if i used an RPM at the very start to install it and that added the repo)
I have NOT tried the flatpak version on here
I tried a fresh profile too that looked promising but as soon as I go to open something ... it crashed
tried "vscodium" from a termnial but as soon as the GUI loads for VSCodium it goes back to a prompt so i couldn't see any output messages about what i was expecting it to complain about.
update: tried the flatpak (I do see that is "unofficial" and not meant for support here if i recall... just stating the following) and it does the exact same thing
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
debian 12 1.89 every release
Hangs for me on Fedora 40, VSCodium 1.90 about the half the time when I open a folder on the main screen.
Describe the bug vscodium crashes after opening folder in main interface
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
To Reproduce Steps to reproduce the behavior:
Expected behavior Folders can be opened using the system file manager
Screenshots
Desktop (please complete the following information):
Linux archlinux 6.2.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 13 Mar 2022 17:02:08 +0000 x86_64 GNU/Linux
Additional context The following is the system log