There is a new experimental package format for ROOT, based on the Snap package manager from Canonical. This package can be ideal for new ROOT users, new Linux users, or people whose ROOT requirements might be entirely satisfied with an immutable container image.
A follow-up, more complete blog post to the original announcement here in the forum. Thanks @James-Carroll!
(Edited this post since I’ve noticed it appears under the blog feed and I’d rather not overburden it 
)
The main things I’m looking into at the moment is getting CUDA working, considering the possibility of Tensorflow in the default package (for Keras/TMVA) and identifying where the sandbox is causing issues. Particularly this last bit is the one that presents the most complex problem. Otherwise the snap should hopefully only lag behind the latest releases by a few days at most, so if it’s suitable for you already it should be plain sailing going forward. If it isn’t, please drop feedback and I can evaluate it and hopefully improve this for everyone 
Hi @James-Carroll , just wondering: what C++ standard is the Snap package compiled with? We should probably add this information at Installing ROOT - ROOT and Install ROOT Framework for Linux using the Snap Store | Snapcraft .
Both the 6-22 and 6-24/latest channels are C++17, being the latest standard GCC 9 claims to be stable with, new releases will probably remain that way until the snap rebases on Ubuntu 22.04.
I’ll add that information to the store listing, but CERN has a service account that has write access to the snap and can change its description, so if you ever wanted to adjust something yourselves then feel free to use it.
Hi @James-Carroll ,
I have the snap version of ROOT 6.27, and I would like to edit the .rootrc file to change the default TBrowser to offline mode. However I cannot find where .rootrc is located. I made my own .rootrc in the home directory, and added the line of code to change the browser setting, but it didn’t work.
Where do I find this .rootrc file if I install via snap?
Thanks,
Clayton
Hello,
Most snaps (strict snaps, left to their defaults) believe that $HOME is actually $HOME/snap/$snap-name/current, so for ROOT, you’d place the .rootrc file in $HOME/snap/root-framework/current/.rootrc
Great, this worked! Thanks
I was using the snap for root on Ubuntu 22_04 without problems. On Ubuntu 24_04 I am not authorized to use the graphics output (X11) I have to issue xhost+ first before the graphics is being displayed. This is annoying. How can I get around that problem (without xhost+ somewhere)
Answering myself: it looks as if in the snap.yaml in the plugs sectionthe wayland entry is missing.
Could you please reconfigure/rebuild the package
Hi,
Sorry for the long delay here. ROOT doesn’t have Wayland socket support implicitly so under most circumstances I’d expect that it isn’t needed, however I imagine this might be a quirk with the interaction between Wayland and X11 (via XWayland), and in any case, it’s a secure plug to add by design, so I’ve no problem with it.
I’ve been a bit behind on the ROOT snap recently due to a combination of life factors (and computer factors to boot). I’ll aim to get 6.32 packaged in the next week or so, with an upgrade to the Core24 snap that’s now stable (So new GCC/Python/etc). There’s a lot to test, but actually the Wayland plug is genuinely just a one liner.
Sorry for not picking this up sooner, the forum swallowed the post without notifying me and the Github issue is on the main ROOT tracker whilst the snap is still unofficial and logged elsewhere (I.E my own private account), meaning I’d only seen this now. But it will be done!
James
The wayland plug is now active by default on the latest channel, which is just upgraded to v6.30.08
I’ll rebuild releases between 6-22 and 6-28 throughout the next 48 hours and then 6.32 with the newer compilers later this week. For now though, that should mean whoever has been having Wayland related issues should stop seeing them imminently, as the automatic updates kick in.