Fedora 42 Cinnamon : long startup / automatic login

Ask Fedora
1

Hello everyone,

I’m a bit new to Linux and installed Fedora 42 Cinnamon on Wednesday. Everything seems to be going well except for 2-3 small things :slight_smile:

I find that starting the PC takes a little time, more than 20 seconds. I’m on a Geekom IT13, 13th generation core i9, 32GB of RAM, 1TB NVMe hard drive.
doing a systemd-analyze , it’s the NeworkManager-wait.online-service that takes more than 8 seconds. I tried to disable it but
1/ it doesn’t change much
2/ I’m struggling to connect to the internet once the PC has started.
On this subject, I should point out that I’m sharing the connection with my iPhone. When NetworkManager is active (and I reactivated it), the connection is much easier.

Another point, how can we make the login automatic? Currently I have to enter my username and password bscore the session starts. I went to the user account and entered my username in the automatic login, but once the PC is started I have to enter the password before doing any other thing.

Sorry for the long message and thank you very much in advance for your help!

2

This is needed to unlock the gnome-keyring, it’s there for security.

Gnome Keyring is a password management system that’s part of the GNOME desktop environment in Linux. It protects several types of sensitive information:

  1. Passwords for applications and websites
  2. Network authentication credentials (like WiFi passwords)
  3. SSH keys and passphrases
  4. PGP keys and passphrases
  5. Secret encryption keys
  6. Security certificates

The main purpose of Gnome Keyring is to securely store these sensitive credentials in an encrypted format, so you don’t have to repeatedly enter passwords for applications that need them. Once you unlock your keyring (typically done when you log into your system), applications can access the stored credentials without requiring you to re-enter passwords.

Gnome Keyring uses encryption to protect the stored data, and the master password (usually your login password) is used to decrypt the keyring when it’s unlocked. This creates a more convenient and secure experience, as sensitive credentials aren’t stored in plaintext in configuration files.

3

20+ seconds to reach graphics target is a reasonable time.

Both machines are using NVME

nvidia driver

$ cat ~/.xsession-errors |grep 'Cinnamon took'
Cjs-Message: 20:35:33.364: JS LOG: [LookingGlass/info] Cinnamon took 410 ms to start

$ inxi -Cm
Memory:
  System RAM: total: 64 GiB available: 62.65 GiB used: 3.08 GiB (4.9%)
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
  Device-1: DIMM_A1 type: DDR4 size: 16 GiB speed: 2666 MT/s
  Device-2: DIMM_A2 type: DDR4 size: 16 GiB speed: 2666 MT/s
  Device-3: DIMM_B1 type: DDR4 size: 16 GiB speed: 2666 MT/s
  Device-4: DIMM_B2 type: DDR4 size: 16 GiB speed: 2666 MT/s
CPU:
  Info: 8-core model: AMD Ryzen 7 5700 bits: 64 type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 3000 min/max: 421/4654 cores: 1: 3000 2: 3000 3: 3000
    4: 3000 5: 3000 6: 3000 7: 3000 8: 3000 9: 3000 10: 3000 11: 3000 12: 3000
    13: 3000 14: 3000 15: 3000 16: 3000
$ systemd-analyze
Startup finished in 8.665s (firmware) + 6.121s (loader) + 2.415s (kernel) + 1.345s (initrd) + 4.281s (userspace) = 22.829s 
graphical.target reached after 4.242s in userspace.

amdgpu driver

$ cat ~/.xsession-errors |grep 'Cinnamon took'
Cjs-Message: 08:45:46.776: JS LOG: [LookingGlass/info] Cinnamon took 1112 ms to start

$ inxi -Cm
Memory:
  System RAM: total: 32 GiB available: 27.31 GiB used: 6.42 GiB (23.5%)
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
  Device-1: Channel-A DIMM 0 type: DDR4 size: 16 GiB speed: 3200 MT/s
  Device-2: Channel-B DIMM 0 type: DDR4 size: 16 GiB speed: 3200 MT/s
CPU:
  Info: quad core model: AMD Ryzen 3 4300U with Radeon Graphics bits: 64
    type: MCP cache: L2: 2 MiB
  Speed (MHz): avg: 1397 min/max: 1400/2700 cores: 1: 1397 2: 1397 3: 1397
    4: 1397
$ systemd-analyze 
Startup finished in 7.946s (firmware) + 5.445s (loader) + 1.239s (kernel) + 5.956s (initrd) + 3.670s (userspace) = 24.256s 
graphical.target reached after 3.481s in userspace.
4

You can use systemd-analyze time too see an overview of where the time is going.
For my desktop it spends more time in the UEFI BIOS then it does booting to KDE login.

5

Your comment doesn’t add anything useful

leigh@leigh-pc:~$ systemd-analyze time
Startup finished in 8.665s (firmware) + 6.121s (loader) + 2.415s (kernel) + 1.345s (initrd) + 4.281s (userspace) = 22.829s 
graphical.target reached after 4.242s in userspace.
leigh@leigh-pc:~$ systemd-analyze
Startup finished in 8.665s (firmware) + 6.121s (loader) + 2.415s (kernel) + 1.345s (initrd) + 4.281s (userspace) = 22.829s 
graphical.target reached after 4.242s in userspace.
leigh@leigh-pc:~$