Speedup Lubuntu Boot Time

My Specs:
inxi -Fxxxz

System:
  Kernel: 5.15.0-52-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: LXQt 0.17.1 info: lxqt-panel wm: Openbox 3.6.1 vt: 1 dm: SDDM
    Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
  Type: Desktop Mobo: N/A model: N/A serial: <superuser required>
    BIOS: American Megatrends v: 080016 date: 02/02/2015
CPU:
  Info: dual core model: Intel Pentium Dual E2160 bits: 64 type: MCP
    smt: <unsupported> arch: Core Merom rev: D cache: L1: 128 KiB L2: 1024 KiB
  Speed (MHz): avg: 1758 high: 1795 min/max: N/A cores: 1: 1795 2: 1722
    bogomips: 7179
  Flags: ht lm nx pae sse sse2 sse3 ssse3
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics driver: i915 v: kernel
    ports: active: VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2a42
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 compositor: Compton v: 1 driver:
    X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
    s-diag: 414mm (16.3")
  Monitor-1: VGA-1 model: Acer S191HQL serial: <filter> res: 1366x768
    hz: 60 dpi: 85 size: 410x230mm (16.1x9.1") diag: 470mm (18.5") modes:
    max: 1366x768 min: 720x400
  OpenGL: renderer: Mesa Mobile Intel GM45 Express (CTG) v: 2.1 Mesa 22.0.5
    direct render: Yes
Audio:
  Device-1: Intel 82801I HD Audio driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-52-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e800 bus-ID: 03:00.0
    chip-ID: 10ec:8136 class-ID: 0200
  IF: ens35 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 298.09 GiB used: 23.73 GiB (8.0%)
  ID-1: /dev/sda vendor: Western Digital model: WD3200AVVS-63L2B0
    size: 298.09 GiB speed: 3.0 Gb/s type: N/A serial: <filter> rev: 3A01
    scheme: MBR
Partition:
  ID-1: / size: 292.35 GiB used: 23.73 GiB (8.1%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 512 MiB used: 365.4 MiB (71.4%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 67.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 192 Uptime: 1h 36m wakeups: 0 Memory: 1.89 GiB
  used: 1.25 GiB (66.2%) Init: systemd v: 249 runlevel: 5 Compilers: gcc: N/A
  Packages: 2038 apt: 2030 flatpak: 8 Shell: Zsh v: 5.8.1
  running-in: terminator inxi: 3.3.13

systemd-analyze blame

3min 4.063s apt-daily-upgrade.service
    27.081s udisks2.service
    26.755s logrotate.service
    25.761s networkd-dispatcher.service
    24.063s accounts-daemon.service
    13.373s dev-sda1.device
    12.048s avahi-daemon.service
    11.882s NetworkManager.service
    11.860s cups.service
    11.640s NetworkManager-wait-online.service
    11.582s polkit.service
    11.497s ModemManager.service
    10.521s gpu-manager.service
     9.921s thermald.service
     9.914s systemd-logind.service
     9.666s wpa_supplicant.service
     8.178s apport.service
     7.780s systemd-resolved.service
     6.699s systemd-journal-flush.service
     6.662s rsyslog.service
     6.162s ua-timer.service
     5.885s man-db.service
     5.437s e2scrub_reap.service
     4.119s apparmor.service
     3.912s systemd-udevd.service
     3.868s grub-common.service
     3.390s packagekit.service
     2.933s grub-initrd-fallback.service
     2.083s keyboard-setup.service
     2.017s systemd-modules-load.service
     1.819s systemd-sysusers.service
     1.712s systemd-udev-trigger.service
     1.692s e2scrub_all.service
     1.665s systemd-random-seed.service
     1.375s geoclue.service
     1.144s systemd-user-sessions.service
     1.093s systemd-journald.service
     1.066s user@1000.service
      978ms systemd-tmpfiles-setup-dev.service
      927ms lvm2-monitor.service
      926ms swapfile.swap
      905ms binfmt-support.service
      896ms setvtrgb.service
      876ms systemd-sysctl.service
      861ms fwupd-refresh.service
      855ms update-notifier-download.service
      736ms systemd-tmpfiles-clean.service
      660ms systemd-tmpfiles-setup.service
      651ms kerneloops.service
      565ms console-setup.service
      531ms plymouth-read-write.service
      434ms systemd-timesyncd.service
      422ms ufw.service
      359ms dev-hugepages.mount
      357ms dev-mqueue.mount
      355ms sys-kernel-debug.mount
      353ms sys-kernel-tracing.mount
      340ms kmod-static-nodes.service
      324ms modprobe@configfs.service
      322ms modprobe@drm.service
      319ms modprobe@fuse.service
      295ms sddm.service
      281ms systemd-update-utmp.service
      201ms upower.service
      143ms rtkit-daemon.service
      140ms systemd-remount-fs.service
       78ms proc-sys-fs-binfmt_misc.mount
       60ms modprobe@chromeos_pstore.service
       41ms modprobe@efi_pstore.service
       35ms user-runtime-dir@1000.service
       27ms alsa-restore.service
       22ms plymouth-quit.service
       20ms modprobe@pstore_blk.service
       16ms modprobe@ramoops.service
       15ms modprobe@pstore_zone.service
       14ms systemd-update-utmp-runlevel.service
        6ms sys-kernel-config.mount
        4ms sys-fs-fuse-connections.mount
       88us blk-availability.service

systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @47.152s
└─udisks2.service @20.070s +27.081s
  └─basic.target @17.520s
    └─paths.target @17.466s
      └─cups.path @28.166s
        └─sysinit.target @16.791s
          └─systemd-timesyncd.service @16.356s +434ms
            └─systemd-tmpfiles-setup.service @15.093s +660ms
              └─systemd-journal-flush.service @8.391s +6.699s
                └─systemd-journald.service @7.294s +1.093s
                  └─systemd-journald.socket @7.261s
                    └─-.mount @7.254s
                      └─-.slice @7.254s

blkid

/dev/sda1: UUID="0663e327-0b95-4f21-a33c-d777682154f1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6abcdb62-01"

lsblk

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 298.1G  0 disk 
└─sda1   8:1    0 298.1G  0 part /
sr0     11:0    1  1024M  0 rom  

1 Like

Wow that is a really great question especially since you have very old 64-bit hardware so you’ll see a big difference with just a few time consuming services disabled.

First note I caution disabling services you don’t research and understand. Recovery may not be as easy as just enabling the service. To avoid long boots due to upgrades I disable upgrade server and manually upgrade but I don’t recommend this as updates are then usually ignored by many.

With that said there are a few I have disabled that I would recommend for most users:

  1. ModemManager — For hose not using 3G/4G Modems
  2. cups – Only remove if you don’t use a printer. Also remove cups-browser first as it is a dependency for cups.
  3. avahi – Some desktop users will want to keep this one but I sure don’t need it. This is for detecting other apps on a network. It’s the Linux implementation of ‘Bonjour’ on MacOS X and Windows.
  4. gpu-manager – Only needed for hot swapping graphics hardware. Most users don’t need this.

By disabling all above I save about 35s boot time on my decade old netbook:

sudo systemctl disable ModemManager
sudo systemctl disable cups-browser
sudo systemctl disable cups
sudo systemctl disable avahi-daemon
sudo systemctl disable gpu-manager

2 Likes

Well I did ran all the commands you recommended but it only reduced 4 secs off my boot time.

systemd-analyze

Startup finished in 6.759s (kernel) + 47.031s (userspace) = 53.791s 
graphical.target reached after 46.992s in userspace

systemd-analyze blame

22.121s udisks2.service
22.058s networkd-dispatcher.service
21.295s accounts-daemon.service
14.364s dev-sda1.device
11.246s avahi-daemon.service
10.909s NetworkManager.service
10.645s NetworkManager-wait-online.service
 9.745s systemd-logind.service
 9.741s thermald.service
 9.556s systemd-resolved.service
 9.077s wpa_supplicant.service
 8.720s cups.service
 8.304s systemd-journal-flush.service
 6.832s rsyslog.service
 6.528s apport.service
 5.372s grub-common.service
 5.339s e2scrub_reap.service
 5.208s apparmor.service
 4.944s systemd-udevd.service
 2.292s systemd-modules-load.service
 2.231s keyboard-setup.service
 2.191s grub-initrd-fallback.service
 2.018s lm-sensors.service
 1.728s systemd-udev-trigger.service
 1.424s systemd-sysusers.service
 1.423s systemd-random-seed.service
 1.419s polkit.service
 1.251s setvtrgb.service
 1.234s systemd-tmpfiles-setup-dev.service
 1.211s modprobe@ramoops.service
 1.166s systemd-sysctl.service
 1.159s geoclue.service
 1.104s user@1000.service
 1.072s modprobe@pstore_blk.service
 1.037s modprobe@chromeos_pstore.service
 1.016s binfmt-support.service
  937ms swapfile.swap
  925ms modprobe@pstore_zone.service
  820ms update-notifier-download.service
  783ms lvm2-monitor.service
  707ms systemd-timesyncd.service
  684ms systemd-tmpfiles-setup.service
  647ms systemd-journald.service
  620ms modprobe@efi_pstore.service
  446ms ufw.service
  440ms systemd-remount-fs.service
  440ms sddm.service
  400ms console-setup.service
  375ms kerneloops.service
  337ms plymouth-read-write.service
  325ms dev-hugepages.mount
  323ms dev-mqueue.mount
  321ms sys-kernel-debug.mount
  319ms sys-kernel-tracing.mount
  306ms kmod-static-nodes.service
  297ms modprobe@configfs.service
  289ms modprobe@drm.service
  281ms modprobe@fuse.service
  258ms systemd-user-sessions.service
  249ms upower.service
  174ms rtkit-daemon.service
  156ms proc-sys-fs-binfmt_misc.mount
  145ms systemd-update-utmp.service
   34ms user-runtime-dir@1000.service
   34ms alsa-restore.service
   13ms systemd-update-utmp-runlevel.service
   13ms plymouth-quit.service
    6ms sys-kernel-config.mount
    5ms sys-fs-fuse-connections.mount
   80us blk-availability.service

systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @46.992s
└─udisks2.service @24.870s +22.121s
  └─basic.target @22.490s
    └─sockets.target @22.489s
      └─uuidd.socket @22.489s
        └─sysinit.target @21.603s
          └─systemd-timesyncd.service @20.895s +707ms
            └─systemd-tmpfiles-setup.service @19.689s +684ms
              └─systemd-journal-flush.service @11.383s +8.304s
                └─systemd-remount-fs.service @10.937s +440ms
                  └─systemd-journald.socket @10.598s
                    └─-.mount @10.590s
                      └─-.slice @10.590s

1 Like

I think there’s only so much software can be tweaked with to the extent that you’ll notice a difference.

When that limit is reached, the only thing you can really work with is the hardware.

Spinning drives are known to be slower and get slower with age… I know for sure my older laptop has always been rather slow to boot and it was worse when I encrypted my installs.

I would consider buying an SSD at some point and migrating to that for your pc.

1 Like

@thetick
Caution about disabling “ModemManager”. That service manage MODEM 3G and 4G.

For “old” SATA disk not having enough speed is possible an solution.
BTRFS compress data.

If using BTRFS and having improvements in kernel new version try update the OS kernel using the PPA below

1 Like

Notice cups and avahi-daemon are still running. You will need to check the dependencies.

Try
systemctl --reverse list-dependencies cups.service
systemctl --reverse list-dependencies avahi-daemon.service

and remove the dependencies first if not needed.

2 Likes

Oh of course Modem is 3G/4G modem. I don’t have those on my computer either.

1 Like

I wrote this about disabling printing:

I agree with the SSD idea, as that will definitely help in boot times - as stuff is read from disk. If you can swing it, an M.2 NVMe SSD is the way to go - they’re insanely fast.

More RAM is also good, but so is patience. How often are you rebooting?

$ uptime
 16:05:18 up 16 days, 21:31,  2 users,  load average: 1.20, 1.30, 1.26

I probably won’t bother rebooting that for a couple more weeks, and I’ll get a cup of coffee when I do so even though my boot times look like:

$ systemd-analyze
Startup finished in 3.176s (kernel) + 6.628s (userspace) = 9.804s 
graphical.target reached after 6.206s in userspace

So, booting isn’t really a long process, and that’s probably not the quickest to boot in my stable.

3 Likes

Yes I used following commands to completely disable cups and avahi-daemon

sudo systemctl mask cups.service
sudo systemctl mask avahi-daemon.service

Results: Saved 2 Seconds

$ systemd-analyze 
Startup finished in 6.600s (kernel) + 44.711s (userspace) = 51.312s 
graphical.target reached after 44.678s in userspace
$systemd-analyze blame
20.295s networkd-dispatcher.service
20.227s udisks2.service
19.815s accounts-daemon.service
14.105s dev-sda1.device
10.659s NetworkManager.service
 9.108s systemd-logind.service
 9.100s thermald.service
 8.910s wpa_supplicant.service
 8.719s systemd-resolved.service
 7.705s systemd-journal-flush.service
 7.351s apport.service
 5.410s rsyslog.service
 4.898s apparmor.service
 4.363s systemd-udevd.service
 4.262s e2scrub_reap.service
 3.955s grub-common.service
 2.400s systemd-modules-load.service
 2.134s keyboard-setup.service
 2.023s grub-initrd-fallback.service
 1.692s lm-sensors.service
 1.527s systemd-udev-trigger.service
 1.482s systemd-sysusers.service
 1.284s polkit.service
 1.278s systemd-random-seed.service
 1.232s systemd-sysctl.service
 1.168s swapfile.swap
 1.136s binfmt-support.service
 1.132s user@1000.service
 1.093s systemd-tmpfiles-setup-dev.service
 1.021s modprobe@chromeos_pstore.service
 1.004s geoclue.service
  840ms modprobe@ramoops.service
  833ms modprobe@pstore_blk.service
  812ms systemd-timesyncd.service
  806ms systemd-journald.service
  746ms modprobe@efi_pstore.service
  595ms systemd-remount-fs.service
  594ms update-notifier-download.service
  591ms systemd-tmpfiles-setup.service
  585ms modprobe@pstore_zone.service
  578ms setvtrgb.service
  442ms console-setup.service
  440ms plymouth-read-write.service
  422ms kerneloops.service
  394ms dev-hugepages.mount
  393ms dev-mqueue.mount
  391ms sys-kernel-debug.mount
  389ms sys-kernel-tracing.mount
  387ms lvm2-monitor.service
  375ms kmod-static-nodes.service
  360ms modprobe@configfs.service
  358ms modprobe@drm.service
  345ms modprobe@fuse.service
  307ms systemd-update-utmp.service
  272ms ufw.service
  261ms sddm.service
  250ms upower.service
  167ms proc-sys-fs-binfmt_misc.mount
  163ms rtkit-daemon.service
   86ms systemd-user-sessions.service
   34ms user-runtime-dir@1000.service
   25ms alsa-restore.service
   14ms systemd-update-utmp-runlevel.service
   12ms plymouth-quit.service
    8ms sys-kernel-config.mount
    5ms sys-fs-fuse-connections.mount
  135us blk-availability.service

$ systemd-analyze critical-chain 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @44.678s
└─udisks2.service @24.450s +20.227s
  └─basic.target @22.238s
    └─sockets.target @22.238s
      └─uuidd.socket @22.238s
        └─sysinit.target @21.795s
          └─systemd-timesyncd.service @20.982s +812ms
            └─systemd-tmpfiles-setup.service @19.821s +591ms
              └─systemd-journal-flush.service @12.114s +7.705s
                └─systemd-remount-fs.service @11.513s +595ms
                  └─systemd-journald.socket @11.101s
                    └─system.slice @11.094s
                      └─-.slice @11.094s

1 Like

Yes I see. I don’t think there is much more you can do other than the suggestion of switching to SSD, increasing RAM, or even better if you can upgrade to a modern machine. At some point running a modern Linux OS on an older, low-end machine is a struggle with which little you can do to improve performance.

1 Like

20.227s udisks2.service

Long udisks2 times are sometimes caused by UUID mismatches.
compare
sudo lsblk -f
with
cat /etc/fstab
and check that they match.

1 Like

I had a thread here or on the list-serve where I was having “long boot times” with Lubuntu . . . which even now, compared to all my other distros . . . is slow to boot . . . . The answer at that time, “systemd takes more time to boot the system” . . . and so it does.

I can neither confirm nor dispute that. All I can give are some historical boot times of the same PC and hardware.

From kernel load - to - the start of the blackscreen just before the desktop.
12.04 - 4 secs (upstart)
18.04 - 8 secs. (systemd)
22.04 - 16 secs. (systemd)
(is this progress ?)
These timings are recorded with a stop watch.

All that systemd-analyze stuff maybe useful for experts, but I find most of the output misleading, because all the tasks overlap each other, and unless you know each dependency, it’s not easy to trace what is happening.

With systemd, the number of services I’ve disabled or removed is embarassing (over 40). It’s because the boot up tries to cater for a wide range of systems, some of which I’ll never use. I can’t say that any of the disabled stuff has helped the boot time, but it does give me a nice feeling each time I boot that I’ve done all I can to make it ‘lean’.

1 Like
# systemd-analyze
Startup finished in 12.149s (firmware) + 1.576s (loader) + 4.771s (kernel) + 3.053s (userspace) = 21.551s 
graphical.target reached after 3.020s in userspace.

What is “(firmware)”?

Firmware is hardware specific low level code. Examples are BIOS or UEFI for your processor, various Wi-Fi, some Ethernet, SSD, most modern GPUs.

To help explain what is happening in your case type the following and post the results:
systemd-analyze blame

1 Like
$ systemd-analyze blame
3.194s apt-daily.service
1.547s systemd-udev-settle.service
1.045s xrdp.service
 706ms smartmontools.service
 347ms man-db.service
 314ms winbind.service
 296ms udisks2.service
 290ms lm-sensors.service
 193ms apt-daily-upgrade.service
 188ms vboxdrv.service
 177ms systemd-journal-flush.service
 161ms virtualbox.service
 149ms cups.service
 135ms dev-nvme0n1p2.device
 125ms user@1000.service
 112ms modprobe@chromeos_pstore.service
  98ms lvm2-monitor.service
  88ms accounts-daemon.service                                                                                                     
  86ms dev-loop8.device                                                                                                            
  81ms dev-loop9.device                                                                                                            
  80ms apparmor.service                                                                                                            
  74ms dev-loop10.device                                                                                                           
  69ms hdd\x2dstorage.mount                                                                                                        
  68ms media-hdd\x2dstorage.mount                                                                                                  
  68ms ua-timer.service                                                                                                            
  67ms systemd-udev-trigger.service                                                                                                
  61ms avahi-daemon.service                                                                                                        
  59ms dundee.service                                                                                                              
  58ms polkit.service                                                                                                              
  58ms dbus.service
  57ms systemd-logind.service
  54ms ofono.service
  50ms ModemManager.service
  50ms thermald.service
  49ms systemd-udevd.service
  48ms update-notifier-download.service
  46ms rtkit-daemon.service
  45ms systemd-resolved.service
  43ms packagekit.service
  40ms plymouth-quit.service
  40ms mnt-AnnotatedSlides.mount
  39ms mnt-Slides.mount
  38ms systemd-timesyncd.service
  38ms mnt-media\x2dfiles.mount
  36ms snap-bare-5.mount
  36ms sysfsutils.service
  36ms home.mount
  36ms snap-core20-1494.mount
  35ms snap-core20-1518.mount
  35ms systemd-journald.service
  34ms systemd-binfmt.service
  33ms NetworkManager.service
  33ms grub-common.service
  31ms kerneloops.service
  31ms snap-firefox-1539.mount
  30ms proc-sys-fs-binfmt_misc.mount
  30ms keyboard-setup.service
  29ms geoclue.service
  29ms nordvpnd.socket
  29ms snap-firefox-1551.mount
  28ms apport.service
  27ms snap-gnome\x2d3\x2d38\x2d2004-106.mount
  26ms rsyslog.service
  26ms snap-gnome\x2d3\x2d38\x2d2004-112.mount
  26ms upower.service
  25ms snap-gtk\x2dcommon\x2dthemes-1534.mount
  25ms udhcpd.service
  23ms snap-gtk\x2dcommon\x2dthemes-1535.mount
  23ms snap-snapd-16292.mount
  22ms systemd-modules-load.service
  21ms colord.service
  20ms snap-snapd-16010.mount
  19ms nvmf-autoconnect.service
  17ms alsa-restore.service
  17ms systemd-tmpfiles-clean.service
  16ms systemd-fsck@dev-disk-by\x2duuid-812C\x2dB4BC.service
  14ms plymouth-start.service
  13ms grub-initrd-fallback.service
  13ms nut-driver.service
  12ms xrdp-sesman.service
  11ms systemd-tmpfiles-setup.service
  11ms openvpn.service
  11ms e2scrub_reap.service
  11ms plymouth-read-write.service
  10ms dev-hugepages.mount
  10ms vsftpd.service
  10ms dev-mqueue.mount
   9ms sys-kernel-debug.mount
   9ms sys-kernel-tracing.mount
   9ms console-setup.service
   9ms binfmt-support.service
   8ms wpa_supplicant.service
   8ms nut-monitor.service
   7ms systemd-tmpfiles-setup-dev.service
   7ms systemd-random-seed.service
   7ms kmod-static-nodes.service
   6ms systemd-sysusers.service
   6ms modprobe@configfs.service
   6ms modprobe@drm.service
   5ms nut-server.service
   5ms modprobe@fuse.service
   5ms systemd-remount-fs.service
   4ms boot-efi.mount
   4ms user-runtime-dir@1000.service
   4ms systemd-update-utmp.service
   3ms systemd-update-utmp-runlevel.service
   3ms systemd-sysctl.service
   2ms systemd-user-sessions.service
   2ms systemd-rfkill.service
   2ms vboxballoonctrl-service.service
   2ms vboxautostart-service.service
   1ms vboxweb-service.service
   1ms sys-fs-fuse-connections.mount
   1ms modprobe@efi_pstore.service
   1ms setvtrgb.service
   1ms sddm.service
   1ms sys-kernel-config.mount
   1ms modprobe@pstore_blk.service
   1ms ufw.service
   1ms modprobe@pstore_zone.service
 954us motd-news.service
 909us modprobe@ramoops.service
   9us blk-availability.service

Is there a way to see which firmwares are being loaded and how long each takes?

I would also like to prevent snap mounts from mounting.
I don’t use them and I have disabled the service.

$ mount | grep snap
/var/lib/snapd/snaps/core20_1518.snap on /snap/core20/1518 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/bare_5.snap on /snap/bare/5 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core20_1494.snap on /snap/core20/1494 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/firefox_1551.snap on /snap/firefox/1551 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/firefox_1539.snap on /snap/firefox/1539 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gnome-3-38-2004_112.snap on /snap/gnome-3-38-2004/112 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gnome-3-38-2004_106.snap on /snap/gnome-3-38-2004/106 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gtk-common-themes_1534.snap on /snap/gtk-common-themes/1534 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gtk-common-themes_1535.snap on /snap/gtk-common-themes/1535 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_16010.snap on /snap/snapd/16010 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_16292.snap on /snap/snapd/16292 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hid
2 Likes