Envision: discourage AppImageLauncher

This commit is contained in:
hypevhs 2025-03-28 10:39:55 -05:00
parent 64a7b7196b
commit ae430abd23

View file

@ -71,6 +71,14 @@ For example, if you installed WlxOverlay-S from AUR or built it from source, you
Now starting the profile will also start your custom or AUR version of WlxOverlay-S. Now starting the profile will also start your custom or AUR version of WlxOverlay-S.
### Plugin troubleshooting
On some systems, a built-in plugin may not launch. This can happen for a number of reasons, but one in particular is so obtuse that it's worth a mention:
Please *uninstall* AppImageLauncher. It intercepts the normal AppImage starting behavior in a dirty way that we can't predict.
You can tell if you are affected if, when you run the WlxOverlay-S AppImage in terminal (whether in plugin form in `~/.local/share/envision/plugins`, or downloaded directly from GitHub), you only get the output `execv error: No such file or directory`.
## Experimental feature settings ## Experimental feature settings
The following resources can be entered into your Envision profile repo and branch settings to enable early access to code before it's fully upstream in Monado itself. To enable these feature sets, simply clone your profile, edit it with these settings, then build. The following resources can be entered into your Envision profile repo and branch settings to enable early access to code before it's fully upstream in Monado itself. To enable these feature sets, simply clone your profile, edit it with these settings, then build.