Announcement

Collapse
No announcement yet.

Desktop comes very slowly after I push power button

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [System] Desktop comes very slowly after I push power button

    I dont know kubuntu version etc. so I open this topic here.Opening is very slow.I wait your suggestions.My kubuntu is setuped on ssd.

    ahmet@ahmet:~$ systemd-analyze
    Startup finished in 7.298s (kernel) + 34.948s (userspace) = 42.246s
    graphical.target reached after 34.938s in userspace
    ahmet@ahmet:~$ systemd-analyze blame
    30.049s NetworkManager-wait-online.service
    2.404s dev-sda2.device
    1.742s tor@default.service
    1.304s snapd.service
    1.240s dev-loop0.device
    1.211s dev-loop1.device
    1.201s dev-loop2.device
    1.174s dev-loop3.device
    1.010s systemd-journal-flush.service
    788ms mpd.service
    784ms systemd-udevd.service
    646ms systemd-logind.service
    640ms avahi-daemon.service
    636ms lm-sensors.service
    630ms pppd-dns.service
    608ms NetworkManager.service
    583ms ModemManager.service
    568ms networkd-dispatcher.service
    483ms udisks2.service
    457ms grub-common.service
    448ms systemd-resolved.service
    420ms systemd-timesyncd.service
    393ms accounts-daemon.service
    392ms gpu-manager.service
    384ms wpa_supplicant.service
    372ms rsyslog.service
    344ms apparmor.service
    268ms upower.service
    224ms phpsessionclean.service
    222ms systemd-fsck@dev-disk-by\x2duuid-B044\x2d884E.service
    189ms thermald.service
    187ms apport.service
    177ms swapdosya.swap
    175ms swapfile.swap
    156ms alsa-restore.service
    156ms keyboard-setup.service
    155ms bluetooth.service
    145ms systemd-rfkill.service
    137ms systemd-udev-trigger.service
    113ms systemd-journald.service
    111ms polkit.service
    lines 1-41


    #2
    Some systems seem to get hit by this where the NetworkManager-wait-online.service takes too long, or cannot connect . Not everyone needs for the network to be up in order to boot, but those using samba, nfs, etc to mount shared drives during boot will need this.

    Try disabling it
    Code:
    systemctl disable NetworkManager-wait-online.service
    systemctl mask NetworkManager-wait-online.service
    Then reboot and see if iotn helps. It will not knock 30+ seconds of f the boot time, as ,many things are started in parallel, but it should make it better

    if it does not help, you can put things back like so

    Code:
    systemctl unmask NetworkManager-wait-online.service
    systemctl enable NetworkManager-wait-online.service

    Comment


      #3
      Originally posted by claydoh View Post
      Some systems seem to get hit by this where the NetworkManager-wait-online.service takes too long, or cannot connect . Not everyone needs for the network to be up in order to boot, but those using samba, nfs, etc to mount shared drives during boot will need this.

      Try disabling it
      Code:
      systemctl disable NetworkManager-wait-online.service
      systemctl mask NetworkManager-wait-online.service
      Then reboot and see if iotn helps. It will not knock 30+ seconds of f the boot time, as ,many things are started in parallel, but it should make it better

      if it does not help, you can put things back like so

      Code:
      systemctl unmask NetworkManager-wait-online.service
      systemctl enable NetworkManager-wait-online.service
      thank you now its better but i wonder 23 seconds is good to see desktop or can you give me another advice to make better?
      also why it says 13 seconds when I record 23 secons with chronometers?
      ahmet@ahmet:~$ systemd-analyze
      Startup finished in 7.375s (kernel) + 6.073s (userspace) = 13.449s
      graphical.target reached after 5.381s in userspace
      ahmet@ahmet:~$
      Last edited by comonda2; Aug 17, 2019, 08:28 AM.

      Comment


        #4
        still its very slow...

        ahmet@ahmet:~$ systemd-analyze
        Startup finished in 7.374s (kernel) + 6.377s (userspace) = 13.751s
        graphical.target reached after 5.575s in userspace
        ahmet@ahmet:~$ systemd-analyze blame
        2.181s dev-sda2.device
        1.642s tor@default.service
        1.432s systemd-journal-flush.service
        1.401s snapd.service
        1.172s ModemManager.service
        1.120s dev-loop0.device
        1.094s dev-loop1.device
        1.079s dev-loop2.device
        1.048s udisks2.service
        1.047s dev-loop3.device
        936ms accounts-daemon.service
        857ms grub-common.service
        773ms mpd.service
        739ms avahi-daemon.service
        700ms networkd-dispatcher.service
        682ms bluetooth.service
        653ms thermald.service
        649ms NetworkManager.service
        444ms systemd-udevd.service
        401ms wpa_supplicant.service
        346ms systemd-logind.service
        307ms rsyslog.service
        267ms systemd-resolved.service
        262ms gpu-manager.service
        257ms colord.service
        227ms upower.service
        210ms systemd-fsck@dev-disk-by\x2duuid-B044\x2d884E.service
        192ms apparmor.service
        189ms polkit.service
        175ms phpsessionclean.service
        174ms apport.service
        169ms systemd-timesyncd.service
        167ms swapdosya.swap
        167ms swapfile.swap
        146ms keyboard-setup.service
        127ms systemd-udev-trigger.service
        120ms snap-ktube\x2dmedia\x2ddownloader-4.mount
        117ms snap-gydl-2.mount
        107ms systemd-sysctl.service
        105ms systemd-journald.service
        98ms systemd-rfkill.service
        lines 1-41



        Last edited by comonda2; Aug 18, 2019, 04:42 AM.

        Comment


          #5
          That is not very slow.
          It is actually quite fast.

          You could shave a bit more out of it by getting rid of snaps.
          And tor, if you don't need it.

          Still, unless your goal is to see the desktop before you push the power button... I'd say you're not doing too bad as it is :·)

          [EDIT] You could also edit /etc/default/grub and delete both quiet and splash (and then sudo update-grub) so you can see what goes on at startup and shutdown... and it might shave a few milliseconds off boot too.
          Last edited by Don B. Cilly; Aug 18, 2019, 05:30 AM.

          Comment


            #6
            I want to be sure before do something if I remove dev-loops from startup, system will crash or not?

            Comment


              #7
              Originally posted by Don B. Cilly View Post
              That is not very slow.
              It is actually quite fast.

              You could shave a bit more out of it by getting rid of snaps.
              And tor, if you don't need it.

              Still, unless your goal is to see the desktop before you push the power button... I'd say you're not doing too bad as it is :·)

              [EDIT] You could also edit /etc/default/grub and delete both quiet and splash (and then sudo update-grub) so you can see what goes on at startup and shutdown... and it might shave a few milliseconds off boot too.
              I cant do what vinnywrigh says on the link you pasted.
              I installed
              kde-config-systemd then I wrote snapd.seeded.service on command console but it said me the command is not exist

              Comment


                #8
                Well, as per link, kde-config-systemd did not work for me.
                Not only that, but it messed up my updates and I hat to remove it. Still...
                if you remove snapd, your system will not crash, but whatever snaps were installed won't work anymore.

                To see what snaps you're using you can type:
                lsblk

                Comment


                  #9
                  Originally posted by comonda2 View Post
                  I cant do what vinnywrigh says on the link you pasted.
                  I installed
                  kde-config-systemd then I wrote snapd.seeded.service on command console but it said me the command is not exist
                  OK since my name was invoked hear ,,,,,,,

                  if you installed kde-config-systemd you now have an entry in "system settings" at the bottom of the list called "systemd" if you click it you will get this



                  in the top left of that window is a "filter" drop down , I have it filtering for "services" , if you right click a service line you will get a list of control options



                  choosing to "mask" the service will keep it from loading .

                  from what I see you can mask (snapd.service , ModemManager.service) to start with

                  VINNY
                  i7 4core HT 8MB L3 2.9GHz
                  16GB RAM
                  Nvidia GTX 860M 4GB RAM 1152 cuda cores

                  Comment


                    #10
                    thanks for your help but after restart system loads still dev-loop devices so I save only one second.Why arent they masked?

                    ahmet@ahmet:~$ systemd-analyze
                    Startup finished in 7.307s (kernel) + 5.227s (userspace) = 12.534s
                    graphical.target reached after 5.221s in userspace
                    ahmet@ahmet:~$ systemd-analyze blame
                    2.031s dev-sda2.device
                    1.201s systemd-journal-flush.service
                    1.195s udisks2.service
                    929ms systemd-resolved.service
                    819ms dev-loop0.device
                    817ms grub-common.service
                    813ms dev-loop2.device
                    811ms dev-loop1.device
                    786ms NetworkManager.service
                    761ms gpu-manager.service
                    760ms lm-sensors.service
                    759ms thermald.service
                    752ms pppd-dns.service
                    745ms rsyslog.service
                    640ms networkd-dispatcher.service
                    621ms mpd.service
                    409ms systemd-udevd.service
                    294ms upower.service
                    234ms systemd-logind.service
                    205ms accounts-daemon.service
                    193ms apparmor.service
                    189ms swapdosya.swap
                    189ms wpa_supplicant.service
                    160ms systemd-timesyncd.service
                    156ms keyboard-setup.service
                    156ms systemd-fsck@dev-disk-by\x2duuid-B044\x2d884E.service
                    132ms systemd-udev-trigger.service
                    123ms swapfile.swap
                    121ms systemd-sysctl.service
                    118ms systemd-tmpfiles-setup.service
                    112ms polkit.service
                    108ms systemd-rfkill.service
                    101ms avahi-daemon.service
                    98ms systemd-journald.service
                    96ms systemd-modules-load.service
                    92ms colord.service
                    73ms snap-core-7396.mount
                    72ms plymouth-quit.service
                    61ms apport.service
                    60ms snap-core-7270.mount
                    56ms user@1000.service
                    lines 1-41

                    Comment


                      #11
                      Wow. I like that config-systemd. I wish xfce/gnome had it.
                      Boot Info Script

                      Comment


                        #12
                        I love kde because of its design.before kubuntu logo blackscreen appears for 7 seconds so starting is totally 23 secons instead of 12 seconds which command says.so how can i remove/short this black screen phase?

                        Comment


                          #13
                          As I said,
                          Originally posted by Don B. Cilly View Post
                          You could also edit /etc/default/grub and delete both quiet and splash (and then sudo update-grub) so you can see what goes on at startup and shutdown... and it might shave a few milliseconds off boot too.
                          Why not try it. You can always put them back.
                          It does get rid of the black screen. You get lots of info instead - and if something "hangs", you see it immediately.
                          It's what I use.

                          I also said,
                          Well, as per link, kde-config-systemd did not work for me.
                          Not only that, but it messed up my updates and I hat to remove it.
                          And it seems it didn't for you either.
                          So, maybe try lsblk, see what snaps you are using, and see about getting rid of them.
                          That would definitely shave a few seconds off boot.

                          And if your updates start hanging, you know where to look ;·)

                          Comment


                            #14
                            Originally posted by Don B. Cilly View Post
                            As I said,

                            Why not try it. You can always put them back.
                            It does get rid of the black screen. You get lots of info instead - and if something "hangs", you see it immediately.
                            It's what I use.

                            I also said,

                            And it seems it didn't for you either.
                            So, maybe try lsblk, see what snaps you are using, and see about getting rid of them.
                            That would definitely shave a few seconds off boot.

                            And if your updates start hanging, you know where to look ;·)
                            ok i will try i hope it will be better

                            Comment

                            Working...
                            X