Issues with specific extensions

[friday]

If you can't install a specific extension or are having other issues with it, please report the issue on the extension's Github page, not here.

Make sure you read their instructions on installing the extension first. They often need you to perform manual steps to install dependencies. @brpaz made a nice static website that explains this: https://ulauncher-extension-doesnt-install-and-now.netlify.app/

When it comes to extension in general, we will try to improve the user experience with these errors, so it's more apparent for users what goes wrong and how they can fix it. Version 5.7.5 did this (as shown above), but it was not meant to be a complete solution. We are also considering supporting a list of dependencies such as requirements.txt either for showing them to the user or installing automatically using virtual envs for Python dependencies.

For binary dependencies this is more complicated. We can't install them automatically, nor control or check the version. Even checking if they're installed can be tricky. Notoriously fd uses the same name as fd, and the former way more popular fd had to be named fdfind in the debian packages because the latter came first. To check if fd is installed you would have to check fd and fdfind, but if you find fd, you still wouldn't know it's the right one.

If we add a method for extensions to check for binary dependencies, they could handle cases like this, return a list of missing dependencies, and Ulauncher could show a warning.

Also see discussion in #273, although it hasn't been updated for a while.

For the GTK 4 compatibility issue, a fix has been merged, and it will be in the next release.

Thank you for understanding.