SDDM doesnt work with Hyprland

ShibamRoy · 2024-08-02 05:59:15

Hello everyone!
I have been using arch for around a month now, and i love it.
Just day before yesterday, I planned to reinstall arch, just to clear up some mess. Everything was working fine. This time, i thought of using a TUI based display manager, and I used Ly. I use both i3 and Hyprland, and both seems to work well with Ly.
But, for some reason, SDDM doesn't seem to work with Hyprland , It works with i3 though. When i try to login with Hyprland, SDDM get's stuck for like 5 secs and then I see a black screen for a few more seconds, and i get back to the login screen.
If i try to run Hyprland directly in the tty mode, it works.
I checked the sddm logs at '/var/log/sddm.log' and this is what i found:

 
[19:27:41.651] (II) HELPER: Jumping to VT 3
[19:27:41.651] (II) HELPER: VT mode didn't need to be fixed
[19:27:54.454] (II) HELPER: Jumping to VT 3
[19:27:54.454] (II) HELPER: VT mode didn't need to be fixed
[19:57:37.436] (II) HELPER: Jumping to VT 3
[19:57:37.437] (II) HELPER: VT mode didn't need to be fixed
[22:06:06.514] (II) HELPER: Jumping to VT 3
[22:06:06.514] (II) HELPER: VT mode didn't need to be fixed
[00:05:17.507] (II) HELPER: Jumping to VT 3
[00:05:17.508] (II) HELPER: VT mode didn't need to be fixed
[09:58:07.573] (II) HELPER: Jumping to VT 5
[09:58:07.576] (II) HELPER: VT mode didn't need to be fixed
[09:58:19.178] (II) HELPER: Jumping to VT 5
[09:58:19.179] (II) HELPER: VT mode didn't need to be fixed
[09:58:30.076] (II) HELPER: Jumping to VT 5
[09:58:30.076] (II) HELPER: VT mode didn't need to be fixed
[09:58:40.505] (II) HELPER: Jumping to VT 5
[09:58:40.505] (II) HELPER: VT mode didn't need to be fixed
[10:21:15.698] (II) HELPER: Jumping to VT 5
[10:21:15.698] (II) HELPER: VT mode didn't need to be fixed
[10:29:06.135] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[10:29:06.209] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[10:29:06.286] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[10:29:06.394] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[10:29:06.472] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[10:29:06.569] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[10:36:30.819] (II) HELPER: Jumping to VT 5
[10:36:30.819] (II) HELPER: VT mode didn't need to be fixed
[10:42:26.795] (II) HELPER: Jumping to VT 7
[10:42:26.796] (II) HELPER: VT mode didn't need to be fixed
[10:51:41.972] (II) HELPER: Jumping to VT 7
[10:51:41.972] (II) HELPER: VT mode didn't need to be fixed

What i have tried:

Tried using SDDM display protocol to wayland, which resulted in a broken SDDM which doesnt even startup. (used the '/usr/lib/sddm/sddm.conf.d/default.conf' file)
Tried to follow the Nvidia page of Hyprland https://wiki.hyprland.org/Nvidia/
Tried disabling my SDDM theme, which didn't cause any changes in the problem

Device specifications and other info:
Kernel: Linux 6.10.2-zen1-1-zen
CPU: Intel(R) Core(TM) i5-6200U (4) @ 2.80 GHz
GPU 1: Intel HD Graphics 520 @ 1.00 GHz [Integrated]
GPU 2: NVIDIA GeForce 940M [Discrete]

I apologize if its a dumb question, I am still a learner, Thanks for any help:)

hypnotics · 2024-08-03 22:51:02

Did you create a config file that can be loaded? My issue was an invalid symlink stopping hyprland from reading or creating the conf file and crashing.
If not can you post the latest hyprland crash report found at ~/.cache/hyprland/?

BluePyTheDeer_ · 2024-08-05 17:12:01

I know this won't help, but it might be something with your system, because I use SDDM for Hyprland, works perfectly.

ShibamRoy · 2024-08-06 17:48:10

Sorry for a late reply,

Did you create a config file that can be loaded?

Yes, I did create a config file for hyprland, infact it works fine with Ly ( a TUI based Login manager),
Seems like my issue got fixed automatically after a few days, I installed many things in the mean time so i am not sure what exactly fixed it...
But, there's another problem now, I still cant use SDDM, for some reason it always logs me in as root, although the default is my current username.
All I have changed is the theme, I changed "/etc/sddm.conf", and this is what I added(Infact i dont think the file was there before)

[Theme]
Current=catppuccin

I know this won't help, but it might be something with your system, because I use SDDM for Hyprland, works perfectly.

It just doesnt work with SDDM, but works with any other display manager... Seems like i do have some problem with my config, but I dont know what, or even where,
I tried looking at all the locations for my config file ( sddm.conf ) , but wasnt able to find it.

Lone_Wolf · 2024-08-07 09:53:44

GPU 1: Intel HD Graphics 520 @ 1.00 GHz [Integrated]
GPU 2: NVIDIA GeForce 940M [Discrete]

Looks like hybrid graphics which often require specific low level config.

Please post the contents of your /etc/mkinitcpio.conf.

As root run

# journalctl -b | curl -F 'file=@-' 0x0.st

It will upload your journal to a public hosting site and output a link. Post that link.

ShibamRoy · 2024-08-08 12:46:59

Here's my /etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"

Here's the link that came from the command:
link

Lone_Wolf · 2024-08-09 10:30:28

There are some things that look wrong, but I'm not sure yet what happens.

Please post the full output of

$ lspci -knn
$ ls -l /etc/modprobe.d/ /etc/modules-load.d/
$ pacman -Qs nvidia

ShibamRoy · 2024-08-10 18:24:00

Output of lspci -knn

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
	Subsystem: Lenovo Device [17aa:504d]
	Kernel driver in use: i915
	Kernel modules: i915
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
	Subsystem: Lenovo Device [17aa:504c]
00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: intel_ish_ipc
	Kernel modules: intel_ish_ipc
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #4 [8086:9d13] (rev f1)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1e.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 [8086:9d27] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d48] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_soc_skl, snd_soc_avs
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-V [8086:1570] (rev 21)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
02:00.0 SD Host controller [0805]: O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01)
	Subsystem: Lenovo Device [17aa:504c]
	Kernel driver in use: sdhci-pci
	Kernel modules: sdhci_pci
03:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
	Subsystem: Intel Corporation Device [8086:1130]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
06:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 940M] [10de:1347] (rev a2)
	Subsystem: Lenovo Device [17aa:504d]
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia

Output of ls -l /etc/modprobe.d/ /etc/modules-load.d/

Permissions Size User Date Modified Name
.rw-r--r--    38 root  1 Aug 02:06   dsp.conf
.rw-r--r--    35 root  1 Aug 02:11   snd-hda-intel-fix.conf

/etc/modules-load.d/:
Permissions Size User Date Modified Name
.rw-r--r--     5 root  3 Jul 18:39   gnutls.conf

Output of pacman -Qs nvidia

local/egl-wayland 3:1.1.13.1-1
    EGLStream-based Wayland external platform
local/libvdpau 1.5-3
    Nvidia VDPAU library
local/nvidia-dkms 555.58.02-1
    NVIDIA drivers - module sources
local/nvidia-utils 555.58.02-1
    NVIDIA drivers utilities

Actually, I was having some trouble with shutdown too, my arch randomly didnt shut down, turns out it was SDDM. Now that i have stopped using it, I dont see the problem at all.
I really am curious to know what's actually causing this issue...

Lone_Wolf · 2024-08-11 14:19:31

Possibly the simpledrm device messed up things, see https://wiki.archlinux.org/title/NVIDIA … de_setting

Try adding nvidia_drm.modeset=1 as kernel paramter (putting it in a modprobe.d file is not enough) .

BluePyTheDeer_ · 2024-08-12 01:18:42

Kinda weird, apparently, according to the Hyprland Wiki, it works the other way around (ly being worse to launch Hyprland than SDDM), getting really confused by this.

Last edited by BluePyTheDeer_ (2024-08-12 01:20:04)

Arch Linux

#1 2024-08-02 05:59:15

SDDM doesnt work with Hyprland

#2 2024-08-03 22:51:02

Re: SDDM doesnt work with Hyprland

#3 2024-08-05 17:12:01

Re: SDDM doesnt work with Hyprland

#4 2024-08-06 17:48:10

Re: SDDM doesnt work with Hyprland

#5 2024-08-07 09:53:44

Re: SDDM doesnt work with Hyprland

#6 2024-08-08 12:46:59

Re: SDDM doesnt work with Hyprland

#7 2024-08-09 10:30:28

Re: SDDM doesnt work with Hyprland

#8 2024-08-10 18:24:00

Re: SDDM doesnt work with Hyprland

#9 2024-08-11 14:19:31

Re: SDDM doesnt work with Hyprland

#10 2024-08-12 01:18:42

Re: SDDM doesnt work with Hyprland

Board footer