codear's questions

I have been checking some systemd-analyze outputs and I actually don't have a crucial problem with my boot time but just wondering whether I can decrease it further. I'd like to mention that I'm using an SSD and Ubuntu is my only OS.

systemd-analyze
Startup finished in 5.450s (firmware) + 565ms (loader) + 2.632s (kernel) + 10.086s (userspace) = 18.734s 
graphical.target reached after 10.071s in userspace

systemd-analyze blame
          6.607s NetworkManager-wait-online.service
          5.660s fwupd.service
          5.042s bolt.service
          4.134s plymouth-quit-wait.service
          1.579s dev-sda2.device
          1.552s systemd-backlight@backlight:intel_backlight.service
          1.367s plymouth-read-write.service
          1.211s snapd.service
           903ms systemd-logind.service
           572ms systemd-journald.service
           555ms dev-loop9.device
           523ms dev-loop6.device
           515ms man-db.service
           499ms dev-loop8.device
           478ms dev-loop5.device
           472ms dev-loop13.device
           448ms dev-loop7.device
           441ms dev-loop11.device
           438ms dev-loop10.device
           432ms dev-loop12.device
           415ms udisks2.service
           406ms dev-loop14.device
           319ms snap-gnome\x2d3\x2d28\x2d1804-71.mount

graphical.target @10.071s
└─multi-user.target @10.071s
  └─kerneloops.service @10.042s +27ms
    └─network-online.target @10.032s
      └─NetworkManager-wait-online.service @3.422s +6.607s
        └─NetworkManager.service @3.224s +186ms
          └─dbus.service @3.218s
            └─basic.target @3.211s
              └─sockets.target @3.211s
                └─snapd.socket @3.208s +2ms
                  └─sysinit.target @3.205s
                    └─systemd-backlight@backlight:intel_backlight.service @1.468s +1.552s
                      └─system-systemd\x2dbacklight.slice @1.467s
                        └─system.slice @212ms
                          └─-.slice @212ms

I already tried the following:

$ sudo apt install --reinstall grub
$ sudo apt install --reinstall grub2-common
$ sudo apt install --reinstall grub-efi-amd64
$ sudo apt install --reinstall grub-efi-amd64-bin
$ sudo apt autoremove
$ sudo apt install grub-efi-amd64-signed

I get this:

Errors were encountered while processing:
 grub-efi-amd64-signed
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Since my topic was marked as duplicate, I showed the generosity to double check the same topic which I've already checked.

ii  linux-headers-4.15.0-39                4.15.0-39.42 all          Header files related to Linux kernel version 4.15.0
ii  linux-headers-4.15.0-39-generic        4.15.0-39.42 amd64        Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii  linux-image-4.15.0-39-generic          4.15.0-39.42 amd64        Signed kernel image generic

nodes are below and I don't know how to empty them:

Filesystem     Inodes IUsed IFree IUse% Mounted on
udev             978K   535  977K    1% /dev
tmpfs            985K  1.1K  984K    1% /run
/dev/sda2         59M  176K   59M    1% /
tmpfs            985K    92  985K    1% /dev/shm
tmpfs            985K     5  985K    1% /run/lock
tmpfs            985K    18  985K    1% /sys/fs/cgroup
/dev/loop0        747   747     0  100% /snap/gnome-system-monitor/57
/dev/loop4       1.7K  1.7K     0  100% /snap/gnome-logs/45
/dev/loop7        27K   27K     0  100% /snap/gnome-3-26-1604/74
/dev/loop1        13K   13K     0  100% /snap/core/5742
/dev/loop3       1.6K  1.6K     0  100% /snap/gnome-characters/139
/dev/loop6         35    35     0  100% /snap/canonical-livepatch/50
/dev/loop5        24K   24K     0  100% /snap/spotify/26
/dev/loop8        13K   13K     0  100% /snap/core/5897
/dev/loop9       1.3K  1.3K     0  100% /snap/gnome-calculator/260
/dev/loop2        27K   27K     0  100% /snap/gtk-common-themes/818
/dev/sda1           0     0     0     - /boot/efi
tmpfs            985K    24  985K    1% /run/user/121
tmpfs            985K    35  985K    1% /run/user/1000

I recently switched from Kali/Windows 10 to Ubuntu 18.04.

Specs:

• CPU: Intel i5 7200U
• RAM: 8GB
• GPU: Nvidia 940mx and a dedicated Intel GPU
• HDD: 1TB

With the above specs I get a 1 minute 15 second boot time and after I login with my password it takes another 15 seconds. Is this normal with a HDD? Should I buy an SSD or is there something wrong?

 4:06:03 PM gnome-logs: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
 4:04:11 PM systemd: Started GNOME Terminal Server.
 4:04:11 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.gnome.Terminal'
 4:04:10 PM systemd: Starting GNOME Terminal Server...
 4:04:10 PM dbus-daemon: [session uid=1000 pid=1348] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.25' (uid=1000 pid=1492 comm="/usr/bin/gnome-shell " label="unconfined")
 4:03:36 PM packagekitd: resolve transaction /186_dcebceda from uid 1000 finished with success after 581ms
 4:03:24 PM systemd: Started GNOME Terminal Server.
 4:03:24 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.gnome.Terminal'
 4:03:24 PM gnome-shell: Object Clutter.Clone (0x55a5642d7bf0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
 4:03:24 PM systemd: Starting GNOME Terminal Server...
 4:03:24 PM dbus-daemon: [session uid=1000 pid=1348] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.25' (uid=1000 pid=1492 comm="/usr/bin/gnome-shell " label="unconfined")
 4:03:09 PM systemd: Started Hostname Service.
 4:03:09 PM dbus-daemon: [system] Successfully activated service 'org.freedesktop.hostname1'
 4:03:08 PM systemd: Starting Hostname Service...
 4:03:08 PM dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.118' (uid=1000 pid=2891 comm="gnome-control-center -s system " label="unconfined")
 4:03:01 PM packagekitd: resolve transaction /185_eaebeaba from uid 1000 finished with success after 530ms
 4:02:58 PM gdm-x-session: (II) modeset(0): Modeline "1920x1080"x0.0  141.40  1920 1968 2000 2142  1080 1083 1089 1100 +hsync -vsync (66.0 kHz eP)
 4:02:51 PM systemd: Started GNOME Terminal Server.
 4:02:51 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.gnome.Terminal'
 4:02:51 PM systemd: Starting GNOME Terminal Server...
 4:02:51 PM dbus-daemon: [session uid=1000 pid=1348] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.25' (uid=1000 pid=1492 comm="/usr/bin/gnome-shell " label="unconfined")
 4:02:17 PM gnome-logs: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
 4:01:49 PM wpa_supplicant: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=58500
 4:01:48 PM gnome-logs: Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not work as expected
 4:01:47 PM packagekitd: resolve transaction /184_babaddec from uid 1000 finished with success after 416ms
 4:01:45 PM snap-confine: main.go:192: cannot change mount namespace of snap "gnome-logs" according to change mount (/snap/gtk-common-themes/818/share/icons/Suru /snap/gnome-logs/45/data-dir/icons/Suru none bind,ro 0 0): cannot use "/snap/gtk-common-themes/818/share/icons/Suru" as bind-mount source: not a directory
 4:01:43 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.gnome.Calendar'
 4:01:43 PM systemd: Started GNOME Terminal Server.
 4:01:43 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.gnome.Terminal'
 4:01:43 PM systemd: Starting GNOME Terminal Server...
 4:01:43 PM dbus-daemon: [session uid=1000 pid=1348] Activating service name='org.gnome.Nautilus' requested by ':1.25' (uid=1000 pid=1492 comm="/usr/bin/gnome-shell " label="unconfined")
 3:57:52 PM systemd: Started Message of the Day.
 3:55:31 PM gnome-shell: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.86/org/ayatana/NotificationItem/software_update_available
 3:55:25 PM packagekitd: get-details transaction /183_dedabdab from uid 1000 finished with success after 837ms
 3:55:14 PM gnome-software: Unable to acquire bus name 'org.gnome.Software'
 3:55:03 PM rsyslogd: main Q:Reg: worker thread 55a97da74de0 terminated, now 1 active worker threads [v8.32.0 try http://www.rsyslog.com/e/2439 ]
 3:55:02 PM systemd: Started BAMF Application Matcher Framework.
 3:55:02 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.ayatana.bamf'
 3:55:01 PM systemd: Starting BAMF Application Matcher Framework...
 3:55:00 PM dbus-daemon: [session uid=1000 pid=1348] Activating via systemd: service name='org.ayatana.bamf' unit='bamfdaemon.service' requested by ':1.82' (uid=1000 pid=2035 comm="plank " label="unconfined")
 3:54:59 PM systemd: Started GNOME Terminal Server.
 3:54:59 PM dbus-daemon: [session uid=1000 pid=1348] Successfully activated service 'org.gnome.Terminal'
 3:54:59 PM systemd: Starting GNOME Terminal Server...
 3:54:59 PM dbus-daemon: [session uid=1000 pid=1348] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.25' (uid=1000 pid=1492 comm="/usr/bin/gnome-shell " label="unconfined")
 3:54:59 PM gnome-shell: Object Clutter.Clone (0x55a5642d71d0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
 3:54:44 PM packagekitd: resolve transaction /170_eaaeaeaa from uid 1000 finished with success after 700ms
 3:54:43 PM gnome-software: Only 0 apps for recent list, hiding
 3:54:43 PM packagekitd: get-updates transaction /169_bbbcadad from uid 1000 finished with success after 557ms
 3:54:41 PM systemd: Started Firmware update daemon.
 3:54:41 PM dbus-daemon: [system] Successfully activated service 'org.freedesktop.fwupd'
 3:54:40 PM fwupd: Daemon ready for requests

systemd-analyze blame
         26.084s systemd-journal-flush.service
         21.290s dev-sda2.device
         18.962s plymouth-quit-wait.service
         11.013s NetworkManager-wait-online.service
         10.526s plymouth-start.service
          9.068s systemd-udevd.service
          8.571s networkd-dispatcher.service
          7.261s dev-loop9.device
          7.045s dev-loop8.device
          6.686s udisks2.service
          6.508s dev-loop4.device
          6.466s dev-loop5.device
          6.437s dev-loop6.device
          6.409s dev-loop7.device
          6.246s grub-common.service
          6.145s dev-loop0.device
          6.040s dev-loop3.device
          5.616s dev-loop1.device
          5.609s dev-loop2.device
          5.597s snapd.service
          5.241s ModemManager.service
          5.206s snap-gnome\x2dlogs-45.mount
          5.078s bolt.service

I'm using Ubuntu 17.10 64-bit. Steam gets stuck as in the following image. What can I do?

Specs: 
Processor       : Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory      : 8069MB (2241MB used)
Machine Type        : Notebook
Operating System        : Ubuntu 17.10
-Display-
Resolution      : 1920x1080 pixels
OpenGL Renderer     : Unknown
X11 Vendor      : The X.Org Foundation
-Audio Devices-
Audio Adapter       : HDA-Intel - HDA Intel PCH