I run latest OpenSUSE tumbleweed, KDE only. I wish to switch the default session from Plasma X11 to Plasma wayland. What should I do to achieve this? The login manager I use comes from sddm. And I can indeed manually log in from the login manager to a wayland session.

The default Breeze theme for SDDM on KDE uses default fonts from somewhere I don't know of. In earlier versions of KDE/SDDM, there used to be specific files in the SDDM themes where a font could be set (using something like font.family in PlasmaComponents.Label). However, in newer versions (Plasma/sddm-breeze 5.10.1-1, sddm 0.14.0-10 on Fedora 26) everything seems to have been rearranged and I can't find any file(s) where the font can clearly/obviously be set. I would like to change the font for preferably _all_ UI elements. I found this post but couldn't glean much useful information from it. One option in particular, got by following a link in that post, is to just change the system's default (fallback) fonts , and that is something I _definitely_ don't want to do (I need the default fonts as they are for other reasons). I also tried the option mentioned in the original post, by the author of an SDDM theme, of setting the font in the theme.conf file , but to no avail. (To be fair, the author does mention that this technique won't work with other themes. :( ) Is there really a way to change the SDDM font, particularly for the Breeze theme?

I have installed Debian 10 on my laptop Dell Inspiron . But when booting first time into Debian, It directs me into the command-line interface, why? I am sure, I have chosen Graphical Install during installation. Is it related to the graphics of my laptop? My laptop has **AMD Radeon R2** graphics and I am using the SDDM Display manager. It has **AMD APU Dual Core E1** processor. I have installed **KDE plasma**, **LxDM**, and **Lxqt** in the select and install software step during installation. I have chosen SDDM as my Display manager between **lightdm** and **sddm**.

The day I attempted to remove the Hyprland desktop (that successfully showed the graphics) I tried to install with https://github.com/JaKooLit/Debian-Hyprland (I did not like it, keybindings are funky) and then reinstalled KDE Plasma 6 on Debian Sid, the display manager would never do anything and would remain in the TTY. Executing /usr/bin/sddm manually does not do anything nor startplasma-wayland. startx is the only command that works, running from the TTY, but it is not the Wayland session and many features such as brightness do not work. The display manager says to have started while booting, and nothing fails. I have tried reinstalling sddm (purging old config files), installing task-xfce-desktop and lightdm over task-kde-desktop and sddm, and reinstalling task-kde-desktop and its dependencies. How can I start the display manager again on boot? I am using Debian Sid (unstable), KDE Plasma version 6.3.5. CPU: 12 × 13th Gen Intel® Core™ i7-1355U GPU: Raptor Lake-P [Iris Xe Graphics] Kernel version: 6.15-rt-amd64 (64-bit)

I keep finding sources talking about changing the DM and DE using /etc/sysconfig/desktop but when I write this in the file, nothing changes: DESKTOP="GNOME" DISPLAYMANAGER="SDDM" I have already installed sddm.

Two days ago I did a system update with sudo pacman -Syyu Unfortunately, my battery was empty and my laptop turned off during the System update. When I tried to start Arch Linux again, I was stuck on the grub Bootloader with the following message: ` Error: file /vmlinux-linux-lts not found. Error: you need to load the kernel first Press a key to continue` According to https://bbs.archlinux.org/viewtopic.php?id=238904 , I have to reinstall linux again so I did the following: 1. Installed an Arch Linux iso on a USB-stick 2. Checked my partitions with fdisk -l 3. Mounted my root partition with mount /dev/sda1 /mnt (I don`t have a boot partiton) 4. Installed mkinitcpio, linux. linux-lts and systemd with sudo pacman -S linux linux-lts mkinitcpio systemd 5. Typed exit and rebooted. As you can see, I forgot to umount my root partiton. When I rebooted the system, I could finally boot into arch without the error messages but I run into the next problem. I was stuck at the boot screen with the message:

Starting Version 244.3-1-arch
/dev/sda1: recovering Journal
/dev/sda1: clean, 712088/5898240 files, 15789063/23592960 blocks

After a while, I switched to tty2 by pressing Ctrl+strg+F2. I did some research on the Internet and I found a solution how to escape from this: On the grub menu, I selected Arch Linux and pressed e. In the line

linux /boot/vmlinuz-linux-lts root=UUID=168b8466-66a9-4da7-bld4-07f5e95d1c73 rw loglevel=3 quiet

I removed quiet and booted into arch. Now I am stuck at Reached target Graphical Interface. For any reason, sddm does not want to start. If I switch to tty2, I always get prompted into a zsh shell. I tried everything, from removing ./Xauthority to reinstalling the xorg package. Nothing worked. Additional Information: Laptop name: HP625 processor: AMD Athlon II P320 GPU: ATI Radeon HD 4250 dual-boot system (Arch Linux alongside with Kali Linux) Related links: https://unix.stackexchange.com/questions/330999/arch-linux-stuck-at-boot-reached-target-graphical-interface https://bbs.archlinux.org/viewtopic.php?id=228814 https://wiki.archlinux.org/index.php/Xorg https://wiki.archlinux.org/index.php/SDDM https://wiki.archlinux.org/index.php/LightDM https://github.com/sddm/sddm/issues/352

On debian version 12.8 fully upgraded, sddm window manager.
Using either gsetting or dconf-editor, I can set and verify org.gnome.desktop.wm.preferences focus-mode to either sloppy or mouse but neither takes effect: still have to click in window to raise focus.
gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy gsettings get org.gnome.desktop.wm.preferences focus-mode 'sloppy'

When using a particular Thunderbolt dock, I wake my machine from sleep and sometimes I can't log in. I see the normal login screen, I can move the cursor and type my password, but hitting Enter or clicking the submit button does nothing. It doesn't tell me my password was wrong or even look like it's trying to authenticate. The UI remains interactive but does not perform its function. The issue is like this one , but I'm not on Arch. The login screen ‘goes to sleep’ after a very short period, and seems to struggle to resume after moving the cursor or pressing a key. I'd rather not restart SDDM because that wipes out the current session, losing my place and any unsaved work.

I'm using CachyOS, which is a Linux-based system, specifically from the Arch Linux family. I have KDE Plasma 6.1.5 and SDDM version 0.21.0 (Wayland) and I would like to add seconds to the login screen and lock screen, but I don't know how to do it and I couldn't find a working solution online. Does anyone know how to do it?

For practicality reasons, I leave a detachable headphone cable permanently plugged into the back of my motherboard. My monitor also has speakers though, which I use during the day when I won't disturb anyone who is sleeping by listening to music. In order to be able to quickly switch the audio output / switch between the audio sinks for my monitor, and for my headphones. I have written a quick shell script that detects the current sink, defines the monitor sink and headphone sink as variables, and then switches between them according to what sink was already active. It works well enough but there are a couple of issues with the script related to my yearning for simpler times... I have set Windows XP's startup and shutdown sounds to run when I login, and when I shutdown my PC. The problem is though, if I shut down the PC late at night and I want to hear the startup sound the next day when I login, I have to switch the audio sink before powering off. Which means the shutdown sound plays through my monitor's speakers late at night. So I've been looking for a way of having the audio sink set before I log in, according to what time it is. I've already tried putting the following code in my /usr/share/sddm/scripts/Xsetup but it doesn't work for some reason. # Define the two audio outputs HEADPHONES="alsa_output.pci-0000_12_00.3.HiFi__hw_Generic__sink" #this is the "Line out" headphone output. MONITOR="alsa_output.pci-0000_0c_00.1.hdmi-stereo" #this is the displayport connection to the monitor. # Decide on the new sink based on the time if [[ "$current_time" -ge "09:00:00" && "$current_time" -le "23:00:00" ]]; then new_sink="$MONITOR" else new_sink="$HEADPHONES" fi # Set the new default sink pactl set-default-sink "$new_sink"# Is automatically running a script after I login or when I power off my PC an option?

I wanted to try Arch and as I have an M1 Mac, I need to use the ARM version of arch or otherwise my Arch is slow as fuk because it's emulated. I'm using UTM as my virtual machine (for those who don't know, UTM is just a nice GUI frontend for managing QEMU machines, so I'm technically running Arch in QEMU). I'm using the pre-configured installation from the UTM gallery: https://mac.getutm.app/gallery/archlinux-arm I wanted to try installing a desktop environment, so I started with installing SDDM (I'm not sure if it already comes with a desktop environment, but I'm happy if I just have a login screen). Basically I just updated Pacman and then installed SDDM. Then I enabled the SDDM service. Then I had to add a display to my VM, because the installation from the UTM gallery does not have a display output by default, but just a serial interface window to interact with Arch. So in the settings of my VM, I added a display and the display card virtio-ramfb was selected by default, so I kept it like this. When I'm now launching my VM, I have one window for the display and one for the serial interface. While you can see the system booting in the serial window, the graphical window just displays 4 Tuxes in a row for some time, and then just has a black screen, while the serial window is just showing a normal terminal login like before. So, I checked systemctl status sddm to see if it's actually running, and the output said that it was active and showed the last logs from this service: Aug 14 19:42:17 alarm sddm: Failed to read display number from pipe Aug 14 19:42:17 alarm sddm: Display server stopping... Aug 14 19:42:17 alarm sddm: Attempt 2 starting the Display server on vt 2 > Aug 14 19:42:19 alarm sddm: Display server starting... Aug 14 19:42:19 alarm sddm: Writing cookie to "/run/sddm/xauth_DguHSX" Aug 14 19:42:19 alarm sddm: Running: /usr/bin/X -nolisten tcp -background > Aug 14 19:42:19 alarm sddm: Failed to read display number from pipe Aug 14 19:42:19 alarm sddm: Display server stopping... Aug 14 19:42:19 alarm sddm: Attempt 3 starting the Display server on vt 2 > Aug 14 19:42:19 alarm sddm: Could not start Display server on vt 2 I don't know where to find the full logs, but I think the important error message shows up here anyway: Failed to read display number from pipe **What I tried to fix this:** I searched for this error, and I found the suggestion to install the drivers required for my display. This would be virtio-gpu for the display card selected in UTM, but pacman doesn't find any packages named virtio-gpu or virtio. I also read a few times that I'd have to re-generate the initramfs or whatever, I'd have to run mkinitcpio -P. But this command always fails with this error message: gzip: stdout: No space left on device bsdtar: Write error bsdtar: Write error ==> ERROR: Initcpio image generation FAILED: 'bsdtar (step 1)' reported an error Somehow gzip complains about not having space left on device, but increasing the size of the RAM as well as the hard drive in the VM settings didn't worked, so I'm not sure if it's really because of having no space left. Restarting the SDDM service manually also didn't work. I tried it with systemctl restart sddm as well as stopping and then starting it, and I also ran systemctl disable sddm and started it manually after rebooting, but still just black screen. But when starting the system with the SDDM service disabled, I found that the display window now shows the usual Arch terminal, so Arch at least somehow detected the display and is able to print something to the screen. So I guess I might need to something for SDDM or so... Do you know where this error comes from? (And do you also know why my initcpio generation fails?) Thank you! :D

I have installed KDE in the /opt prefix and when I try to use different themes in SDDM like breeze or Sweet-Mars I always get the error saying that the main module “org.kde.plasma.extras” and module “org.kde.plasma components” are NOT installed. Could anyone please give a solution.

I'd like to be able to log in as the superuser via SDDM without having to manually enter its username. I'd consequently like to have it appear amongst users (created via KDE Plasma 6's kcm_users).

I thought it was enough to Log Out then in the upper left of the lockscreen clicking the dropdown to change it from "Plasma (X11)" to "Plasma (Wayland)" would be enough but apparently it isn't. I checked if I was using Wayland with loginctl show-session 1 -p Type (replace "1" with your session number shown by running loginctl) after a reboot and it showed X11.

My fingerprint sensor works fine, in fact it works quite well except when it comes to SDDM. I use fprintd and systemd.

I have looked online for solutions, one involved changing some code in a systemd service, the only problem is I use NixOS. (for those who don't know, NixOS makes most of the root folder read only for the purpose of making everything editable from one file). I don't know how to change an existing service inside of NixOS.

to replicate my situation I have a fresh install of NixOS plasma5 from Here . I then moved to the unstable channel and upgraded my system to plasma6 with this guid . and lastly I enabled fprintd. for my sensor I didn't need to specify any drivers but your experience may vary.

Does anyone know how to fix this? and if not, does anyone know how to edit or append to an already existing systemd service inside of NixOS? also, if possible, I would like to only use the config file. you should probably also know I have no experience using flakes or the nix-env command.

any help would be appreciated, thank you.

I have the problem where sddm won't let me login to my box, it just throws me back to the password entry screen. When I change to a shell with Ctrl-Alt-F2 and login, it tells me user change directory failed permission denied with a reference to home dir /home/user but my home dir has the correct owner and 755 permissions. I can get to Plasma fine when I type startx from the cli. What might be going on, here? This on my Fedora38 box. I have not tried another WM as I don't have another one installed and I'm using X11.

 I’m using _simple desktop display manager (SDDM)_ & _KDE Plasma 5_. How do I configure the avatar picture of a _non-root_ user, **through commands** (so that I can automate it)? How do I do the above in a terminal? I can’t even find the configuration file, .ini, .conf, *rc, be it whatever. I have done kfind throughout the whole system and found nothing but the locations of those icon image files, which are of no use.

Radeon card on computer may is defect after current problems. How to check? sddm not start, card detected but no vram My raddeon sapphire has 3 fans. These fans were only turning when had gpu loads to do. Otherwise, in reboot they were still. However, now all three fans working continously. Display says null display. Sddm is stuch on logind message. My terminal "font" is the basic (large letters) and not the "high-end" font of a graphic card (small letters), as previously. By the local current problems in Greece (due to fires and heat), i dont know if my graphic card has problem or not. I cant find any util to test its "integrity". I have gpu utils. It is detected by system as radeon but what else i can do to see if it can work or it is for trash? - Sddm says is starting but no display in tty7. - gpu-chk utils says all green and some oranges - most test utils must open a display to test graphic card UPDATE 1: I changed from sddm to lightdm display manager. However monitor started to low resolution (1080x -75hz). It appears that i cannot change it UPDATE 2: radeonontop when using glmark2 and glxgear is all values "0". It appears that GPU is off. VRAM is not detected by radeonontop it appears that only some very basic display things is working from radeon card :( See my whole dmesg (nothing of value) here my /etc/modules contains only AMDPowerProfiler SOLUTION led by Artem S. Tashkinov running sudo modprobe amdgpu but it was not permanent i found out that for some reason, amdgpu was blacklisted in my system at etc/modprobe.d/blacklist-amdgpu.conf. I dont know neither the reason nor the process that led to that. However, after commenting the line, it was fixed. Thanks.

I have Fedora KDE 37 installed on my laptop. I use NoMachine to connect to the laptop remotely from my Windows 10 desktop, so I typically leave the lid closed. I was able to configure my normal desktop session to do nothing when the lid is closed while on external power. However, if I have to reboot the laptop, I am no longer able to connect to the laptop after it boots up again because it has gone to sleep. Is it possible to configure the power management settings of SDDM so that it never goes to sleep while on external power? I tried using

to open up a shell as the

user and use the

command to alter the power management settings, but I got an error message stating that the power management service wasn't available.

I am running Parrot OS (Debian) with KDE as the default desktop environment and SDDM as the display manager. I want to run Openbox and MATE desktop environments parallel to KDE on different virtual terminals. However, when I switch back to KDE after running Openbox or MATE on a different virtual terminal, the KDE desktop freezes and shows the last frame from Openbox or MATE or a black screen. I started Openbox on TTY3 using the command startx /usr/bin/openbox -- :1 and MATE on TTY2 using startx /usr/bin/mate-session -- :2. Both sessions work fine, but the KDE session on TTY7 freezes when I switch back to it. If I set Mate as the default desktop environment. And start another Mate or Openbox on a different virtual terminal. And switch between them, the Mate started by SDDM also freezes, the others are working fine. If I use LightDM instead of SDDM I get the same problem. How can I fix this issue and switch between the different desktop environments seamlessly without freezing the desktop environment session on TTY7 (started by the desktop manager)?