(Very) long delay after logging in

[LittleStone]

Hello,

first of all. This is my first time trying to install/use linux. So be patient.

I erased the driver of my 2010 macbook pro.

I downloaded the Manjaro 250-5-manjaro (manjaro-gnome-21.2.1-220103-linux515) and checked, that it was not corrupted and flashed it from an SD Card.

I managed to install Manjaro but already had an issue: It took about estimated 20 minutes to half an hour until the dock in the liveOS and the installation menu appeared.

After I managed to install Manjaro the system boots in normal time but when i log in it takes a similar time for the dock to appear.

Furthermore the system sometimes wakes up after it went to sleep because of inactivity but most times not. Also most times it doesn’t find Wifi.

I would really appreciate to be able to fix this issues but am already thinking about trying another gnu/linuxOS…

So thanks for your help!

[CyberOto]

Hey,

You could try running in console systemd-analyze blame and systemd-analyze blame --user, which shows which services are taking the longest to start up.

That might give some ideas what is happening and possible further steps.

Example how mine looks like

systemd-analyze blame
1.797s systemd-random-seed.service
 949ms systemd-modules-load.service
 661ms ufw.service
 565ms dev-loop3.device
 563ms dev-loop2.device
 556ms dev-loop1.device
 552ms dev-loop0.device
 534ms systemd-swap.service
 441ms dev-sdb2.device
 336ms cups.service
 316ms snapd.service
 230ms polkit.service
 200ms systemd-tmpfiles-clean.service
 187ms user@120.service
 168ms systemd-udevd.service
 155ms ModemManager.service
 135ms NetworkManager.service
 131ms smb.service
 129ms systemd-logind.service
 125ms user@1000.service
 123ms upower.service
 122ms udisks2.service
  95ms lvm2-monitor.service
  91ms systemd-sysctl.service
  80ms systemd-journal-flush.service
  66ms lm_sensors.service
  66ms systemd-udev-trigger.service
  63ms boot-efi.mount
  56ms media-myssd_ntfs.mount
  50ms accounts-daemon.service
  42ms systemd-tmpfiles-setup.service
  42ms home.mount
  40ms media-myssd.mount
  39ms systemd-fsck@dev-disk-by\x2duuid-c49dcd3e\x2d18a1\x2d4086\x2d88c2\x2d89671dcfdf93.service
  38ms systemd-timesyncd.service
  32ms colord.service
  31ms gdm.service
  31ms systemd-journald.service
  29ms var-lib-snapd-snap-core-11993.mount
  24ms systemd-tmpfiles-setup-dev.service
  23ms var-lib-snapd-snap-core-12603.mount
  21ms systemd-fsck@dev-disk-by\x2duuid-07AD\x2dCDAD.service
  21ms modprobe@fuse.service
  20ms wpa_supplicant.service
  20ms var-lib-snapd-snap-snapd-14295.mount
  17ms var-lib-snapd-snap-snapd-14549.mount
  15ms power-profiles-daemon.service
  13ms tmp.mount
  11ms dev-hugepages.mount
  11ms sys-kernel-config.mount
  10ms dev-mqueue.mount
  10ms systemd-binfmt.service
  10ms sys-kernel-debug.mount
   9ms sys-kernel-tracing.mount
   8ms alsa-restore.service
   8ms kmod-static-nodes.service
   7ms user-runtime-dir@120.service
   7ms systemd-user-sessions.service
   6ms systemd-remount-fs.service
   6ms modprobe@configfs.service
   6ms modprobe@drm.service
   6ms linux-module-cleanup.service
   5ms user-runtime-dir@1000.service
   4ms systemd-update-utmp.service
   4ms proc-sys-fs-binfmt_misc.mount
   2ms rtkit-daemon.service
   2ms sys-fs-fuse-connections.mount
 329us snapd.socket

systemd-analyze blame --user
1.527s xdg-desktop-portal.service
1.233s org.gnome.Shell@x11.service
 720ms xdg-desktop-portal-gtk.service
 483ms pulseaudio.service
 370ms tracker-miner-fs-3.service
 341ms xdg-desktop-portal-gnome.service
 326ms org.gnome.SettingsDaemon.XSettings.service
 170ms gvfs-udisks2-volume-monitor.service
 104ms evolution-source-registry.service
  95ms evolution-calendar-factory.service
  94ms gnome-terminal-server.service
  89ms org.gnome.SettingsDaemon.MediaKeys.service
  85ms org.gnome.SettingsDaemon.Color.service
  83ms org.gnome.SettingsDaemon.Keyboard.service
  82ms org.gnome.SettingsDaemon.Power.service
  82ms org.gnome.SettingsDaemon.Wacom.service
  68ms gnome-session-manager@gnome.service
  32ms org.gnome.SettingsDaemon.PrintNotifications.service
  31ms evolution-addressbook-factory.service
  30ms org.gnome.SettingsDaemon.Datetime.service
  25ms org.gnome.SettingsDaemon.Housekeeping.service
  24ms org.gnome.SettingsDaemon.ScreensaverProxy.service
  24ms org.gnome.SettingsDaemon.Sound.service
  22ms org.gnome.SettingsDaemon.Sharing.service
  20ms org.gnome.SettingsDaemon.UsbProtection.service
  19ms org.gnome.SettingsDaemon.Rfkill.service
  16ms org.gnome.SettingsDaemon.Smartcard.service
  14ms org.gnome.SettingsDaemon.A11ySettings.service
  11ms gnome-session-signal-init.service
  10ms gvfs-daemon.service
   9ms gvfs-mtp-volume-monitor.service
   9ms flatpak-session-helper.service
   7ms xdg-document-portal.service
   7ms org.gnome.Shell@wayland.service
   6ms gvfs-goa-volume-monitor.service
   5ms gvfs-afc-volume-monitor.service
   5ms at-spi-dbus-bus.service
   4ms gvfs-metadata.service
   3ms dbus.socket
   3ms gnome-session-monitor.service
   3ms dconf.service

[andreas85]

Please also search for threads taged with macbook

How to increase your chances of solving your issue:

[HowTo] Request support

Difficulty: ★☆☆☆☆ Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to follow three major points. Provide context Simply signaling an issue is rarely enough to understand how it occurred. It is thus important to provide details on how it happened: Detail prior actions leading to the issue. List solutions and guides you already tried, with links when…

Please provide Information:

[HowTo] Provide System Information

This tutorial is superseded by this one. Remember all Tutorials are wiki posts that can be edited by TL2 (Trust Level 2) members and above. Welcome to Manjaro! To allow all of us helpful people on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly. Someone else probably linked you to…

[LittleStone]

Thank you for your help!

    ~  systemd-analyze blame                                            ✔ 
30.995s plymouth-quit-wait.service
12.611s snapd.service
 9.222s dev-mapper-luks\x2d1b2ce4cc\x2d18ac\x2d4109\x2dac6f\x2dcafb21ea0de5.dev>
 8.867s polkit.service
 4.372s bluetooth.service
 4.362s NetworkManager.service
 4.339s systemd-logind.service
 4.089s cups.service
 4.072s ModemManager.service
 3.092s udisks2.service
 2.943s apparmor.service
 2.702s accounts-daemon.service
 2.256s systemd-udevd.service
 2.007s systemd-journal-flush.service
 1.683s systemd-vconsole-setup.service
 1.527s systemd-sysusers.service
 1.335s gdm.service
 1.266s systemd-fsck@dev-disk-by\x2duuid-9DFD\x2dCA64.service
 1.263s ldconfig.service
 1.027s wpa_supplicant.service
  865ms systemd-random-seed.service
  732ms systemd-modules-load.service
  688ms systemd-tmpfiles-setup.service

systemd-analyze blame --user                                     ✔ 
10.585s org.gnome.Shell@x11.service
 3.973s gvfs-udisks2-volume-monitor.service
 2.897s evolution-source-registry.service
 2.345s gvfs-goa-volume-monitor.service
 2.159s evolution-calendar-factory.service
 1.802s org.gnome.SettingsDaemon.XSettings.service
 1.401s pulseaudio.service
 1.050s org.gnome.SettingsDaemon.Power.service
 1.009s org.gnome.SettingsDaemon.MediaKeys.service
  873ms org.gnome.SettingsDaemon.Wacom.service
  733ms evolution-addressbook-factory.service
  626ms org.gnome.SettingsDaemon.Color.service
  496ms org.gnome.SettingsDaemon.Datetime.service
  474ms org.gnome.SettingsDaemon.Keyboard.service
  339ms gnome-terminal-server.service
  283ms org.gnome.SettingsDaemon.A11ySettings.service
  258ms gnome-session-signal-init.service
  251ms org.gnome.SettingsDaemon.Housekeeping.service
  245ms gnome-session-manager@gnome.service
  208ms org.gnome.SettingsDaemon.Rfkill.service
  208ms org.gnome.SettingsDaemon.Sound.service
  194ms org.gnome.SettingsDaemon.PrintNotifications.service
  194ms org.gnome.SettingsDaemon.Smartcard.service

[Wollie]

@LittleStone

9.222s dev-mapper-luks\x2d1b2ce4cc\x2d18ac\x2d4109\x2dac6f\x2dcafb21ea0de5.dev>

Have you encrypted the disk or partitions? Decryption could take quite a while.

More helpful would be output of

systemd-analyze critical-chain

[LittleStone]

Yes, i encrypted the disk.

systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target at52.881s
└─multi-user.target at52.881s
  └─plymouth-quit-wait.service at21.084s +31.796s
    └─systemd-user-sessions.service at20.973s +101ms
      └─nss-user-lookup.target at23.785s

Sorry. I had to replace @ with “at” because I’m only allowed to mention two users.

[Yochanan]

Welcome to the forum!

Tip: When pasting terminal output on Discourse forums, one can either…

• Use the Preformatted text </> toolbar button.

• Add three backticks ` above and below the text (Markdown):

  ```
  type or paste code here
  ```

• Use HTML:

  <pre><code>
  type or paste code here
  </pre></code>

I’ve done it for you this time.

In the future, please edit your previous post rather than posting multiple times in a row. This is a support forum, not an instant messenger.

[anon89812132]

@LittleStone

30.995s plymouth-quit-wait.service

I would remove plymouth and also remove the entry from /etc/mkinitcpio.conf and then run
sudo mkinitcpio -P
sudo update-grub

You can also
systemctl mask ModemManager.service

[LittleStone]

Thank you! I renmoved Plymouth with

systemctl disable plymouth….service

Nothing changed.

But how can I remove it from the file? Sorry I’m a real noob. I opened the file but there is nothing to find so I guess I have to do this per commands in terminal?!