Sorry for the report. My main problem was related to netctl created by
easyroam software. The bug report can be deleted
** Description changed:
I experience really long boot up time after reboot on modern hardware.
Otherwise the system has no noticable hardware problems (may be related:
startup of programs is rather slow compared to my old laptop). I created
a bug report with AI assistance and happily contribute logs etc.
**Summary**
On a fresh installation of Ubuntu 26.04 Desktop, `graphical.target` is
consistently reached only after about 95 seconds, although no single
long-running service appears in `systemd-analyze blame`.
**System**
* Ubuntu 26.04 Desktop (fresh installation)
* Lenovo IdeaPad Pro 5 16IPH11
* GNOME (Wayland)
* Hibernate configured manually (working configuration with swap file)
**Observed behaviour**
`systemd-analyze` reports a userspace startup time of approximately 95
seconds.
`systemd-analyze critical-chain` consistently shows:
```
graphical.target
└─ power-profiles-daemon.service
- └─ multi-user.target
- └─ plymouth-quit-wait.service
- └─ systemd-user-sessions.service
- └─ network.target
- └─ NetworkManager.service
- └─ ...
- └─ local-fs.target
- └─ run-snapd-ns-snapd-desktop-integration.mnt.mount
+ └─ multi-user.target
+ └─ plymouth-quit-wait.service
+ └─ systemd-user-sessions.service
+ └─ network.target
+ └─ NetworkManager.service
+ └─ ...
+ └─ local-fs.target
+ └─ run-snapd-ns-snapd-desktop-integration.mnt.mount
```
The critical path passes through `run-snapd-ns-snapd-desktop-
integration.mnt.mount`, which becomes active roughly 90 seconds after
boot.
`systemd-analyze blame` does not show any service accounting for this
delay, suggesting that the boot time is dominated by waiting rather than
execution time.
The issue is reproducible across multiple reboots.
**Additional observations**
During boot, the journal contains messages from snapd, including DNS
lookup failures for `api.snapcraft.io`. I cannot determine whether these
are related to the observed delay, so I am including them only as
additional information rather than as the suspected cause.
Relevant outputs attached:
* `systemd-analyze`
* `systemd-analyze blame`
* `systemd-analyze critical-chain`
* boot journal (`journalctl -b`)
* snapd logs
-
-----------------------------------------------
- attachement: Log of
+ attachement: Log of
systemd-analyze
systemd-analyze blame | head -30
journalctl -b | grep -Ei "snap|snapd|mount|namespace"
journalctl -b | grep -i snapd
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: snapd 2.75.2+ubuntu26.04.2
ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6
Uname: Linux 7.0.0-27-generic x86_64
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 9 15:07:50 2026
InstallationDate: Installed on 2026-06-17 (22 days ago)
InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64
(20260423.1)
ProcEnviron:
- LANG=de_DE.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=<set>
+ LANG=de_DE.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=<set>
SnapChanges:
- keine Änderungen gefunden
- WARNUNG: Es gibt 1 neue Warnung. Siehe »snap warnings«.
+ keine Änderungen gefunden
+ WARNUNG: Es gibt 1 neue Warnung. Siehe »snap warnings«.
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2160227
Title:
Long boot up time: graphical.target is delayed by about 95 seconds on
a fresh Ubuntu 26.04 installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2160227/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
