From 0d0cdbb7b191f1257306197609fc74a4babf97bf Mon Sep 17 00:00:00 2001 From: Mathieu Westphal Date: Sun, 14 May 2023 08:31:44 +0200 Subject: [PATCH 1/3] Adding doc --- doc/user/INSTALLATION.md | 2 +- doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md | 11 +++-------- 2 files changed, 4 insertions(+), 9 deletions(-) diff --git a/doc/user/INSTALLATION.md b/doc/user/INSTALLATION.md index f8ea15b708..3d5269e004 100644 --- a/doc/user/INSTALLATION.md +++ b/doc/user/INSTALLATION.md @@ -12,7 +12,7 @@ ## Alternatives -You can find other (older, smaller, checksum, RCs) release related packages and files on the [releases page](https://github.com/f3d-app/f3d/releases). +You can find other (headless, older, smaller, checksum, RCs) release related packages and files on the [releases page](https://github.com/f3d-app/f3d/releases). You can also find there the [nightly release](https://github.com/f3d-app/f3d/releases/tag/nightly) to test the development version of F3D. See the [desktop integration](DESKTOP_INTEGRATION.md) section in order actually integrate the binary release in your desktop. Alternatively, you can build F3D yourself by following the [build](../dev/BUILD.md) guide. diff --git a/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md b/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md index d616da23ff..466dc670f4 100644 --- a/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md +++ b/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md @@ -50,15 +50,10 @@ With some C++ STD library version, explicit linking to `stdc++fs` is not support * If no formats have working thumbnails, then it is an issue with the `f3d-plugin-xxx.thumbnailer` files. * If only big file do not have thumbnails, this is intended, you can modify this behavior in the `thumbnail.d/10_global.json` configuration folder using the `max-size` option. -Some file managers (eg: Nautilus) are using sandboxing for thumbnails, which the F3D binary release does not support as it needs +Some file managers (eg: Nautilus) are using sandboxing for thumbnails, which the F3D standard binary release does not support as it needs access to the Xorg server for rendering anything. -A work around to this issue is to use a virtual Xorg server like Xephyr or Xvfb in all the `f3d-plugin-xxx.thumbnailer` files. -Here is how your `Exec` line should look to use `xvfb-run`. Keep in mind running xvfb can be very slow. - -`Exec=xvfb-run f3d --dry-run -sta --no-background --output=%o --resolution=%s,%s %i` - -Another workaround is to build VTK with EGL or osmesa support and then build F3D yourself against -this custom VTK build. +In that case, you want to use the headless version of F3D that rely on EGL instead of Xorg, available in the [releases page](https://github.com/f3d-app/f3d/releases). +If you use the portable archive, make sure to extract it somewhere the sandboxing system has access to, eg: `/usr/opt/`. ## Windows From 0670d737357cbebd37bb8b64ba5780625ef87725 Mon Sep 17 00:00:00 2001 From: Mathieu Westphal Date: Sun, 14 May 2023 10:27:56 +0200 Subject: [PATCH 2/3] Update doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md Co-authored-by: snoyer --- doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md b/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md index 466dc670f4..1471ca470e 100644 --- a/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md +++ b/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md @@ -51,7 +51,7 @@ With some C++ STD library version, explicit linking to `stdc++fs` is not support * If only big file do not have thumbnails, this is intended, you can modify this behavior in the `thumbnail.d/10_global.json` configuration folder using the `max-size` option. Some file managers (eg: Nautilus) are using sandboxing for thumbnails, which the F3D standard binary release does not support as it needs -access to the Xorg server for rendering anything. +access to the Xorg server to render anything. In that case, you want to use the headless version of F3D that rely on EGL instead of Xorg, available in the [releases page](https://github.com/f3d-app/f3d/releases). If you use the portable archive, make sure to extract it somewhere the sandboxing system has access to, eg: `/usr/opt/`. From c6d5cf2272174b96f326e1e777975cf59ecb6fce Mon Sep 17 00:00:00 2001 From: Mathieu Westphal Date: Sun, 14 May 2023 10:28:05 +0200 Subject: [PATCH 3/3] Update doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md Co-authored-by: snoyer --- doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md b/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md index 1471ca470e..6449b9b205 100644 --- a/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md +++ b/doc/user/LIMITATIONS_AND_TROUBLESHOOTING.md @@ -53,7 +53,7 @@ With some C++ STD library version, explicit linking to `stdc++fs` is not support Some file managers (eg: Nautilus) are using sandboxing for thumbnails, which the F3D standard binary release does not support as it needs access to the Xorg server to render anything. In that case, you want to use the headless version of F3D that rely on EGL instead of Xorg, available in the [releases page](https://github.com/f3d-app/f3d/releases). -If you use the portable archive, make sure to extract it somewhere the sandboxing system has access to, eg: `/usr/opt/`. +If you use the portable archive, make sure to extract it somewhere the sandboxing system has access to, eg: Nautilus uses `bwrap` and gives it access to `/usr` but not to `/opt`. ## Windows