Where did linux install Ver 26.1?

[Martin Lewicki]

Have  v24.4 already installed in /usr/share/stellarium/ 

Downloaded and installed 26.1 as "upgrade"  flatpack from repository. Run from the new 26.1  icon Ok. Some custom settings it copied from the 24.4, others like my extra landscapes are ignored.

So I thought I could manually copy them over to the  26.1. But I could not find the location of 26.1 anywhere in the folders. Is it hidden or what? It mean there are now 2 Stellarium versions occupying the system? Because I can open both versions separately

I only wanted to upgrade!

Linux Mint 22.2

Martin

[Alexander V. Wolf]

Hi!

ср, 3 июн. 2026 г. в 14:48, Martin Lewicki <martin....@gmail.com>:

Have  v24.4 already installed in /usr/share/stellarium/ 

Downloaded and installed 26.1 as "upgrade"  flatpack from repository. Run from the new 26.1  icon Ok. Some custom settings it copied from the 24.4, others like my extra landscapes are ignored.

Was it deb, snap or flatpak package?

 

So I thought I could manually copy them over to the  26.1. But I could not find the location of 26.1 anywhere in the folders. Is it hidden or what? It mean there are now 2 Stellarium versions occupying the system? Because I can open both versions separately

Hmm... please try to remove version 24.4

 

--

With best regards, Alexander

[Georg Zotti]

Does flatpack-stellarium (which is not our build AFAICS)  ignore ~/.stellarium so that your landscapes are not found? Never copy own landscapes into the program folder. You can also use envvar STEL_USERDIR. (See User Guide ch. 5+6 for config details. Should we [and if yes, please can someone in the know] describe idiosyncrasies of flatpack? It seems to become more widespread.) 

[Alexander V. Wolf]

Hi!

ср, 3 июн. 2026 г. в 15:13, Georg Zotti <georg...@univie.ac.at>:

Does flatpack-stellarium (which is not our build AFAICS)  ignore ~/.stellarium so that your landscapes are not found?

It's semi-our build - I can ping builders and I can edit the spec for builders, but I never used flatpack packages.

In any way mixing different packages which can read same standard directory is very bad idea.

[Georg Zotti]

I can use many versions from V0.20 to V26.1 from the same user dir. Occasionally I see complaints/warnings (e.g. DSO catalog versions), and there are some breaking changes when using RemoteSync, but sharing landscapes between versions is no problem. 

I just don't know what flatpack does in terms of sandboxing. Does it limit accessing the file system?

[Alexander V. Wolf]

Hi!

ср, 3 июн. 2026 г. в 15:52, Georg Zotti <georg...@univie.ac.at>:

I can use many versions from V0.20 to V26.1 from the same user dir. Occasionally I see complaints/warnings (e.g. DSO catalog versions), and there are some breaking changes when using RemoteSync, but sharing landscapes between versions is no problem. 

Because you're using standard deb packages or self-compiled binaries, which installed into /opt or /home/username

 

I just don't know what flatpack does in terms of sandboxing. Does it limit accessing the file system?

Mixing various types of packages with different "levels of sandboxing" can give weird results

[Martin Lewicki]

It seemed so messy I unistalled 26.1 and stick with  24.2 . Have  timeshifted back to yesterday. What if I uninstall 24.4, reboot and install 26.1 afresh? Don't mind re configuring again. In this case where would I expect to find 26.1. Should it be where 24.4 was (\usr\share\)

Martin