Sign in takes more than a couple of minutes

General system Newbie
1

After an update (not sure which one, it’s been a while, over a year), I noticed that when I sign back in after the screen locked or the PC went to sleep, the screen will kind of “freeze” on the sign in background. Moving the mouse or typing something will wake the screen up, but it takes a while for the password “window” to show up, or if I just start typing my password (correctly) right away, it’ll take a while for the screen to unlock and go in my desktop. I don’t have any issues once signed back in, always just at the sign-in process, the issue would “hang” for maybe a dozen seconds more than usual. Now that I recently added a second monitor, It’s worse. The “hang” will last more than a couple minute, and I often have to type in my password a couple of times, move and click my mouse for something to happen, if I don’t, the screens shuts off.

How can I make this process better, going back to a fast and smooth sign-in?

I’m on KDE with a Nvidia 1070 and a Ryzen with a dGPU.

Here’s the latest inxi output after a BIOS update and yay update:

  Kernel: 6.14.4-arch1-2 arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: ProArt B550-CREATOR v: Rev X.0x serial: <filter>
    part-nu: SKU UEFI: American Megatrends v: 3802 date: 01/14/2025
Memory:
  System RAM: total: 32 GiB available: 31.13 GiB used: 14.52 GiB (46.6%)
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: no module installed
  Device-2: DIMM_A2 type: DDR4 size: 16 GiB speed: 2666 MT/s volts: 1.2
    manufacturer: G Skill Intl part-no: F4-3200C16-16GVK
  Device-3: DIMM_B1 type: no module installed
  Device-4: DIMM_B2 type: DDR4 size: 16 GiB speed: 2666 MT/s volts: 1.2
    manufacturer: G Skill Intl part-no: F4-3200C16-16GVK
CPU:
  Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 2393 min/max: 400/4673 boost: enabled cores: 1: 2393
    2: 2393 3: 2393 4: 2393 5: 2393 6: 2393 7: 2393 8: 2393 9: 2393 10: 2393
    11: 2393 12: 2393 13: 2393 14: 2393 15: 2393 16: 2393 bogomips: 121374
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nvidia
    v: 570.144 arch: Pascal pcie: speed: 8 GT/s lanes: 16 ports: active: none
    off: DP-1,HDMI-A-1 empty: DVI-D-1,DVI-D-2 bus-ID: 01:00.0
    chip-ID: 10de:1b81
  Display: unspecified server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3640x1920 s-dpi: 101
  Monitor-1: DP-1 mapped: DP-0 note: disabled pos: right model: VP229
    res: 1920x1080 hz: 60 dpi: 102 diag: 546mm (21.5")
  Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: primary,left
    model: Gigabyte M32QC res: 2560x1440 hz: 60 dpi: 93 diag: 800mm (31.5")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 1 drv: nouveau
    device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11:
    drv: nvidia inactive: wayland
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.144
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
  API: Vulkan v: 1.4.309 surfaces: xcb,xlib device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:1b81
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Drives:
  Local Storage: total: 931.51 GiB used: 746.64 GiB (80.2%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
    size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 44.9 C
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 43.0 C gpu: nvidia temp: 59 C
  Fan Speeds (rpm): cpu: 881 gpu: nvidia fan: 28%
2

This won’t solve your issue directly, but have you checked if booting from a current LIVE iso displays the same problem?
If not, this would probably mean it’s your configuration that’s causing you issues.

3

Hmm, good suggestion, I’ll have to try that. In the case it’s the config, how could I change it for the better?

4

Well the quick and dirty would probably be remove your config, but you could also try creating a new userid and see if it’s plagued with the same issue.

5

Interesting suggestion, I’ll have to try that as well.

6

Well, did it help pinpoint any issues?

7

Ok So I have the same issue with a new userid. I havent yet tried the liveUSB yet, I have to dl the new version.

8

Well, that rules out the easiest thing to check…it’s not just your personal settings.

9

Yeah. Other than the liveUSB, any other things I can try?

10

Well you could try a non-KDE and non-SDDM (assuming that’s your setup) environment. Basically just try different things :0 Wayland and X11 too.
You can also try to figure out where the time may be getting consumed with systemd-analyze and systemd-analyze blame.

11

Yeah ok, more work to figure out things… I’ve been wondering if I should reinstall EOS, is there a way to do that and not lose all the programs and settings?

12

Hah, nothing worth having comes without work. You learn by fixing your problem(s).
And yeah, probably not, since the chances are good that something you did caused your problem, so trying to keep those settings, would likely continue the problem.
The only other indication would be booting off that live ISO and determining if you still have the issue there (in an unsullied? configuration)

13

So, In a live ISO, works as normal. Definitely a problem with my current config…

14

IS the SDDM login screen just for login or also for sign-in?

15

To me those words mean the same thing ;0

16

The reason why I ask, When Logging in from booting/rebooting the PC, I have a normal login speed. It’s when the PC locks (due to inactivity or when I lock it) and the screen goes dark, then you have to sign back in, that’s where it’s slow. the reason why I differentiate the two is because the login screen is different to the sign-in screen. Is that normal?

17

There is in many desktops the notion of a lockscreen vs a login screen. I believe KDE also has that notion.
If you’re saying that you only experience this on the lockscreen, then you can disable that on your existing install (though that doesn’t mean it’s fixed/correct, just that you are avoiding it…some people do that to just prevent screen lock anyway) :slight_smile:

18

And yet in the settings, I can only change the login screen, typing lockscreen in the search yield nothing that allows modification other than choosing when screen locks and delay before password required as options

19

I’m currently in HyprLand, so I can’t check, but I believe it’s under power savings along with sleep/hibernate options.

20

I only have power management, and there’s only only Suspend session. Display and brightness and Other settings which is for power profile. in the advanced tab, it’s just battery levels for peripherals and pause media when suspending…

I’ll try LighDM, found the setting to change it in the EOS Welcome program