Black screen and delay before logging into Cinnamon

Rehdon
Level 3
Level 3
Posts: 172
Joined: Tue Nov 29, 2011 9:18 am

Black screen and delay before logging into Cinnamon

Hi guys,
I've just installed LM 20 Cinnamon edition on a new partition and made it my main version of LM to use. So far so good, but a couple of days after using it (and installing more software) I started having problems logging in:

1. the boot process seems to be normal although a little slower than in the past
2. after keying my password the screen goes black, I can't even see the mouse pointer
3. after about 30-40 seconds Cinnamon comes to life, yay!!!

I've done some research on the forums, people are pointing their fingers to lots of possible causes, but I guess it could be a either a problem with the Nvidia drivers (running nvidia-driver-440-server at the moment because that is what it was suggested after install time, but now nvidia-driver-440 is the suggested one!) or with some of the software I installed (someone wrote about x86 libraries included with Wine, I am somewhat more skeptical about that).

Any ideas? xsession.errors shows some warnings, but I don't see a possible cause there.

Thank you in advance,

R

Rehdon
Level 3
Level 3
Posts: 172
Joined: Tue Nov 29, 2011 9:18 am

Re: Black screen and delay before logging into Cinnamon

Post by Rehdon »

smurphos wrote: ↑

Fri Aug 07, 2020 3:10 am

Can we see the output of cat ~/.xsession-errors run just after logging in?

Sure thing, here you go, this is just after the log in and before I launched Firefox:

Code: Select all

                  dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting XAUTHORITY=/home/roby/.Xauthority dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting SHELL=/bin/bash dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 dbus-update-activation-environment: setting LANGUAGE=it_IT dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge dbus-update-activation-environment: setting PWD=/home/roby dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon dbus-update-activation-environment: setting LOGNAME=roby dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1 dbus-update-activation-environment: setting XAUTHORITY=/home/roby/.Xauthority dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/roby dbus-update-activation-environment: setting GDM_LANG=it_IT dbus-update-activation-environment: setting HOME=/home/roby dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 dbus-update-activation-environment: setting LANG=it_IT.UTF-8 dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 dbus-update-activation-environment: setting XDG_SESSION_CLASS=user dbus-update-activation-environment: setting USER=roby dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting SHLVL=1 dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000 dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/roby/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share dbus-update-activation-environment: setting PATH=/home/roby/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games dbus-update-activation-environment: setting GDMSESSION=cinnamon dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment [cinnamon-settings-daemon-smartcard] Failed to start: nessun driver smartcard adatto disponibile [cinnamon-settings-daemon-smartcard] Failed to start: nessun driver smartcard adatto disponibile Cinnamon warning: Log level 128: unsetenv() is not thread-safe and should not be used after threads are created Clutter-Message: 08:32:19.333: Sync method: PRESENTATION TIME Cjs-Message: 08:32:19.457: JS LOG: About to start Cinnamon Cjs-Message: 08:32:19.631: JS LOG: [LookingGlass/info] Cinnamon.AppSystem.get_default() started in 172 ms Cjs-Message: 08:32:19.640: JS LOG: [LookingGlass/info] loading user theme: /usr/share/themes/Mint-Y-Dark-Blue/cinnamon/cinnamon.css Cjs-Message: 08:32:19.658: JS LOG: [LookingGlass/info] added icon directory: /usr/share/themes/Mint-Y-Dark-Blue/cinnamon  (cinnamon:1548): Cjs-WARNING **: 08:32:19.658: Some code accessed the property 'BackgroundManager' on the module 'backgroundManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Cinnamon warning: Log level 128: posix_spawn avoided (fd close requested)   (cinnamon:1548): Cjs-WARNING **: 08:32:19.775: Some code accessed the property 'EdgeFlipper' on the module 'edgeFlip'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Cjs-Message: 08:32:19.776: JS LOG: [LookingGlass/info] loaded at Sat Aug 08 2020 08:32:19 GMT+0200 (CEST) Cjs-Message: 08:32:19.777: JS LOG: Cinnamon started at Sat Aug 08 2020 08:32:19 GMT+0200 (CEST) Cjs-Message: 08:32:19.788: JS LOG: [LookingGlass/info] ExtensionSystem started in 2 ms Cjs-Message: 08:32:19.788: JS LOG: [LookingGlass/info] DeskletManager started in 2 ms Cjs-Message: 08:32:19.788: JS LOG: [LookingGlass/info] SearchProviderManager started in 2 ms openGL version 3.1 detected (GL3 Cogl Driver) Cjs-Message: 08:32:19.823: JS LOG: [LookingGlass/info] Role locked: tray Cjs-Message: 08:32:19.825: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 14 ms Cjs-Message: 08:32:19.851: JS LOG: [LookingGlass/info] Loaded applet show-desktop@cinnamon.org in 26 ms Cjs-Message: 08:32:19.882: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 32 ms St-Message: 08:32:19.887: cogl npot texture sizes SUPPORTED Cjs-Message: 08:32:19.896: JS LOG: [LookingGlass/info] Role locked: notifications Cjs-Message: 08:32:19.903: JS LOG: [LookingGlass/info] Loaded applet notifications@cinnamon.org in 20 ms Cjs-Message: 08:32:19.907: JS LOG: [LookingGlass/info] Loaded applet xapp-status@cinnamon.org in 4 ms Cjs-Message: 08:32:19.933: JS LOG: [LookingGlass/info] Loaded applet recent@cinnamon.org in 26 ms Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)  Cjs-Message: 08:32:19.948: JS LOG: [LookingGlass/info] Loaded applet printers@cinnamon.org in 16 ms Cjs-Message: 08:32:19.958: JS LOG: [LookingGlass/info] Loaded applet workspace-switcher@cinnamon.org in 10 ms Cjs-Message: 08:32:19.978: JS LOG: [LookingGlass/info] Loaded applet user@cinnamon.org in 20 ms Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)  Cjs-Message: 08:32:20.005: JS LOG: [LookingGlass/info] Loaded applet power@cinnamon.org in 26 ms Cjs-Message: 08:32:20.026: JS LOG: [LookingGlass/info] Role locked: panellauncher Cjs-Message: 08:32:20.029: JS LOG: [LookingGlass/info] Loaded applet grouped-window-list@cinnamon.org in 24 ms  (csd-power:1405): power-plugin-CRITICAL **: 08:32:20.052: abs_to_percentage: assertion 'max > min' failed Cjs-Message: 08:32:20.086: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 58 ms Cjs-Message: 08:32:20.102: JS LOG: [LookingGlass/info] Loaded applet network@cinnamon.org in 16 ms Cjs-Message: 08:32:20.268: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 166 ms Cjs-Message: 08:32:20.269: JS LOG: [LookingGlass/info] AppletManager started in 490 ms Cjs-Message: 08:32:20.271: JS LOG: [LookingGlass/info] Cinnamon took 814 ms to start Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)  Cjs-Message: 08:32:20.297: JS LOG: Unknown network device type, is 14 Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)  Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)  dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-RnyPbj dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/dropbox' dropbox: setting python path '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383:/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)  Cjs-Message: 08:32:20.919: JS LOG: [LookingGlass/info] Hiding XAppStatusIcon (we have an applet): nm-applet dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/apex._apex.cpython-37m-x86_64-linux-gnu.so' ** Message: 08:32:21.164: nemo-desktop: session is cinnamon, establishing proxy dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/home/roby/.dropbox-dist/dropbox-lnx.x86_64-103.4.383/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so' Cjs-Message: 08:32:24.099: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: dropbox (org.x.StatusIcon.PID-1561-0) cinnamon-session[1275]: WARNING: t+11,75615s: Detected that screensaver has appeared on the bus Nemo-Share-Message: 08:32:29.273: Called "net usershare info" but it failed: «net usershare» ha restituito l'errore 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error File o directory non esistente Please ask your system administrator to enable user sharing.  Cjs-Message: 08:32:40.646: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: mintUpdate.py (org.x.StatusIcon.PID-1995-0) Cinnamon warning: Log level 128: posix_spawn avoided (automatic reaping requested) (fd close requested)                                  

I see a few warnings, but nothing that I could fix apparently (they are Cinnamon-related if I understand it right).

R

User avatar

smurphos
Level 17
Level 17
Posts: 7286
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Black screen and delay before logging into Cinnamon

Post by smurphos »

Thanks - it's still useful. It shows that the Desktop itself is loading quickly once it starts doing so and the delay is somewhere earlier.

Next this to do is examine the journal output. The command below will display the output for the current boot.

There will be a lot of output - the area of interest will be after something looking like the output below which corresponds to entering your password on the login screen and hitting enter.

Code: Select all

                  Aug 08 07:25:44 steve-Inspiron-5580 systemd[1]: Stopping Session c1 of user lightdm. Aug 08 07:25:44 steve-Inspiron-5580 systemd[1]: session-c1.scope: Succeeded. Aug 08 07:25:44 steve-Inspiron-5580 systemd[1]: Stopped Session c1 of user lightdm. Aug 08 07:25:44 steve-Inspiron-5580 systemd-logind[883]: Removed session c1. Aug 08 07:25:44 steve-Inspiron-5580 lightdm[1322]: pam_unix(lightdm:session): session opened for user steve by (uid=0)                                  

I can't really be specific on what to look for but big gaps in the timestamps will be of interest - there may some obvious error or timeout messages.

If you get as far as this line in the journal output...

Code: Select all

                  Aug 08 07:25:46 steve-Inspiron-5580 systemd[1396]: Started Virtual filesystem metadata service.                                  

...it pretty much coincides with the line in ~/.xsession-errors

Code: Select all

                  Cjs-Message: 07:25:46.506: JS LOG: About to start Cinnamon                

For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.

Rehdon
Level 3
Level 3
Posts: 172
Joined: Tue Nov 29, 2011 9:18 am

Re: Black screen and delay before logging into Cinnamon

Post by Rehdon »

Wow, you weren't kidding about the quantity of output! It took me a while to scroll all of it, but as you hinted I got a few places where things seem to stop for a while. The first bump (about 6 seconds) was soon after the login:

Code: Select all

                  ago 08 09:51:51 Wodan systemd[1054]: Starting Virtual filesystem service...  [...]  ago 08 09:51:52 Wodan systemd[1054]: Started Sound Service. ago 08 09:51:52 Wodan systemd[1054]: Reached target Main User Target. ago 08 09:51:52 Wodan systemd[1054]: Startup finished in 1.978s. ago 08 09:51:58 Wodan lightdm[1136]: pam_unix(lightdm:auth): Couldn't open /etc/securetty: No such file or directory ago 08 09:51:58 Wodan lightdm[1136]: gkr-pam: unable to locate daemon control file ago 08 09:51:58 Wodan lightdm[1136]: gkr-pam: stashed password to try later in open session ago 08 09:51:58 Wodan systemd[1]: Stopping Session c1 of user lightdm. ago 08 09:51:58 Wodan lightdm[1050]: pam_unix(lightdm-greeter:session): session closed for user lightdm ago 08 09:51:58 Wodan systemd[1]: session-c1.scope: Succeeded. ago 08 09:51:58 Wodan systemd[1]: Stopped Session c1 of user lightdm.                                  

Then smaller ones (about 2-4 seconds) follow up here:

Code: Select all

                  ago 08 09:51:59 Wodan systemd[1213]: Started Virtual filesystem service - Apple File Conduit monitor. ago 08 09:52:02 Wodan rtkit-daemon[1082]: Supervising 1 threads of 1 processes of 2 users. ago 08 09:52:02 Wodan rtkit-daemon[1082]: Successfully made thread 1514 of process 1245 owned by '1000' RT at priority 5. ago 08 09:52:02 Wodan rtkit-daemon[1082]: Supervising 2 threads of 1 processes of 2 users.  [...]  ago 08 09:52:02 Wodan systemd[1213]: Reached target Main User Target. ago 08 09:52:02 Wodan systemd[1213]: Startup finished in 4.295s. ago 08 09:52:04 Wodan dbus-daemon[1261]: [session uid=1000 pid=1261] Activating via systemd: service name='org.ayatana.bamf' unit='bamfdaemon.service' requested by ':1.51' (uid=1000 pid=1573 comm="plank " label="unconfined") ago 08 09:52:04 Wodan systemd[1213]: Starting BAMF Application Matcher Framework... ago 08 09:52:04 Wodan dbus-daemon[1261]: [session uid=1000 pid=1261] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.54' (uid=1000 pid=1570 comm="/usr/libexec/evolution-data-server/evolution-alarm" label="unconfined")  [...]  ago 08 09:52:04 Wodan systemd[1213]: Started Evolution address book service. ago 08 09:52:08 Wodan systemd[1]: Stopping User Manager for UID 120... ago 08 09:52:08 Wodan systemd[1054]: Stopped target Main User Target. ago 08 09:52:08 Wodan systemd[1054]: Stopping Accessibility services bus... ago 08 09:52:08 Wodan systemd[1054]: Stopping D-Bus User Message Bus... ago 08 09:52:08 Wodan systemd[1054]: Stopping Virtual filesystem service...                                  

After which you have a couple of really long pauses:

Code: Select all

                  ago 08 09:52:09 Wodan systemd[1]: Started Daemon for generating UUIDs. ago 08 09:52:09 Wodan cinnamon-session[1251]: WARNING: t+10,82063s: Detected that screensaver has appeared on the bus ago 08 09:52:17 Wodan dbus-daemon[772]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ago 08 09:52:17 Wodan pulseaudio[1245]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ago 08 09:52:17 Wodan systemd-timesyncd[748]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubuntu.com). ago 08 09:52:18 Wodan systemd[1]: systemd-hostnamed.service: Succeeded. ago 08 09:52:18 Wodan systemd[1]: systemd-fsckd.service: Succeeded. ago 08 09:52:42 Wodan dbus-daemon[1261]: [session uid=1000 pid=1261] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.52' (uid=1000 pid=1575 comm="nemo-desktop " label="unconfined") ago 08 09:52:42 Wodan systemd[1213]: Starting Virtual filesystem metadata service... ago 08 09:52:42 Wodan dbus-daemon[1261]: [session uid=1000 pid=1261] Successfully activated service 'org.gtk.vfs.Metadata' ago 08 09:52:42 Wodan systemd[1213]: Started Virtual filesystem metadata service.                                  

Hope this tells you something about how to fix it, I can see which services are slowing the desktop but no idea what's actually wrong.

Thanks a lot for your help!

R

Rehdon
Level 3
Level 3
Posts: 172
Joined: Tue Nov 29, 2011 9:18 am

Re: Black screen and delay before logging into Cinnamon

Post by Rehdon »

Ouch, I really hoped there were some hints in there. I'm afraid boot.log is not going to give you any major insights, unless the absence of [OK] is a valuable clue:

Code: Select all

                  [  OK  ] Finished Detect the availa… deal with any system changes. [  OK  ] Started WPA supplicant. [  OK  ] Started Thermal Daemon Service. [  OK  ] Started Avahi mDNS/DNS-SD Stack. [  OK  ] Started Make remote CUPS printers available locally.          Starting Manage, Install and Generate Color Profiles...          Stopping CUPS Scheduler... [  OK  ] Stopped CUPS Scheduler. [  OK  ] Started Authorization Manager.          Starting Modem Manager... [  OK  ] Started CUPS Scheduler. [  OK  ] Started Network Manager. [  OK  ] Reached target Network.          Starting OpenVPN service...          Starting Permit User Sessions... [  OK  ] Finished OpenVPN service. [  OK  ] Started Manage, Install and Generate Color Profiles. [  OK  ] Finished Permit User Sessions.          Starting Light Display Manager...          Starting Hold until boot process finishes up...          Starting Hostname Service... [  OK  ] Started Accounts Service. [  OK  ] Started Login Service. [  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.                                  

R

Rehdon
Level 3
Level 3
Posts: 172
Joined: Tue Nov 29, 2011 9:18 am

Re: Black screen and delay before logging into Cinnamon

Post by Rehdon »

Hi senjoz,
thanks for your reply. Sorry to answer just now but I have been away for holidays. This is what systemd-analyze critical-chain tells me:

Code: Select all

                  graphical.target @2.664s └─[b]udisks2.service @1.574s +1.089s[/b]   └─basic.target @1.537s     └─sockets.target @1.537s       └─uuidd.socket @1.537s         └─sysinit.target @1.533s           └─[b]systemd-timesyncd.service @1.461s +72ms[/b]             └─[b]systemd-tmpfiles-setup.service @1.436s +21ms[/b]               └─local-fs.target @1.431s                 └─[b]media-multimedia.mount @1.406s +24ms[/b]                   └─[b]systemd-fsck@dev-disk-by\x2duuid-3b4fdaba\x2d0540\x2d47c1\x2d9452\x2df910b0b4d469.service @819ms +585ms[/b]                     └─dev-disk-by\x2duuid-3b4fdaba\x2d0540\x2d47c1\x2d9452\x2df910b0b4d469.device @810ms                                  

The lines I marked with [ b ] are in red in the output, so perhaps there's something wrong there?

systemd-analyze blame, OTOH, doesn't show anything in red, here's the output:

Code: Select all

                  1.462s apt-daily-upgrade.service                                                                 1.089s udisks2.service                                                                            786ms man-db.service                                                                             585ms systemd-fsck@dev-disk-by\x2duuid-3b4fdaba\x2d0540\x2d47c1\x2d9452\x2df910b0b4d469.service  560ms dev-sda6.device                                                                            481ms systemd-fsck@dev-disk-by\x2duuid-09515bce\x2d6b9f\x2d478b\x2db53f\x2d45cd4aea6855.service  357ms systemd-fsck@dev-disk-by\x2duuid-e7674bd9\x2d34cd\x2d48c2\x2d8d6b\x2d9a302eadc912.service  353ms networkd-dispatcher.service                                                                281ms accounts-daemon.service                                                                    278ms systemd-fsck@dev-disk-by\x2duuid-ba266740\x2d7364\x2d44ae\x2da5d3\x2d6d535c0f8d5d.service  270ms systemd-logind.service                                                                     265ms e2scrub_reap.service                                                                       260ms ubuntu-system-adjustments.service                                                          231ms logrotate.service                                                                          165ms NetworkManager.service                                                                     165ms avahi-daemon.service                                                                       163ms polkit.service                                                                             154ms upower.service                                                                             153ms systemd-modules-load.service                                                               138ms plymouth-quit-wait.service                                                                 137ms lightdm.service                                                                            133ms thermald.service                                                                           132ms wpa_supplicant.service                                                                     130ms lvm2-monitor.service                                                                       123ms ModemManager.service                                                                       121ms networking.service                                                                         120ms systemd-resolved.service                                                                   114ms media-store.mount                                                                          113ms user@1000.service                                                                          104ms systemd-udev-trigger.service                                                               104ms gpu-manager.service                                                                        102ms keyboard-setup.service                                                                     101ms systemd-journald.service                                                                    94ms systemd-journal-flush.service                                                               90ms systemd-fsck@dev-disk-by\x2duuid-CC8D\x2dBEB1.service                                       83ms systemd-udevd.service                                                                       77ms grub-common.service                                                                         72ms systemd-timesyncd.service                                                                   69ms apparmor.service                                                                            68ms hddtemp.service                                                                             66ms secureboot-db.service                                                                       58ms colord.service                                                                              55ms alsa-restore.service                                                                        45ms lm-sensors.service                                                                          42ms grub-initrd-fallback.service                                                                42ms rsyslog.service                                                                             37ms systemd-tmpfiles-clean.service                                                              33ms media-progetti.mount                                                                        31ms dev-disk-by\x2duuid-3d57d866\x2d4a1e\x2d46d5\x2d8dd9\x2d8893c001d966.swap                   30ms media-home.mount                                                                            27ms dns-clean.service                                                                           27ms kerneloops.service                                                                          24ms media-multimedia.mount                                                                      23ms systemd-sysusers.service                                                                    21ms systemd-tmpfiles-setup.service                                                              21ms systemd-fsck@dev-disk-by\x2duuid-791c38ea\x2d216a\x2d443b\x2d8ed5\x2da374aa0d9590.service   21ms nvidia-persistenced.service   20ms modprobe@drm.service                                                                        19ms systemd-random-seed.service                                                                 18ms systemd-tmpfiles-setup-dev.service                                                          18ms pppd-dns.service                                                                            17ms systemd-sysctl.service                                                                      15ms systemd-update-utmp.service                                                                 13ms plymouth-start.service                                                                      13ms systemd-remount-fs.service                                                                  12ms dev-hugepages.mount                                                                         12ms dev-mqueue.mount                                                                            12ms plymouth-read-write.service                                                                 11ms sys-kernel-debug.mount                                                                      11ms systemd-update-utmp-runlevel.service                                                        11ms user-runtime-dir@1000.service                                                               10ms sys-kernel-tracing.mount                                                                    10ms console-setup.service                                                                       10ms blk-availability.service                                                                     9ms media-data.mount                                                                             8ms kmod-static-nodes.service                                                                    8ms boot-efi.mount                                                                               7ms systemd-user-sessions.service                                                                4ms ifupdown-pre.service                                                                         4ms ufw.service                                                                                  3ms rtkit-daemon.service                                                                         3ms setvtrgb.service                                                                             3ms finalrd.service                                                                              2ms sys-fs-fuse-connections.mount                                                                2ms sys-kernel-config.mount                                                                      2ms openvpn.service                                  

I must say that after applying the latest cinnamon updates the delay time has decreased to less than ten seconds, worse than before but I can live with that.

Thanks again for any help!

R

senjoz
Level 5
Level 5
Posts: 538
Joined: Tue Jun 09, 2020 3:55 am
Location: Kamnik

Re: Black screen and delay before logging into Cinnamon

Post by senjoz »

Rehdon wrote: ↑

Wed Aug 19, 2020 2:41 am

This is what systemd-analyze critical-chain tells me:

Code: Select all

                      graphical.target @2.664s └─[b]udisks2.service @1.574s +1.089s[/b]   └─basic.target @1.537s     └─sockets.target @1.537s       └─uuidd.socket @1.537s         └─sysinit.target @1.533s           └─[b]systemd-timesyncd.service @1.461s +72ms[/b]             └─[b]systemd-tmpfiles-setup.service @1.436s +21ms[/b]               └─local-fs.target @1.431s                 └─[b]media-multimedia.mount @1.406s +24ms[/b]                   └─[b]systemd-fsck@dev-disk-by\x2duuid-3b4fdaba\x2d0540\x2d47c1\x2d9452\x2df910b0b4d469.service @819ms +585ms[/b]                     └─dev-disk-by\x2duuid-3b4fdaba\x2d0540\x2d47c1\x2d9452\x2df910b0b4d469.device @810ms                                          

The lines I marked with [ b ] are in red in the output, so perhaps there's something wrong there?

systemd-analyze blame, OTOH, doesn't show anything in red, here's the output:

Code: Select all

                      1.462s apt-daily-upgrade.service                                                                 1.089s udisks2.service                                                                            786ms man-db.service                                                                             585ms systemd-fsck@dev-disk-by\x2duuid-3b4fdaba\x2d0540\x2d47c1\x2d9452\x2df910b0b4d469.service  560ms dev-sda6.device                                                                            481ms systemd-fsck@dev-disk-by\x2duuid-09515bce\x2d6b9f\x2d478b\x2db53f\x2d45cd4aea6855.service  357ms systemd-fsck@dev-disk-by\x2duuid-e7674bd9\x2d34cd\x2d48c2\x2d8d6b\x2d9a302eadc912.service  353ms networkd-dispatcher.service                                                                281ms accounts-daemon.service                                                                    278ms systemd-fsck@dev-disk-by\x2duuid-ba266740\x2d7364\x2d44ae\x2da5d3\x2d6d535c0f8d5d.service  270ms systemd-logind.service                                                                     265ms e2scrub_reap.service                                                                       260ms ubuntu-system-adjustments.service                                                          231ms logrotate.service                                                                          165ms NetworkManager.service                                                                     165ms avahi-daemon.service                                                                       163ms polkit.service                                                                             154ms upower.service                                                                             153ms systemd-modules-load.service                                                               138ms plymouth-quit-wait.service                                                                 137ms lightdm.service                                                                            133ms thermald.service                                                                           132ms wpa_supplicant.service                                                                     130ms lvm2-monitor.service                                                                       123ms ModemManager.service                                                                       121ms networking.service                                                                         120ms systemd-resolved.service                                                                   114ms media-store.mount                                                                          113ms user@1000.service                                                                          104ms systemd-udev-trigger.service                                                               104ms gpu-manager.service                                                                        102ms keyboard-setup.service                                                                     101ms systemd-journald.service                                                                    94ms systemd-journal-flush.service                                                               90ms systemd-fsck@dev-disk-by\x2duuid-CC8D\x2dBEB1.service                                       83ms systemd-udevd.service                                                                       77ms grub-common.service                                                                         72ms systemd-timesyncd.service                                                                   69ms apparmor.service                                                                            68ms hddtemp.service                                                                             66ms secureboot-db.service                                                                       58ms colord.service                                                                              55ms alsa-restore.service                                                                        45ms lm-sensors.service                                                                          42ms grub-initrd-fallback.service                                                                42ms rsyslog.service                                                                             37ms systemd-tmpfiles-clean.service                                                              33ms media-progetti.mount                                                                        31ms dev-disk-by\x2duuid-3d57d866\x2d4a1e\x2d46d5\x2d8dd9\x2d8893c001d966.swap                   30ms media-home.mount                                                                            27ms dns-clean.service                                                                           27ms kerneloops.service                                                                          24ms media-multimedia.mount                                                                      23ms systemd-sysusers.service                                                                    21ms systemd-tmpfiles-setup.service                                                              21ms systemd-fsck@dev-disk-by\x2duuid-791c38ea\x2d216a\x2d443b\x2d8ed5\x2da374aa0d9590.service   21ms nvidia-persistenced.service   20ms modprobe@drm.service                                                                        19ms systemd-random-seed.service                                                                 18ms systemd-tmpfiles-setup-dev.service                                                          18ms pppd-dns.service                                                                            17ms systemd-sysctl.service                                                                      15ms systemd-update-utmp.service                                                                 13ms plymouth-start.service                                                                      13ms systemd-remount-fs.service                                                                  12ms dev-hugepages.mount                                                                         12ms dev-mqueue.mount                                                                            12ms plymouth-read-write.service                                                                 11ms sys-kernel-debug.mount                                                                      11ms systemd-update-utmp-runlevel.service                                                        11ms user-runtime-dir@1000.service                                                               10ms sys-kernel-tracing.mount                                                                    10ms console-setup.service                                                                       10ms blk-availability.service                                                                     9ms media-data.mount                                                                             8ms kmod-static-nodes.service                                                                    8ms boot-efi.mount                                                                               7ms systemd-user-sessions.service                                                                4ms ifupdown-pre.service                                                                         4ms ufw.service                                                                                  3ms rtkit-daemon.service                                                                         3ms setvtrgb.service                                                                             3ms finalrd.service                                                                              2ms sys-fs-fuse-connections.mount                                                                2ms sys-kernel-config.mount                                                                      2ms openvpn.service                                          

No significant delays in both outputs. Lines in red indicate that the unit took some time to start (after the "+" character). Those start times look normal. I have nofurter ideas.

Regards,
Jože