vscodium
vscodium copied to clipboard
The editor crashed when starting
The editor crashed when I tried to start it.
-
I'm not sure This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
-
[x] I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.
Details
PID: 10718 (codium)
UID: 1000 (gordonzhang)
GID: 1000 (gordonzhang)
Signal: 11 (SEGV)
Timestamp: Tue 2024-04-30 19:13:42 CST (3min 26s ago)
Command Line: $'/app/share/codium/codium --extensions-dir --ozone-platform=x11 --unity-launch /home/gordonzhang/.var/app/com.vscodium.codium/data/codium/extensions'
Executable: /app/share/codium/codium
Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/app-flatpak-com.vscodium.codium-10680.scope
Unit: [email protected]
User Unit: app-flatpak-com.vscodium.codium-10680.scope
Slice: user-1000.slice
Owner UID: 1000 (gordonzhang)
Boot ID: 36b31dc5f32b40be99d5bd1fbcb07dcc
Machine ID: 94299471b52f483980cabb30285b7e3d
Hostname: 192.168.2.109
Storage: /var/lib/systemd/coredump/core.codium.1000.36b31dc5f32b40be99d5bd1fbcb07dcc.10718.1714475622000000.zst (present)
Size on Disk: 3.2M
Message: Process 10718 (codium) of user 1000 dumped core.
Stack trace of thread 19:
#0 0x00007fe6da462ae4 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x90ae4)
#1 0x000055c9d6d804ee n/a (/app/share/codium/codium + 0x23a84ee)
#2 0x000055c9d6f0d905 n/a (/app/share/codium/codium + 0x2535905)
#3 0x000055c9d6f4914e n/a (/app/share/codium/codium + 0x257114e)
#4 0x000055c9d6e6682e n/a (/app/share/codium/codium + 0x248e82e)
#5 0x000055c9d6e668ee n/a (/app/share/codium/codium + 0x248e8ee)
#6 0x000055c9d94f57f7 n/a (/app/share/codium/codium + 0x4b1d7f7)
#7 0x000055c9d94f595e n/a (/app/share/codium/codium + 0x4b1d95e)
#8 0x000055c9d94f9e69 n/a (/app/share/codium/codium + 0x4b21e69)
#9 0x000055c9d94f99a8 n/a (/app/share/codium/codium + 0x4b219a8)
#10 0x000055c9d94f541e n/a (/app/share/codium/codium + 0x4b1d41e)
#11 0x000055c9d70a71b4 n/a (/app/share/codium/codium + 0x26cf1b4)
#12 0x000055c9d70a8a8e n/a (/app/share/codium/codium + 0x26d0a8e)
#13 0x000055c9d70a886f n/a (/app/share/codium/codium + 0x26d086f)
#14 0x000055c9d70a60de n/a (/app/share/codium/codium + 0x26ce0de)
#15 0x000055c9d70a61e6 n/a (/app/share/codium/codium + 0x26ce1e6)
#16 0x000055c9d6d860d9 n/a (/app/share/codium/codium + 0x23ae0d9)
#17 0x00007fe6dbf9830b n/a (/app/lib/libzypak-preload-host-spawn-strategy.so + 0xad30b)
#18 0x00007fe6da3fa08a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2808a)
#19 0x00007fe6da3fa14b n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2814b)
#20 0x00007fe6dbf9859d n/a (/app/lib/libzypak-preload-host-spawn-strategy.so + 0xad59d)
#21 0x000055c9d699a02a n/a (/app/share/codium/codium + 0x1fc202a)
ELF object binary architecture: AMD x86-64
Desktop (please complete the following information):
- OS: Fedora Workstation 40
- Architecture x86-64
- Version 1.87.2.24072
- App Manager Flatpak
- Sandboxed Flatpak
System information
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4400
Manufacturer: LENOVO
Product Name: 20AMA4DJCD
System Version: ThinkPad X240
It seems like this problem only appears when I'm using KDE.
I'm also on Fedora 40 with KDE Plasma 6, and I can reproduce the crash using flatpak VSCodium (which is what you seem to be using as well).
I tried running VSCodium in Hyprland, and there was no crash there.
However, running flatpak run com.vscodium.codium --ozone-platform=wayland
inside a terminal in KDE allows the app to launch successfully.
I'm not sure if this is a flatpak issue or if it's also an issue with the rpm, as I haven't tried the rpm version yet. If it's flatpak only we should probably move this issue to https://github.com/flathub/com.vscodium.codium
Maybe related: https://github.com/flathub/com.vscodium.codium/issues/321#issuecomment-2089606662 @noonsleeper suggests that maybe the update on your flatpak setup is not changed to the new defaults Can you try the commands he provides? Thx
Thanks for the link @daiyam
Unfortunately, the commands didn't work. I'll post the error log there.
Hi @GordonZhang2024, I recently fix the wayland checking at the startup to be compatible with KDE6. Can you update to latest version on flatpak version and try if it is working for you again?
It works! Thank you very much! @noonsleeper