Pop!_OS 19.04 ou LinuxMint-19.1-Cinnamon [RESOLVIDO]
25. Re: Pop!_OS 19.04 ou LinuxMint-19.1-Cinnamon
MMonks
(usa KUbuntu)
Enviado em 13/07/2019 - 10:58h
Você pode me dizer se o tempo de boot também é demorado? Abra o terminal ao iniciar a máquina e digite nele
systemd-analyze blame
marcio@marcio-Inspiron-N4030:~$ systemd-analyze blame
22.633s dev-sda1.device
16.823s systemd-journal-flush.service
16.771s apt-daily-upgrade.service
13.149s ufw.service
11.261s lvm2-monitor.service
10.976s keyboard-setup.service
10.817s systemd-modules-load.service
10.533s snapd.service
10.238s systemd-tmpfiles-setup-dev.service
7.079s NetworkManager.service
6.483s networkd-dispatcher.service
5.352s ubuntu-system-adjustments.service
4.965s udisks2.service
3.991s accounts-daemon.service
3.669s ModemManager.service
3.184s wpa_supplicant.service
2.222s grub-common.service
1.911s lightdm.service
1.902s plymouth-quit-wait.service
1.866s gpu-manager.service
1.796s dns-clean.service
1.455s thermald.service
1.421s apparmor.service
Para sabermos a lista de serviços ativos:
systemctl list-unit-files --type=service | grep enabled
marcio@marcio-Inspiron-N4030:~$ systemctl list-unit-files --type=service | grep enabled
accounts-daemon.service enabled
anacron.service enabled
apparmor.service enabled
autovt@.service enabled
avahi-daemon.service enabled
blk-availability.service enabled
casper.service enabled
console-setup.service enabled
cron.service enabled
cups-browsed.service enabled
cups.service enabled
dbus-fi.w1.wpa_supplicant1.service enabled
dbus-org.freedesktop.Avahi.service enabled
dbus-org.freedesktop.ModemManager1.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.freedesktop.resolve1.service enabled
dbus-org.freedesktop.thermald.service enabled
dns-clean.service enabled
getty@.service enabled
gpu-manager.service enabled
hddtemp.service enabled
irqbalance.service enabled
kerneloops.service enabled
keyboard-setup.service enabled
lm-sensors.service enabled
lvm2-monitor.service enabled
mintsystem.service enabled
ModemManager.service enabled
network-manager.service enabled
networkd-dispatcher.service enabled
networking.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager-wait-online.service enabled
NetworkManager.service enabled
ondemand.service enabled
openvpn.service enabled
pppd-dns.service enabled
rsync.service enabled
rsyslog.service enabled
setvtrgb.service enabled
snapd.autoimport.service enabled
snapd.core-fixup.service enabled
snapd.seeded.service enabled
snapd.service enabled
snapd.system-shutdown.service enabled
syslog.service enabled
systemd-fsck-root.service enabled-runtime
systemd-resolved.service enabled
systemd-timesyncd.service enabled
thermald.service enabled
ubuntu-system-adjustments.service enabled
udisks2.service enabled
ufw.service enabled
ureadahead.service enabled
wpa_supplicant.service enabled
Veja se ajuda!
Interessante, mas é bom ter cuidado ao remover o pacote bluez, dependendo da distro, ele pode levar junto boa parte do ambiente gráfico. Esse pacote é similar ao pacote gnome-keyring, então todo cuidado é pouco.
No caso de não poder ser removido, o ideal é dar um mask nele através do systemctl, evitando que seja ativo.
Pesquisei sobre esse pacote e julguei seguro removê-lo. Melhorou bastante.
Agora, ao ligar o notebook, ele está consumindo entre 5% e 6% de CPU e uns 950MB de RAM.