snap download snapd --revision=24724 sudo snap ack snapd_24724.assert sudo snap install snapd_24724.snap sudo sudo snap refresh --hold snapd
Just wanted to add that this fixed my ability to boot chromium on my custom (JP 6.2.1, r36.4.4) kernel/bootloader on an Orin NX. I also snap remove(d) and (re)installed chromium before testing.
Thanks for posting the solution.
@silenzio777 It worked!! Thanks bro!
However, I didn’t save any backups. So, what I did was installing snap with the following command on a working kernel. (In my case, the unbootable kernel is in NVMe and I have another one running in eMMC)
Then replace those problematic v2.70 snap folders mentioned by @silenzio777 in my NVMe drive with the freshly installed ones.
After that, add the following and you are ready to go.
Thanks for the great troubleshooting and fixes, Kangalow!
You are welcome, I’m glad you got it to work. Remember to mark snap as hold so it doesn’t update again.
UPDATE:
It’s not work for me:
This is works!
$ sudo apt install --reinstall snapd=2.67.1+22.04 -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 545 not upgraded.
Need to get 25.0 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 snapd arm64 2.67.1+22.04 [25.0 MB]
Fetched 25.0 MB in 3s (7,199 kB/s)
(Reading database ... 320463 files and directories currently installed.)
Preparing to unpack .../snapd_2.67.1+22.04_arm64.deb ...
Unpacking snapd (2.67.1+22.04) over (2.67.1+22.04) ...
Setting up snapd (2.67.1+22.04) ...
snapd.failure.service is a disabled or a static unit not running, not starting it.
snapd.snap-repair.service is a disabled or a static unit not running, not starting it.
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
silenzio@jetsonnx:~/ros2_ws$ systemctl status snapd
● snapd.service - Snap Daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2025-07-16 18:01:24 MSK; 41s ago
TriggeredBy: ● snapd.socket
Main PID: 56492 (snapd)
Tasks: 17 (limit: 18452)
Memory: 327.3M
CPU: 21.969s
CGroup: /system.slice/snapd.service
└─56492 /usr/lib/snapd/snapd
Jul 16 18:01:24 jetsonnx systemd[1]: Started Snap Daemon.
Jul 16 18:01:45 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:01:46 jetsonnx snapd[56492]: snapmgr.go:611: cannot read snap info of snap "core22" at revision 1612: cannot find installed snap "core22" at revision 1612: missing file /snap/core22/1612/meta/snap.yaml
Jul 16 18:01:49 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:01:49 jetsonnx snapd[56492]: services.go:1152: RemoveSnapServices - disabling snap.snapd-desktop-integration.snapd-desktop-integration.service
Jul 16 18:02:04 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:02:04 jetsonnx snapd[56492]: services.go:1152: RemoveSnapServices - disabling snap.cups.cupsd.service
Jul 16 18:02:04 jetsonnx snapd[56492]: services.go:1152: RemoveSnapServices - disabling snap.cups.cups-browsed.service
Jul 16 18:02:05 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:02:06 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
DeepSeek is a genius! 8)
On shutdown or power up of the Jetson Orin Nano, I’ve noticed that snap updates so the revert does not stay. Is there a way I can force this ? Do I have
to disconnect from internet during boot up and shutdown every time ?
After you install the downgrade, what is the result of
snap info snapd
So bossman, I realised it kept taking me in a loop for 3 hours, the best fix is I removed the snap, I removed the selinux, and then rebooted the systemctl.
press enter to enter maintainance
this is what I did, and claude helped.
" After following JetsonHacks Chromium fix [Why Chromium Suddenly Broke on Jetson Orin (and How to Bring It Back) - JetsonHacks]
(snapd downgrade), system won’t boot - stuck in emergency mode with:
1. Access emergency shell:
bash
# Press Enter at "Press Enter for maintenance"
2. Remove SELinux completely:
bash
apt remove --purge selinux-utils policycoreutils
rm -rf /etc/selinux
3. Remove Snapd completely:
bash
apt remove --purge snapd squashfs-tools
rm -rf /snap /var/snap /var/lib/snapd /var/cache/snapd
rm -f /etc/systemd/system/snap-*.mount
4. Clean systemd:
bash
systemctl daemon-reload
systemctl reboot
bash
apt install firefox
# or
apt install chromium-browser
This gives you a working Jetson without the problematic security layers that break embedded systems."
Hope this helps. I dont know how much this is right but @Kangalow @DaneLLL please suggest this temp fix?
@schugh1 Which Jetson and JetPack version are you using?
=== Jetson Hardware ===
NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super
=== L4T/JetPack Version ===
R36 (release), REVISION: 4.4, GCID: 41062509, BOARD: generic, EABI: aarch64, DATE: Mon Jun 16 16:07:13 UTC 2025
KERNEL_VARIANT: oot
TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
=== Kernel Version ===
Linux ubuntu 5.15.148-tegra #1 SMP PREEMPT Mon Jun 16 08:24:48 PDT 2025 aarch64 aarch64 aarch64 GNU/Linux
=== CUDA Version ===
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Wed_Aug_14_10:14:07_PDT_2024
Cuda compilation tools, release 12.6, V12.6.68
Build cuda_12.6.r12.6/compiler.34714021_0
=== Architecture ===
arm64
| JetPack Version | L4T Version | Release Date |
|---|---|---|
| JetPack 6.2.1 | R36.4.4 | July 2025 |
| JetPack 6.2 | R36.4.0 | June 2025 |
| JetPack 6.1 | R36.3.0 | March 2025 |
| JetPack 6.0 | R36.2.0 | December 2024 |
| JetPack 5.1.3 | R35.5.0 | September 2024 |
I’m having Jetson Orin Nano, and I recently installed the image for the first time on ssd
=== Jetson Hardware ===
NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super
=== L4T/JetPack Version ===
TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
=== Kernel Version ===
Linux ubuntu 5.15.148-tegra #1 SMP PREEMPT Mon Jun 16 08:24:48 PDT 2025 aarch64 aarch64 aarch64 GNU/Linux
=== CUDA Version ===
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Wed_Aug_14_10:14:07_PDT_2024
Cuda compilation tools, release 12.6, V12.6.68
Build cuda_12.6.r12.6/compiler.34714021_0
=== Architecture ===
arm64
| JetPack Version | L4T Version | Release Date |
|---|---|---|
| JetPack 6.2.1 | R36.4.4 | July 2025 |
| JetPack 6.2 | R36.4.0 | June 2025 |
| JetPack 6.1 | R36.3.0 | March 2025 |
| JetPack 6.0 | R36.2.0 | December 2024 |
| JetPack 5.1.3 | R35.5.0 | September 2024 |
I have Jetson Orin Nano, just installed a image for the first time and had faced same issue
I have Jetson Orin Nano and JetPack 6.2.1, R36.4.4. which might be what caused the issue, hope we can update this without reinstalling everything
@schugh1 How did you upgrade to 6.2.1 ? Is this a fresh SD card install or SDK Manager install?
A default 6.2.1 36.4.4 install does not have selinux-utils or policycoreutils installed. Did you install your own security policies?
I installed using SDK Manager, the issue if i myself am using it for the first time, if you know how i can do installation right would be helpful, i not am not able to use the chromium or firefox but rest all is working, i think i am okay with new installation, if you can help me with that and exact steps would be helpful
I’ve only tested against a SD card install, maybe the SDK Manager does something different. Your response implies that you now have a working browser, and that it is a fix for the issue. Does your browser work? Are you booting from the SD card or a NVMe ?
I’m on nvme and the browser still doesn’t work, and haven’t fixed yet. I hope things works soon once there is a new update, please suggest if there is a particular config I must use and will install things rightly using SDK Manager.
also @DaneLLL please help if you know anything
Hi,
We are still working on a solution. For now, please run the manual steps to install system image:
And apply JetsonHacks’ solution:
Why Chromium Suddenly Broke on Jetson Orin (and How to Bring It Back) - JetsonHacks
So that snap is in old version.
Browers sloved! but dmesg still show squashfs and xattr errors …
sudo dmesg | grep -i “squashfs”
[ 0.150602] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 9.488482] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[ 9.603225] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[ 9.643441] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
Would you kindly assist as well? I’ve tried to reverse the snap multiple times, but I’m still having this problem. However, nothing changed.
How did you resolve these problems?