My Budgie is taking a very long time to boot
Which log or what could i do to find what is making it so long to reach the User/password prompt
tks
JF
once in, it works well
i7, SSD drive, 16 gig ram
My Budgie is taking a very long time to boot
Which log or what could i do to find what is making it so long to reach the User/password prompt
tks
JF
once in, it works well
i7, SSD drive, 16 gig ram
Is this something new or has it always taken a long time?
Run
systemd-analyze blame
This will show how long processes are taking during boot and hopefully will indicate a likely area to concentrate on
2min 27.138s snapd.seeded.service
56.385s snapd.service
7.066s configure-printer@usb-001-003.service
3.692s NetworkManager-wait-online.service
832ms fwupd.service
622ms keyboard-setup.service
610ms motd-news.service
546ms apparmor.service
475ms dev-sda1.device
471ms plymouth-start.service
364ms snap-canonical\x2dlivepatch-42.mount
363ms vboxdrv.service
354ms lightdm.service
352ms plymouth-quit-wait.service
352ms snap-telegram\x2ddesktop-264.mount
336ms snap-obs\x2dstudio-55.mount
295ms systemd-journal-flush.service
286ms NetworkManager.service
279ms snap-ubuntu\x2dbudgie\x2dwelcome-57.mount
257ms snap-keepassxc-39.mount
240ms snap-core-4917.mount
231ms snap-signal\x2ddesktop-76.mount
216ms snap-core-5145.mount
208ms snap-spotify-16.mount
206ms systemd-timesyncd.service
206ms snap-telegram\x2ddesktop-266.mount
197ms tlp.service
193ms snap-ubuntu\x2dbudgie\x2dwelcome-61.mount
188ms systemd-logind.service
179ms snap-core-4830.mount
176ms snap-ubuntu\x2dbudgie\x2dwelcome-60.mount
174ms snap-htop-959.mount
164ms systemd-resolved.service
153ms snap-spotify-19.mount
I had this problem
It dissapeared
Just came back
tks for your help
JF
Do I need to give you all the lines ? Very long / several of them
2min 27.138s snapd.seeded.service
56.385s snapd.service
Those two lines there look like the culprits.
Are you fully up to date?
sudo apt update && sudo apt dist-upgrade
That should run without warnings or errors
In that thread press and holding the shift button was the suggested workaround or using grub and booting with an older kernel
But it should have been fixed by now with a recent kernel update
pressing shift at regular interval allowed to boot with kernel 4.15.0.20 instead of 4.15.0.24 and it booted within seconds
Problem solved
JF
odd - the current kernel is 4.15.0.33 - does it still take a long time to boot with the .33 kernel as well?
HOw can I go / force an update to .33 (as normal updates didnāt bring me there) ?? I was at .24 before dowgrading to .20
Tks !
sudo apt update && sudo apt dist-upgrade
After reboot
jeff@desktop-office:~$ uname -a
Linux desktop-office 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
do double check that in software-updater - settings - updates tab that the first three tick boxes are ticked - the āsecurityā checkbox is important to ensure you get the latest kernel
huh?
https://launchpad.net/ubuntu/+source/linux-meta
You can see that the security rep should have .33 - .20 was the version that 18.04 was originally shipped with.
Try changing your mirror āUbuntu Softwareā tab - and the āDownload fromā drop-down
CHanged it from Canada to MAIN
jeff@desktop-office:~$ sudo apt update && sudo apt dist-upgrade
Hit:1 http://prerelease.keybase.io/deb stable InRelease
Hit:2 http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:5 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease
Hit:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:7 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Hit:8 https://s3-us-west-2.amazonaws.com/brave-apt bionic InRelease
Hit:9 http://ppa.launchpad.net/remmina-ppa-team/remmina-next/ubuntu bionic InRelease
Hit:10 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease
Hit:11 http://ppa.launchpad.net/tista/adapta/ubuntu bionic InRelease
Hit:12 http://ppa.launchpad.net/ubuntubudgie/backports/ubuntu bionic InRelease
Hit:13 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
Reading package listsā¦ Done
Building dependency tree
Reading state informationā¦ Done
All packages are up to date.
Reading package listsā¦ Done
Building dependency tree
Reading state informationā¦ Done
Calculating upgradeā¦ Done
The following packages were automatically installed and are no longer required:
linux-aws-tools-4.15.0-1013 linux-aws-tools-4.15.0-1014 linux-aws-tools-4.15.0-1015 linux-aws-tools-4.15.0-1017 linux-aws-tools-4.15.0-1018
linux-aws-tools-4.15.0-1019
Use āsudo apt autoremoveā to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
hmm - you have got the google-chrome added more than once - delete the duplicates from the other tab.
Check that you have linux-generic and linux-image-generic installed
sudo apt install --reinstall iinux-generic linux-image-generic
jeff@desktop-office:~$ sudo apt install --reinstall iinux-generic linux-image-generic Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package iinux-generic jeff@desktop-office:~$
absolutely baffling!
On the āUbuntu Softwareā tab you do have the āMainā checkbox ticked (first three should be ticked at a minimum really)