[lubuntu-devel] Lu 20.10 seems to be very slow to boot & log in???

Mon Aug 17 18:58:31 UTC 2020

20.10 stuff should go to "devel" list rather than open Lu-users list . . . .

On Mon, Aug 17, 2020 at 11:13 AM James <bjlockie at lockie.ca> wrote:

>
>
> On 2020-08-17 11:31 a.m., Fritz Hudnut wrote:
>
> Got the SG2 disk out and booted into TW to get the os-prober going to fix
> grub . . . something in ubuntu for the last year has been breaking grub on
> apt upgrades . . . there is a bug report on it . . . devs seem to be
> "stuck" on a fix, but it is "irritating" to have to "repair grub" each time
> after running apt as I did yesterday with Lu 20.10.
>
> OK, the good news is that after that upgrade in Lu yesterday the boot time
> seemed a little faster, and the log in password wasn't exactly "zippy" but
> it did at least "respond" after one click  . . . but there was a delay.  I
> ran the analyze blame command and in Lu it brought back a bunch of lines, I
> copied the top 25 or so . . . but again these times were an improvement
> from the pre- 300 package upgrade from yesterday.
>
> "systemd-analyze blame
> 23.068s man-db.service
>  >
> 16.522s NetworkManager-wait-online.service
>  >
> 12.036s udisks2.service
>   >
> 11.315s snapd.service
>   >
>  9.028s networkd-dispatcher.service
>   >
>  8.032s dev-sdc7.device
>   >
>  6.735s accounts-daemon.service
>   >
>  6.267s systemd-journal-flush.service
>   >
>  5.326s dev-loop0.device
>  >
>  5.253s polkit.service
>  >
>  5.061s NetworkManager.service
>  >
>  5.057s avahi-daemon.service
>  >
>  5.054s bluetooth.service
>   >
>  5.026s dundee.service
>  >
>  4.989s ofono.service
>   >
>  4.973s wpa_supplicant.service
>  >
>  4.973s systemd-logind.service
>  >
>  4.101s ModemManager.service
>  >
>  3.919s dev-loop2.device
>  >
>  3.918s dev-loop1.device
>  >
>  3.860s dev-loop4.device
>  >
>  3.849s dev-loop5.device
>  >
>  3.843s dev-loop3.device
>  >
>  3.765s dev-loop7.device
>  >
>  3.742s dev-loop6.device
>  >
>  3.552s gpu-manager.service
>   >
>  3.548s logrotate.service
>   >
>  2.550s systemd-udevd.service
>   >
>  1.709s rsyslog.service
>   >
>  1.545s grub-initrd-fallback.service
>  >
>  1.410s apport.service
>  >
>  1.373s grub-common.service
>   >
>  1.219s systemd-resolved.service
>  >
>  1.057s colord.service
>  >
>  1.041s systemd-fsck at dev-disk-by
> \x2duuid-598d1ebe\x2d6ad9\x2d4491\x2db95a\x2>
>   992ms apparmor.service
>  >
>   926ms upower.service
>  >
>   881ms systemd-modules-load.service
>  >
>   757ms systemd-fsck at dev-disk-by\x2duuid-67E3\x2d17ED.service
>   >
>   675ms snapd.seeded.service
>  >
>   663ms systemd-sysusers.service
>  >
>   563ms keyboard-setup.service
>  >
>   551ms systemd-journald.service      "
>
> On Mon, Aug 17, 2020 at 7:57 AM Fritz Hudnut <este.el.paz at gmail.com>
> wrote:
>
>> James:
>>
>> Seems like running Lu apt yesterday showing some "grub" packages again
>> wiped grub . . . ???  So cold booting only provided U-MATE . . . actually
>> doesn't seem any faster than the Lu option . . . .
>>
>> Since they both are 20.10  I ran what I thought is your suggested command
>> . . . once after logging in and launching FF . . . then half an hour later
>> after going thru emails and social media stuff . . . got the same errors:
>>
>> "$ systemd-analyze blame
>> Bootup is not yet finished
>> (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
>> Please try again later.
>> Hint: Use 'systemctl list-jobs' to see active jobs"
>>
>> When I get grub straightened out I'll try it in Lu to see what that
>> provides . . . .
>>
>> On Sun, Aug 16, 2020 at 7:05 PM James Lockie <bjlockie at lockie.ca> wrote:
>>
>>> Blame will list all the processes so you can see what is slow.
>>> I had a problem with alsa timing out on something.
>>> I forget the fix (it might have gone away).
>>>
>>> On August 16, 2020 21:26:57 Fritz Hudnut <este.el.paz at gmail.com> wrote:
>>>
>>>> Alrighty . . . well I'll try to run that command when I get back to my
>>>> Lu install . . . .
>>>>
>>>> On Sun, Aug 16, 2020 at 5:30 PM James Lockie <bjlockie at lockie.ca>
>>>> wrote:
>>>>
>>>>> That blame command will print the times for the boot.
>>>>> Maybe try the auto login.
>>>>>
>>>>> On August 16, 2020 20:00:24 Fritz Hudnut <este.el.paz at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> James:
>>>>>>
>>>>>> OK, well thanks for the reply . . . after I posted that email I ran
>>>>>> "apt" and there were roughly "300" packages to update, but I don't know if
>>>>>> "systemd" was in there or not . . . .
>>>>>>
>>>>>> Anything to "monitor" in this regard??  It is much slower to get to
>>>>>> log in window and then really slow getting from there into GUI . . . .
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Aug 16, 2020 at 4:13 PM James Lockie <bjlockie at lockie.ca>
>>>>>> wrote:
>>>>>>
>>>>>>> systemd-analyze blame
>>>>>>> I think.
>>>>>>>
>>>>>>> On August 16, 2020 18:49:10 Fritz Hudnut <este.el.paz at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Posting here in case the helm is manned . . . in comparison to my
>>>>>>>> other linux installs and more basically in comparison to my U-MATE 20.10
>>>>>>>> install . . . the Lu boot time is "slower" to run through what must be the
>>>>>>>> "dmesg" data . . . which it says is "system check" . . . and possibly could
>>>>>>>> be "cancelled" . . . might save some time . . . .
>>>>>>>>
>>>>>>>> But, more of a problem is when the log in window shows and I type
>>>>>>>> my password and hit return . . . nothing happens . . . and I wind up
>>>>>>>> hitting return key several times before the system decides to load the
>>>>>>>> desktop????
>>>>>>>>
>>>>>>>> It's happened enough times that I am now taking time too report the
>>>>>>>> problem here.
>>>>>>>>
>>>>>>>> F
>>>>>>>> --
>>>>>>>> Lubuntu-devel mailing list
>>>>>>>> Lubuntu-devel at lists.ubuntu.com
>>>>>>>> Modify settings or unsubscribe at:
>>>>>>>> https://lists.ubuntu.com/mailman/listinfo/lubuntu-devel
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20200817/f3fb4b2e/attachment-0001.html>