New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions can not be installed #5546
Comments
As a quick follow up, I realized after writing this that I could just modify the packaging to install Slicer into my |
If you install Slicer as an administrator then you need to install all the extensions and Python packages, too. See some more explanation here: https://discourse.slicer.org/t/unable-to-install-extensions-when-slicer-is-installed-in-system-location/16588 |
Closing this, as the change was intended. I've added a note to the migration guide. |
Hi all,
I've been using Slicer on Arch Linux without a problem via the
3dslicer-bin
package (which just downloads the binary from the slicer site and installs it on the system) for quite some time. You can see the fullPKGBUILD
script (simplybash
with some variables for use by the package manager) here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=3dslicer-binHowever, I'm hitting an issue with the extension manager in recent releases.
Previously, it seems Slicer happily installed extensions into
$XDG_CONFIG_HOME/NA-MIC/Extensions-<somenumbers>
. In the newest release, it seems like Slicer is attempting to write Extensions to/opt/3dslicer/NA-MIC/Extensions-29738
. Since I'm usually running Slicer as a normal user but have it installed system-wide in/opt/
this fails due to the lack of permission to change/opt
. Ideally, I'd like to avoid running Slicer with fullsudo
powers and have it continue to use the old user-level directories for extensions. Unfortunately, this also seems to be stopping me from effectively changing my user preferences.Steps to reproduce
Install Slicer on Arch via the AUR PKGBUILD (see: https://slicer.readthedocs.io/en/latest/user_guide/getting_started.html#archlinux). Then launch the extension manager.
Expected behavior
I'd expect another folder to show up with the new Slicer release. My current NA-MIC user directory looks like this:
but Slicer is looking for
/opt/3dslicer/NA-MIC/Extensions-29738
when I would expect it to create a new entry there.Environment
Slicer:
Additional info on environment:
The text was updated successfully, but these errors were encountered: