foxglove studio 2.2 core dump on Ubuntu 24.04 #988
-
LaunchProcess: failed to execvp: |
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 6 comments · 10 replies
-
How did you install the app? How are you launching the app? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I download the deb package and install. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Internal tracking issue: https://linear.app/foxglove/issue/FG-7374/foxglove-studio-22-core-dump-on-ubuntu-2404 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks, but is it possible for me to check the progress of this issue |
Beta Was this translation helpful? Give feedback.
All reactions
-
Any progress on this issue, please? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I was able to reproduce the segfault but have not yet identified a fix. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I suspect it is this upstream electron issue: electron/electron#41066 |
Beta Was this translation helpful? Give feedback.
All reactions
-
@jalenzz I am still looking into how we can better fix this issue. In the meantime I did find that launching the app with |
Beta Was this translation helpful? Give feedback.
All reactions
-
thanks |
Beta Was this translation helpful? Give feedback.
All reactions
-
We'll have a fix for this in the 2.4.0 release as part of the .deb install process. |
Beta Was this translation helpful? Give feedback.
All reactions
-
thanks |
Beta Was this translation helpful? Give feedback.
All reactions
-
This issue is resolved in the latest release. You no longer have to use the workaround to open the app. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I've just installed the latest version, and it seems like a regression bug:
Packages installed from debs, accordingly to current documentation. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Which deb did you install? amd64? arm64? we tried with the latest arm64 deb and were not able to reproduce this issue. Also note that this discussion was about ubuntu 24.04 which specifically has new behavior with system security. Ubuntu 22.04 did not have such behavior unless you've configured your system differently. Can you reproduce this on a stock ubuntu 22.04 install? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I've tried
Although i'm using custom ubuntu22.04 docker with nvidia drivers, it's easly reproducable in standard ros2:humble docker:
log
docker build -f Dockerfile . #1 [internal] load build definition from Dockerfile #2 [internal] load metadata for docker.io/library/ros:humble #3 [internal] load .dockerignore #4 [1/5] FROM docker.io/library/ros:humble #5 [2/5] RUN if id -u 1000 ; then userdel #6 [3/5] RUN groupadd --gid 1000 USERNAME && useradd --uid 1000 --gid 1000 -m USERNAME && apt-get update && apt-get install -y sudo && echo USERNAME ALL=(root) NOPASSWD:ALL > /etc/sudoers.d/USERNAME && chmod 0440 /etc/sudoers.d/USERNAME #7 [4/5] RUN apt-get update && apt-get upgrade -y #8 [5/5] RUN apt-get install -y python3-pip #9 exporting to image 1 warning found (use docker --debug to expand):
(base) gigi@GiGis:~$ docker run -it ros2:humble bash Cannot write to ‘foxglove-studio-latest-linux-amd64.deb’ (Success). foxglove-studio-latest-linux-amd64.deb 100%[=====================================================================================================>] 80.63M 24.3MB/s in 4.2s 2025-01-11 11:32:07 (19.3 MB/s) - ‘foxglove-studio-latest-linux-amd64.deb’ saved [84551764/84551764] USERNAME@94281f1db7ae:/tmp$ sudo apt install ./foxglove-studio-.deb |
Beta Was this translation helpful? Give feedback.
All reactions
-
Foxglove is not designed or expected to run in a docker container. This is not a workflow we support. |
Beta Was this translation helpful? Give feedback.
@jalenzz I am still looking into how we can better fix this issue. In the meantime I did find that launching the app with
foxglove-studio --no-sandbox
seems to work. I think it disables some sandboxing/security aspects to launch the app this way so that's up to you on whether you want to use this approach or wait for a different fix.