Ubuntu Support Template
Ubuntu Version : 24.04.3 – Ubuntu Unity flavour
Desktop Environment (if applicable) : Unity 7.7
Problem Description :
Infrequently, upon cold boot.
Somewhat often (about 1 in every 2 times) after logging out then logging in again.
Infrequently, upon restarting.
It is somewhat mildly irritating when it happens, though almost always a reboot or logout/login will solve this.
I would not consider this a “major issue” by any means as it does not really impact my performance when using my computer but, if anyone has any suggestions or if anyone has run into this and has some tips, it would be helpful.
Relevant System Information :
inxi -F
System:
Host: jadams-Aspire-A315-23 Kernel: 6.14.0-36-generic arch: x86_64 bits: 64
Desktop: Unity v: 7.7.0 Distro: Ubuntu Unity 24.04.3 LTS (Noble Numbat)
Machine:
Type: Laptop System: Acer product: Aspire A315-23 v: V1.21
serial: <superuser required>
Mobo: DL model: Lotus_DA v: V1.21 serial: <superuser required>
UEFI: Insyde v: 1.21 date: 09/08/2022
Battery:
ID-1: BAT1 charge: 39.3 Wh (100.0%) condition: 39.3/41.6 Wh (94.6%)
CPU:
Info: dual core model: AMD Athlon Silver 3050U with Radeon Graphics bits: 64
type: MCP cache: L2: 1024 KiB
Speed (MHz): avg: 1306 min/max: 1400/2300 cores: 1: 1212 2: 1400
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-2: Chicony VGA WebCam driver: uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.11 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution:
1: 1680x1050~60Hz 2: 1920x1080~60Hz
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa
v: 25.0.7-0ubuntu0.24.04.2 renderer: AMD Radeon Graphics (radeonsi raven2
ACO DRM 3.61 6.14.0-36-generic)
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp3x
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.14.0-36-generic status: kernel-api
Server-1: PulseAudio v: 16.1 status: active
Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
IF: wlp2s0 state: up mac: 10:a5:1d:83:97:1c
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp3s0 state: down mac: c0:18:50:a6:09:ea
Bluetooth:
Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb type: USB
Report: hciconfig ID: hci0 state: up address: 10:A5:1D:83:97:20 bt-v: 4.2
Drives:
Local Storage: total: 2.05 TiB used: 316.11 GiB (15.0%)
ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GD3JX016N
size: 238.47 GiB
ID-2: /dev/sda vendor: Seagate model: One Touch w PW size: 1.82 TiB
type: USB
Partition:
ID-1: / size: 233.38 GiB used: 111.26 GiB (47.7%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 299.4 MiB used: 7.8 MiB (2.6%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 45.4 C mobo: N/A gpu: amdgpu temp: 45.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 6 GiB available: 5.73 GiB used: 1.82 GiB (31.7%)
Processes: 263 Uptime: 30m Shell: Bash inxi: 3.3.34
Screenshots or Error Messages :
What I’ve Tried :
Checked /var/crash logs for errors.
Tried Slick greeter to rule out it being a lightdm unity greeter issue vs. desktop session.
General Google searches looking for other threads of users facing similar problems.
Before Posting :
After searching, I could not find any other topics on this issue.
qiii
December 8, 2025, 11:54am
2
Hello!
In the terminal, issue
systemd-analyze blame
Post back the top half dozen or so entries. They should be arranged in descending order of time taken to initialize.
1 Like
Hi @qiii ,
Please see output below of the first several lines of systemd-analyze blame .
Many thanks.
systemd-analyze blame
5.912s NetworkManager-wait-online.service
5.198s logrotate.service
4.786s NetworkManager.service
4.472s accounts-daemon.service
4.287s snapd.seeded.service
4.151s polkit.service
4.106s bluetooth.service
4.099s snapd.service
P.S. Today was a “normal” bootup in that it didn’t take very long and all components (e.g., Nemo desktop with icons) seemed to have loaded properly.
qiii
December 9, 2025, 6:23am
4
Well, it looks like we didn’t catch it behaving badly, given the specs of your machine. We should probably try this again when you have a slow startup.
I’ll try to pop in to check for another reply to the thread, but if I miss it and don’t get right back to you, hopefully someone else in the community will take it from there.
I encountered the same problem a couple of times and just now. Here’s my output:
5.745s NetworkManager-wait-online.service
1.319s NetworkManager.service
1.199s gpu-manager.service
930ms systemd-backlight@backlight:intel_backlight.service
897ms snapd.seeded.service
551ms snapd.service
478ms thermald.service
452ms dev-nvme0n1p2.device
435ms apport.service
316ms udisks2.service
304ms accounts-daemon.service
293ms systemd-udev-trigger.service
233ms polkit.service
227ms rsyslog.service
202ms user@1000.service
197ms bolt.service
176ms systemd-resolved.service
168ms systemd-journald.service
145ms secureboot-db.service
141ms avahi-daemon.service
139ms bluetooth.service
138ms upower.service
135ms dev-loop13.device
134ms networking.service
131ms dev-loop17.device
128ms dev-loop5.device
126ms dev-loop2.device
124ms dev-loop6.device
120ms dev-loop19.device
119ms dev-loop1.device
117ms systemd-udevd.service
115ms dev-loop4.device
115ms dev-loop10.device
113ms grub-common.service
113ms systemd-logind.service
112ms systemd-journal-flush.service
111ms keyboard-setup.service
110ms systemd-timesyncd.service
109ms dev-loop8.device
107ms apparmor.service
107ms dev-loop7.device
106ms lm-sensors.service
106ms dev-loop3.device
102ms ModemManager.service
97ms switcheroo-control.service
95ms e2scrub_reap.service
89ms dev-loop14.device
88ms lvm2-monitor.service
88ms boot-efi.mount
87ms dev-loop21.device
87ms snapd.apparmor.service
86ms dev-loop16.device
86ms dev-loop20.device
85ms dev-loop0.device
85ms dev-loop15.device
84ms dev-loop18.device
83ms dev-loop12.device
82ms dev-loop9.device
79ms dev-loop11.device
70ms systemd-modules-load.service
68ms colord.service
65ms systemd-remount-fs.service
64ms dbus.service
63ms lightdm.service
60ms snap-bare-5.mount
59ms snap-core22-2139.mount
58ms snap-core22-2163.mount
56ms snap-core24-1225.mount
55ms snap-discord-262.mount
54ms grub-initrd-fallback.service
53ms snap-discord-263.mount
51ms snap-element\x2ddesktop-186.mount
51ms systemd-tmpfiles-setup-dev-early.service
50ms plymouth-quit-wait.service
49ms snap-element\x2ddesktop-188.mount
48ms snap-firefox-7355.mount
47ms systemd-tmpfiles-setup.service
47ms snap-firefox-7423.mount
46ms cups.service
43ms snap-gnome\x2d42\x2d2204-202.mount
42ms snap-gnome\x2d42\x2d2204-226.mount
40ms snap-gnome\x2d46\x2d2404-125.mount
39ms systemd-rfkill.service
38ms snap-gnome\x2d46\x2d2404-145.mount
38ms sysstat.service
37ms systemd-binfmt.service
37ms snap-gtk\x2dcommon\x2dthemes-1535.mount
35ms systemd-fsck@dev-disk-by\x2duuid-CB35\x2d89C8.service
35ms snap-mesa\x2d2404-1165.mount
33ms plymouth-start.service
32ms sys-fs-fuse-connections.mount
32ms snap-mesa\x2d2404-912.mount
29ms snap-rpi\x2dimager-709.mount
28ms snap-snapd-24792.mount
26ms snap-snapd-25577.mount
26ms sys-kernel-config.mount
24ms wpa_supplicant.service
24ms snap-telegram\x2ddesktop-6862.mount
23ms snap-telegram\x2ddesktop-6869.mount
22ms proc-sys-fs-binfmt_misc.mount
21ms tmp.mount
21ms dev-hugepages.mount
21ms dev-mqueue.mount
20ms sys-kernel-debug.mount
20ms sys-kernel-tracing.mount
19ms dns-clean.service
19ms systemd-update-utmp.service
18ms modprobe@drm.service
17ms systemd-user-sessions.service
17ms systemd-sysctl.service
17ms plymouth-read-write.service
17ms systemd-backlight@leds:tpacpi::kbd_backlight.service
16ms modprobe@fuse.service
15ms kmod-static-nodes.service
15ms kerneloops.service
14ms rtkit-daemon.service
14ms modprobe@configfs.service
14ms alsa-restore.service
11ms ifupdown-pre.service
10ms console-setup.service
10ms systemd-tmpfiles-setup-dev.service
10ms systemd-random-seed.service
10ms systemd-update-utmp-runlevel.service
10ms user-runtime-dir@1000.service
9ms modprobe@dm_mod.service
8ms swapfile.swap
8ms modprobe@efi_pstore.service
8ms modprobe@loop.service
7ms sysstat-collect.service
7ms ufw.service
2ms setvtrgb.service
1ms snapd.socket
31us blk-availability.service
I would suggest running these commands and see if we can narrow it down:
systemd-analyze
systemd-analyze critical-chain --no-pager
journalctl -b -1 --no-pager
1 Like
systemd-analyze
Startup finished in 7.298s (firmware) + 2.660s (loader) + 2.819s (kernel) + 9.238s (userspace) = 22.016s
graphical.target reached after 9.226s in userspace.
systemd-analyze critical-chain --no-pager
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 @9.226s
└─multi-user.target @9.226s
└─kerneloops.service @9.210s +15ms
└─network-online.target @9.173s
└─NetworkManager-wait-online.service @3.426s +5.745s
└─NetworkManager.service @2.092s +1.319s
└─dbus.service @1.946s +64ms
└─basic.target @1.909s
└─sockets.target @1.909s
└─snapd.socket @1.907s +1ms
└─sysinit.target @1.901s
└─systemd-backlight@backlight:intel_backlight.service @2.095s +930ms
└─system-systemd\x2dbacklight.slice @1.542s
└─system.slice @324ms
└─-.slice @324ms
The journalctl output is way too large to post.
The NetworkManager-wait-online.service is frequently associated with delayed boot times. I’ve had it disabled for a long time. Even if my network isn’t fully up by the time I login, it usually is a few seconds afterwards so it’s no big deal.
But since the slowness occurs just after you log in, it may be caused by one more of the services that are started when the Unity session begins.
$ systemd-analyze --user blame.
Also, do you have any programs that are set to autostart on login which might hog cpu time/io bandwidth? That can cause slowdowns that systemd-analyze won’t pick up.
qiii
December 9, 2025, 8:16pm
9
I’m going to have to second gpmitch. It sure doesn’t seem that kernel startup is the issue. It just seems that way since the behavior at kernel startup sometimes appearss to be bundled with whatever is happening at login.
1 Like
mekaneck@mekaneck:~$ systemd-analyze --user blame
25.198s bamfdaemon.service
25.191s xdg-desktop-portal.service
25.137s evolution-source-registry.service
25.083s xdg-desktop-portal-gtk.service
25.078s gvfs-udisks2-volume-monitor.service
25.045s org.freedesktop.IBus.session.GNOME.service
25.040s xdg-desktop-portal-rewrite-launchers.service
17.178s evolution-calendar-factory.service
530ms pulseaudio.service
217ms org.gnome.SettingsDaemon.XSettings.service
150ms hud.service
148ms unity7.service
133ms gnome-terminal-server.service
116ms gnome-session-manager@unity.service
46ms evolution-addressbook-factory.service
40ms gvfs-gphoto2-volume-monitor.service
32ms zeitgeist.service
30ms gvfs-afc-volume-monitor.service
24ms unity-gtk-module.service
22ms gvfs-mtp-volume-monitor.service
18ms xdg-document-portal.service
18ms zeitgeist-fts.service
16ms gpg-agent-ssh.socket
14ms gnome-session-signal-init.service
10ms gvfs-goa-volume-monitor.service
9ms gvfs-daemon.service
8ms at-spi-dbus-bus.service
8ms dbus.socket
8ms xdg-permission-store.service
8ms unity-panel-service.service
7ms dbus.service
6ms session-migration.service
6ms gvfs-metadata.service
4ms dconf.service
3ms gnome-session-monitor.service
I don’t have any other programs set to autostart. These are enabled by default:
qiii
December 9, 2025, 9:32pm
11
I wonder if it might be helpful to see a hierarchical view of what processes are being run when you finally get to userspace. There’s an outside chance that this might give us a clue as to the culprit if whatever that is is still running by the time you get to your desktop.
Try
pstree your_user_name
gpmitch
December 9, 2025, 10:25pm
12
well, bamfdaemon has historically caused slowdowns and is likely slowing down the execution of the other services below it until it finally get finished with whatever it’s doing and then allows everything to start executing normally. I’d expect to see the systemd journal filled with errors related to it if it is indeed the culprit.
1 Like
Of course, after I ask the question, everything has been working just fine ever since. Go figure!
This is the output for mine. I just did a reboot so all I did after boot was open my browser (Brave) and come to this site.
systemd-analyze --user blame
819ms pulseaudio.service
703ms unity7.service
612ms evolution-source-registry.service
350ms gnome-session-manager@unity.service
313ms gvfs-afc-volume-monitor.service
302ms bamfdaemon.service
302ms evolution-calendar-factory.service
301ms gvfs-daemon.service
292ms xdg-desktop-portal.service
241ms org.gnome.SettingsDaemon.XSettings.service
200ms evolution-addressbook-factory.service
145ms gnome-terminal-server.service
105ms dconf.service
100ms hud.service
94ms gnome-session-monitor.service
92ms gnome-session-signal-init.service
83ms unity-gtk-module.service
76ms org.freedesktop.IBus.session.GNOME.service
71ms xdg-desktop-portal-gtk.service
68ms xdg-document-portal.service
46ms zeitgeist.service
40ms unity-panel-service.service
33ms gpg-agent-ssh.socket
32ms session-migration.service
30ms gvfs-udisks2-volume-monitor.service
28ms zeitgeist-fts.service
17ms xdg-desktop-portal-rewrite-launchers.service
16ms gvfs-goa-volume-monitor.service
12ms gvfs-gphoto2-volume-monitor.service
12ms gvfs-mtp-volume-monitor.service
12ms at-spi-dbus-bus.service
10ms xdg-permission-store.service
10ms dbus.socket
6ms gvfs-metadata.service
5ms dbus.service
However, before the reboot it did take a few more seconds (about 10 s) to shut down the computer (i.e., sitting on the wallpaper for a few more seconds than normal after clicking “Shut Down” until I got to the Ubuntu Unity shutdown screen).
Just to follow up – I have done my darndest to replicate the issue I’ve had as I really want to know what happened.
Ever since I made this post, it has been working perfectly ever since.
The computer saw me typing the support post and was like, no way Jaymo, you’re not getting to the bottom of this.
ogra
December 12, 2025, 7:55am
16
The wonders of AI… What a time to live in …
It happens randomly at my end. Also logging out takes a long time and that happens every time. It’s been years like that, even before UU became a official flavor and has been reported to the developer a couple of times. Something is getting in the way that causes it. Most of the time i just press the power button when it hangs and shut it down that way.
We are currently busy with fixing more critical bugs but it’s something I’d like to see getting solved and we’ll investigate it further once we solved the main problems with Unity.
Two things I would like to suggest that may or may not help in this situation.
Firstly, change quiet splash to text in the GRUB config file:
sudo nano /etc/default/grub
Change this GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
To thisGRUB_CMDLINE_LINUX_DEFAULT="text"
Save with Ctrl+O then Enter then Ctrl+X
sudo update-grub
In my test with Ubuntu 25.10 in a VM both startup and shutdown times were faster.
Secondly, never use the power button to force a shutdown, it may damage the filesystem.
Instead, use the Linux magic SysRq to reboot or poweroff cleanly.
Hold Alt + SysRq (PrintScreen) and then press the following keys one at a time, slowly, to reboot:R E I S U B
To power off, same combo but with this:R E I S U O
1 Like
Ok, the problem happened now.
systemd-analyze --user blame
24.776s hud.service
1.191s unity7.service
780ms pulseaudio.service
442ms evolution-source-registry.service
242ms gnome-session-manager@unity.service
229ms xdg-desktop-portal.service
202ms evolution-addressbook-factory.service
164ms evolution-calendar-factory.service
155ms bamfdaemon.service
138ms gnome-terminal-server.service
118ms zeitgeist-fts.service
113ms dconf.service
105ms org.gnome.SettingsDaemon.XSettings.service
81ms xdg-desktop-portal-gtk.service
76ms gnome-session-signal-init.service
67ms unity-panel-service.service
66ms unity-gtk-module.service
56ms zeitgeist.service
54ms gvfs-udisks2-volume-monitor.service
37ms xdg-document-portal.service
33ms xdg-desktop-portal-rewrite-launchers.service
27ms org.freedesktop.IBus.session.GNOME.service
21ms gnome-session-monitor.service
19ms gpg-agent-ssh.socket
19ms launchpadlib-cache-clean.service
18ms at-spi-dbus-bus.service
17ms gvfs-mtp-volume-monitor.service
15ms dbus.socket
14ms session-migration.service
12ms xdg-permission-store.service
11ms gvfs-afc-volume-monitor.service
11ms gvfs-daemon.service
10ms gvfs-gphoto2-volume-monitor.service
8ms gvfs-goa-volume-monitor.service
7ms gvfs-metadata.service
4ms dbus.service
1 Like
system
January 5, 2026, 1:23am
20
This topic was automatically closed after 30 days. New replies are no longer allowed.
Please check if similar issues have already been reported and resolved.
