After logging in and the desktop appearing there is a delay of about 30secs to 45secs and then the login sound plays and I gain control of the desktop - can’t do anything until after this pause. Is anybody else experiencing this and how would you even go about trying to troubleshoot this?
Its like something is trying to start in the background and holding up the rest of the startup process.
Also during the boot process I notce quite a few errors being reported but dont have time to read then. Is there anyway to pause the boot process or perhaps tje whole boot process is logged to some file? I’ve looked for /var/log/boot.log but there is no such file? Any ideas?
Well besides the basic speed of your computer and its hard drives, I have seen this delay myself. On many occasions, it can be blamed on the activation of your network, with wireless networks being the worst. Second is the activation of mapped drives over a network. I have seen some suggestions or reducing the network startup delays as helping in speeding up your system. I have also found that modifying your /etc/fstab file can be helpful in reducing startup delays. I place all real local drives mapping at the top of the script and if you have more than one hard drive, arrange them in hardware and partition order and do not have drive mappings above and below the proc statement. Buying and installing a SSD drive can also be very helpful in speeding up startup times. I have lots of drive mappings in my fstab file which can affect startup speed when placed in random order as can seem to happen sometimes.
What is strange though is thatm, sometimes from being logged in I can reboot my machine and the system will come back up, I will login and that delay will not be there and I can start using the desktop straight away. Maybe its something related to whether the boot process is a cold boot or a soft-boot.
So I do think that you are correct about the difference in cold vers warm booting. By the way, I do have a bash script, if you have not seen it, that can speed up a restart when you are restarting from-to openSUSE. Check this bash script out:
There has been discussion of this problem in 11.4 (sorry, can’t find it now). It was suggested that Aparmor amd Pulse were somehow involved. I deselect pulse when installing and don’t have that problem anymore. Aparmor isn’t installed by default now anyway. Hope that helps.
Hi all, thx for the ^ info, some useful tips. What is the application tracker?
Also, is there any way to visibly see the boot process as it happens and maybe even time each process as it happens? Most of the boot process is hidden behind the gui and its possible for some errors to not seen. I’ve checked the logs in /var/log/ but I also see errors at the start of boot which don’t appear in any of the logs. What I’m really after is a more thorough log of the boot process. I understand that one of the (ctrl+alt+f#) consoles (tty#) used to provide a textual log of the boot process but it seem that has gone with 12.1.
It must be possible to do a dump of the boot process to a text file somehow.