SDDM login loop in Plasma 6

Hello,

After recently updating my system, I am not able to login into my system. After placing correct password it keeps on coming back to the main login screen. I am using plasma 6 and right now am on X11 session

inxi -F
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_ADDRESS = "en_US.UTF-8",
	LC_NAME = "en_US.UTF-8",
	LC_MONETARY = "ne_NP.UTF-8",
	LC_PAPER = "ne_NP.UTF-8",
	LC_IDENTIFICATION = "en_US.UTF-8",
	LC_TELEPHONE = "ne_NP.UTF-8",
	LC_MEASUREMENT = "ne_NP.UTF-8",
	LC_TIME = "en_US.UTF-8",
	LC_NUMERIC = "en_US.UTF-8",
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
System:
  Host: superadmin Kernel: 6.6.30-1-lts arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.0.4 Distro: EndeavourOS
Machine:
  Type: Laptop System: LENOVO v: Lenovo Yoga
    serial: <superuser required>
  Mobo: LENOVO model: 
    serial: <superuser required> UEFI: LENOVO v: FSCN14WW date: 08/26/2020
Battery:
  ID-1: BAT0 charge: 32.5 Wh (60.1%) condition: 54.1/60.0 Wh (90.2%)
    volts: 15.8 min: 15.4
CPU:
  Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1492 min/max: 1400/2900 cores: 1: 1400 2: 2900 3: 1400
    4: 1400 5: 1400 6: 1397 7: 1397 8: 1400 9: 1397 10: 1397 11: 1400 12: 1400
    13: 1400 14: 1400 15: 1400 16: 1397
Graphics:
  Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] driver: nvidia
    v: 550.78
  Device-2: AMD Renoir [Radeon RX Vega 6 ] driver: amdgpu v: kernel
  Device-3: IMC Networks Integrated Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6 driver: X:
    loaded: amdgpu,nvidia unloaded: modesetting dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~144Hz
  API: EGL v: 1.5 drivers: nvidia,radeonsi,swrast
    platforms: x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 24.0.6-arch1.2
    renderer: AMD Radeon Graphics (radeonsi renoir LLVM 17.0.6 DRM 3.54
    6.6.30-1-lts)
  API: Vulkan v: 1.3.279 drivers: nvidia surfaces: xcb,xlib
Audio:
  Device-1: NVIDIA TU116 High Definition Audio driver: snd_hda_intel
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  API: ALSA v: k6.6.30-1-lts status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: eno1 state: down mac: 8c:8c:aa:27:6b:06
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
  IF: wlan0 state: up mac: a4:b1:c1:a9:a8:d5
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 rfk-id: 4 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: A4:B1:C1:A9:A8:D9 bt-v: 5.2
Drives:
  Local Storage: total: 1.38 TiB used: 160.59 GiB (11.4%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P3SSD8 size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: SK Hynix model: HFS512GD9TNI-L2A0B
    size: 476.94 GiB
Partition:
  ID-1: / size: 195.8 GiB used: 50.51 GiB (25.8%) fs: ext4 dev: /dev/dm-1
  ID-2: /boot/efi size: 511 MiB used: 27.2 MiB (5.3%) fs: vfat
    dev: /dev/nvme0n1p2
  ID-3: /home size: 702.71 GiB used: 110.05 GiB (15.7%) fs: ext4
    dev: /dev/dm-2
Swap:
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) dev: /dev/dm-0
Sensors:
  System Temperatures: cpu: 51.2 C mobo: N/A gpu: amdgpu temp: 37.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15 GiB used: 4.08 GiB (27.2%)
  Processes: 371 Uptime: 3h 51m Shell: Bash inxi: 3.3.34

You can’t load into Wayland? but x11 works?

Yep !! I am able to login into X11 session but not in Wayland session !!
After placing the password the Wayland comes back to SDDM screen again !!

Have you tried sddm-git?

I think I used to have this problem back when I testing plasma 6 in the beta phase and ended up having to delete the screen configuration directory. Not sure what would cause it at this stage though.