My Ubuntu booting to much slow

Abhiso9

New Member
Credits
168
Hello, I'm new user of Ubuntu there is little bit problem in my Ubuntu OS, When I'm start my Ubuntu and getting to slow and hold my laptop screen for 1 minutes and then start, and when I'm using then sometimes also hold my screen as like hang. So, what should I do for that problem please suggest me. Thanks




 


MatsuShimizu

Active Member
Credits
1,751
Hi,
Type this in your terminal and then post the result that you see in the terminal here:
inxi -Fxxxrz
It will return your system, Linux kernel version etc. Based on your previous post here, I think you are using Ubuntu 20.04. But, we don't know your RAM, laptop model etc.

This command will be useful to find out what makes your PC slow:
systemd-analyze blame
 
Last edited:

Abhiso9

New Member
Credits
168
Hi,
Type this in your terminal and then post th
IMG_20210515_103430.jpg
e result that you see in the terminal here:

It will return your system, Linux kernel version etc. Based on your previous post here, I think you are using Ubuntu 20.04. But, we don't know your RAM, laptop model etc.

This command will be useful to find out what makes your PC slow:
 

Attachments

MatsuShimizu

Active Member
Credits
1,751
Hi,
Some things are missing in your screenshot, especially the Info section at the bottom. Select the text in your terminal, right click, select copy and then paste here. You don't need to take a screenshot.

And, did you run this command?
systemd-analyze blame
What are the first 10 processes that you find? Can you copy and paste them here?
Help us and we will help you.

 

Abhiso9

New Member
Credits
168
[email protected]:~$ inxi -Fxxxrz
System:
Kernel: 5.8.0-53-generic x86_64 bits: 64 compiler: N/A
Desktop: Gnome 3.36.7 wm: gnome-shell dm: GDM3 3.36.3
Distro: Ubuntu 20.04.2 LTS (Focal Fossa)
Machine:
Type: Laptop System: Acer product: Aspire A715-42G v: V1.01
serial: <filter>
Mobo: LN model: Azalea_CAS v: V1.01 serial: <filter> UEFI: Insyde v: 1.01
date: 12/14/2020
Battery:
ID-1: BAT1 charge: 50.1 Wh condition: 50.1/47.8 Wh (105%) volts: 13.0/11.2
model: LGC AP18C8K type: Li-ion serial: <filter> status: Full
CPU:
Topology: 6-Core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64
type: MT MCP arch: Zen rev: 1 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 50305
Speed: 1397 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz):
1: 1397 2: 1398 3: 1397 4: 1396 5: 1397 6: 1396 7: 1400 8: 1397 9: 1397
10: 1396 11: 1398 12: 1396
Graphics:
Device-1: NVIDIA vendor: Acer Incorporated ALI driver: nouveau v: kernel
bus ID: 01:00.0 chip ID: 10de:1f9d
Device-2: AMD vendor: Acer Incorporated ALI driver: amdgpu v: kernel
bus ID: 05:00.0 chip ID: 1002:164c
Display: x11 server: X.Org 1.20.9 driver: ati,fbdev
unloaded: modesetting,radeon,vesa compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RENOIR (DRM 3.38.0 5.8.0-53-generic LLVM 11.0.0)
v: 4.6 Mesa 20.2.6 direct render: Yes
Audio:
Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel
v: kernel bus ID: 05:00.1 chip ID: 1002:1637
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
vendor: Acer Incorporated ALI driver: N/A bus ID: 05:00.5
chip ID: 1022:15e2
Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel bus ID: 05:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k5.8.0-53-generic
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 2000
bus ID: 03:00.0 chip ID: 10ec:8168
IF: enp3s0 state: down mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000
bus ID: 04:00.0 chip ID: 8086:2723
IF: wlp4s0 state: up mac: <filter>
Drives:
Local Storage: total: 476.94 GiB used: 29.47 GiB (6.2%)
ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM512GD3JX016N
size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 41020C20
scheme: GPT
Partition:
ID-1: / size: 97.93 GiB used: 29.41 GiB (30.0%) fs: ext4
dev: /dev/nvme0n1p7
Sensors:
System Temperatures: cpu: 50.5 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 47 C device: nouveau temp: N/A
Repos:
Active apt repos in: /etc/apt/sources.list
1: deb http://in.archive.ubuntu.com/ubuntu/ focal main restricted
2: deb http://in.archive.ubuntu.com/ubuntu/ focal-updates main restricted
3: deb http://in.archive.ubuntu.com/ubuntu/ focal universe
4: deb http://in.archive.ubuntu.com/ubuntu/ focal-updates universe
5: deb http://in.archive.ubuntu.com/ubuntu/ focal multiverse
6: deb http://in.archive.ubuntu.com/ubuntu/ focal-updates multiverse
7: deb http://in.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
8: deb http://security.ubuntu.com/ubuntu focal-security main restricted
9: deb http://security.ubuntu.com/ubuntu focal-security universe
10: deb http://security.ubuntu.com/ubuntu focal-security multiverse
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/linuxuprising-ubuntu-apps-focal.list
1: deb http://ppa.launchpad.net/linuxuprising/apps/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/teams.list
1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
Info:
Processes: 336 Uptime: 5m Memory: 15.06 GiB used: 1.44 GiB (9.6%)
Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash
v: 5.0.17 running in: gnome-terminal inxi: 3.0.38
[email protected]:~$
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
15,812
Thank you for that input @Abhiso9 .

And the other one that @MatsuShimizu asked for was for output of

Code:
systemd-analyze blame
Could you provide that please?

Wizard
 

Abhiso9

New Member
Credits
168
[email protected]:~$ systemd-analyze blame
6.335s NetworkManager-wait-online.service
3.496s dev-nvme0n1p7.device
3.257s plymouth-quit-wait.service
2.551s snap-whatsie-35.mount
1.794s snap-snapd-11588.mount
1.769s snap-gnome\x2d3\x2d34\x2d1804-66.mount
1.703s snap-snap\x2dstore-518.mount
1.647s snap-whatsie-24.mount
1.563s snap-qt513-20.mount
1.492s snap-qt513-19.mount
1.446s snapd.service
1.407s snap-canonical\x2dlivepatch-98.mount
1.399s snap-p3x\x2donenote-120.mount
1.318s snap-core-10958.mount
1.237s dev-loop1.device
1.236s dev-loop4.device
1.235s snap-gtk\x2dcommon\x2dthemes-1514.mount
1.235s snap-gtk\x2dcommon\x2dthemes-1515.mount
1.234s snap-p3x\x2donenote-119.mount
1.149s dev-loop2.device
1.124s dev-loop3.device
1.113s dev-loop9.device
1.098s dev-loop5.device
lines 1-23...skipping...
6.335s NetworkManager-wait-online.service
3.496s dev-nvme0n1p7.device
3.257s plymouth-quit-wait.service
2.551s snap-whatsie-35.mount
1.794s snap-snapd-11588.mount
1.769s snap-gnome\x2d3\x2d34\x2d1804-66.mount
1.703s snap-snap\x2dstore-518.mount
1.647s snap-whatsie-24.mount
1.563s snap-qt513-20.mount
1.492s snap-qt513-19.mount
1.446s snapd.service
1.407s snap-canonical\x2dlivepatch-98.mount
1.399s snap-p3x\x2donenote-120.mount
1.318s snap-core-10958.mount
1.237s dev-loop1.device
1.236s dev-loop4.device
1.235s snap-gtk\x2dcommon\x2dthemes-1514.mount
1.235s snap-gtk\x2dcommon\x2dthemes-1515.mount
1.234s snap-p3x\x2donenote-119.mount
1.149s dev-loop2.device
1.124s dev-loop3.device
1.113s dev-loop9.device
1.098s dev-loop5.device
1.065s dev-loop0.device
1.054s dev-loop6.device
925ms dev-loop8.device
848ms dev-loop16.device
811ms dev-loop7.device
791ms dev-loop17.device
436ms snap-core18-1997.mount
374ms dev-loop10.device
364ms systemd-logind.service
345ms dev-loop11.device
282ms snap-gnome\x2d3\x2d28\x2d1804-145.mount
272ms snap-snapd-11841.mount
260ms dev-loop12.device
245ms tlp.service
223ms snap-core-11081.mount
208ms dev-loop13.device
207ms snap-vlc-2103.mount
170ms snap-core18-1988.mount
167ms fwupd.service
156ms networkd-dispatcher.service
152ms systemd-journal-flush.service
145ms dev-loop14.device
139ms systemd-resolved.service
131ms systemd-timesyncd.service
122ms udisks2.service
120ms accounts-daemon.service
97ms apparmor.service
82ms systemd-journald.service
82ms avahi-daemon.service
80ms upower.service
lines 1-53



















































6.335s NetworkManager-wait-online.service
3.496s dev-nvme0n1p7.device
3.257s plymouth-quit-wait.service
2.551s snap-whatsie-35.mount
1.794s snap-snapd-11588.mount
1.769s snap-gnome\x2d3\x2d34\x2d1804-66.mount
1.703s snap-snap\x2dstore-518.mount
1.647s snap-whatsie-24.mount
1.563s snap-qt513-20.mount
1.492s snap-qt513-19.mount
1.446s snapd.service
1.407s snap-canonical\x2dlivepatch-98.mount
1.399s snap-p3x\x2donenote-120.mount
1.318s snap-core-10958.mount
1.237s dev-loop1.device
1.236s dev-loop4.device
1.235s snap-gtk\x2dcommon\x2dthemes-1514.mount
1.235s snap-gtk\x2dcommon\x2dthemes-1515.mount
1.234s snap-p3x\x2donenote-119.mount
1.149s dev-loop2.device
1.124s dev-loop3.device
1.113s dev-loop9.device
1.098s dev-loop5.device
1.065s dev-loop0.device
1.054s dev-loop6.device
925ms dev-loop8.device
848ms dev-loop16.device
811ms dev-loop7.device
791ms dev-loop17.device
436ms snap-core18-1997.mount
374ms dev-loop10.device
364ms systemd-logind.service
345ms dev-loop11.device
282ms snap-gnome\x2d3\x2d28\x2d1804-145.mount
272ms snap-snapd-11841.mount
260ms dev-loop12.device
245ms tlp.service
223ms snap-core-11081.mount
208ms dev-loop13.device
207ms snap-vlc-2103.mount
170ms snap-core18-1988.mount
167ms fwupd.service
156ms networkd-dispatcher.service
152ms systemd-journal-flush.service
145ms dev-loop14.device
139ms systemd-resolved.service
131ms systemd-timesyncd.service
122ms udisks2.service
120ms accounts-daemon.service
97ms apparmor.service
82ms systemd-journald.service
82ms avahi-daemon.service
80ms upower.service
80ms polkit.service
80ms bluetooth.service
79ms NetworkManager.service
75ms systemd-udev-trigger.service
70ms [email protected]
70ms switcheroo-control.service
lines 10-59
 

MatsuShimizu

Active Member
Credits
1,751

KGIII

Super Moderator
Staff member
Gold Supporter
Credits
19,769
Snaps add a lot to the boot time. It is what it is.

I've never tried masking them. I suspect that they'd still start and run, but slower, if you tried masking them.

As for the other services, many of those can be masked and the system will still run fine. Don't bother masking "plymouth-quit-wait.service", as that's a symptom and not a cause. Masking that one won't actually do any good.
 

MatsuShimizu

Active Member
Credits
1,751
Snaps add a lot to the boot time. It is what it is.
I've never tried masking them. I suspect that they'd still start and run, but slower, if you tried masking them.
Then, the only option for the OP is to remove the snap.

@Abhiso9, you can follow the link below for instructions to remove snap and make your PC boot faster. But after that, you won't be able to use Whatsapp/WhatSie on your Ubuntu PC.
 

KGIII

Super Moderator
Staff member
Gold Supporter
Credits
19,769
Then, the only option for the OP is to remove the snap.
They can *try* masking them, or just live with the slower boot. I don't have much experience with snaps. I usually disable them entirely. So, I've never masked them. If that did work, and I don't know if it will, then I suspect the snap app itself would then start slow when they did go to use it.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Latest posts

Top