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**.

I recently installed **Debian 13 RC (trixie)** on VMWare using the net install image and during the installation I opted out the desktop environment. After the installation, I installed the gdm3 packages and rebooted to a black screen with a blinking underscore. For comparison, I repeated the exact same process on **Debian 12 (bookworm)** and was able to boot into the graphical interface without any problem. I'm using VMware Workstation 17 Pro, so I'm not sure if this is nvidia GPU related. I was wondering what would be the root cause of this issue. PS: I do notice that the dependencies for gdm3 packages for trixie and bookworm are slighly different.

I have a Debian 12 VM that and when I boot it remotely the user session is a TTY, can I have it launch an X11 session at the console end? ### Attempt A ### - KDE is installed - I have selected plasma-x11 as my default session manager - I have changed the default display manager to sddm

loginctl
SESSION  UID USER   SEAT TTY  
      3 1000 user1      pts/0

1 sessions listed.

loginctl show-session 3 -p Type                                   
Type=tty

update-alternatives --config x-session-manager             
There are 3 choices for the alternative x-session-manager (providing /usr/bin/x-session-manager).

  Selection    Path                      Priority   Status
------------------------------------------------------------
  0            /usr/bin/startxfce4        50        auto mode
* 1            /usr/bin/startplasma-x11   40        manual mode
  2            /usr/bin/startxfce4        50        manual mode
  3            /usr/bin/xfce4-session     40        manual mode

Press  to keep the current choice[*], or type selection number: 1

cat /etc/X11/default-display-manager
/usr/sbin/sddm

ls /usr/share/xsessions
lightdm-xsession.desktop  plasma.desktop  xfce.desktop

but my user keeps login into a TTY session. How can I solve it? ### Attempt B ### - I have tried starting the display-manager.service

systemctl start display-manager.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to start 'lightdm.service'.
Authenticating as: root
Password: 
==== AUTHENTICATION COMPLETE ====

loginctl show-session 22 -p Type
Type=tty

but it started lightdm instead of sddm even though I set x-session-manager to /usr/bin/startplasma-x11, and the session is still type=tty. ### Attempt C ### - I have manually started sddm - I have tried startx, startplasma-x11 and startkde, but to no avail.

systemctl start sddm.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to start 'sddm.service'.
Authenticating as: root
Password: 
==== AUTHENTICATION COMPLETE ====

startx
/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
^Cxinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: unexpected signal 2
Couldn't get a file descriptor referring to the console.

startkde
zsh: command not found: startkde

startplasma-x11
$DISPLAY is not set or cannot connect to the X server.

As a result, an x11 session has been started for the sddm user instead of changing my user's session to X11.

loginctl
SESSION  UID USER   SEAT  TTY  
     22 1000 user1       pts/0
     24  111 sddm   seat0 

2 sessions listed.

When I have a regular X11 session, it's my user's session, not the session for the display manager user. ### Attempt D ### - I have tried startX with root privileges and detaching it, so it doesn't block the terminal.

doas startx &
 2446
  + suspended (tty output)  doas startx

but it doesn't work.

I have Debian, Sid if it matters, and I'd like to start X from the console, rather than using a display manager, but when i type startx I receive the following message xinit: connection to X server lost If I'm logged as root, or if I use sudo, I'm able to start X so I suspect that permissions are at the root of the problem . What should I do to enable generic users to start X, possibly via startx ? I'm interested both in a simple solution, achieved probably manipulating permissions, that has other drawbacks and in a possibly more complicated solution, maybe a proxy like a sort of _non-graphical display manager_, or whatever else…

I have the following lines in /etc/X11/xinit/xinputrc to tame my mouse sensitivity: xinput --set-prop 9 "Device Accel Constant Deceleration" 4.5 xinput --set-prop 9 "Device Accel Velocity Scaling" 1 xinput --set-prop 9 "Device Accel Adaptive Deceleration" 1.5 These work great, the mouse behaves as I want. However, these commands only get run after a user logs in - on the login screen the mouse has the default sensitivities and is almost unusable. How do I get xinput commands to run that effect the login screen? Running LinuxMint 17.1, standard display manager (mdm).

On ubuntu 22.04, I want to login remotely to it using RDP after boot up, the machine is not connected any display. RDP is not started and Wayland (Gnome session) is not unlocked without physical interaction of user with keyboard and mouse. Although Autologin is successful, gnome session is locked with keyring on ubuntu 22.04. When I try to unlock manually by connecting with HDMI display, the RDP password is randomly changed. Needs. 1. Bypass the keyring prompt to unlock automatically. 2. Must not be randomly changed RDP login password. How to solve it. Thanks.

I'm creating a display manager (dm) in python, which waits to Xorg to start in order to run the GUI. ### Python (omitted unnecessary code like widgets and classes and functions)

import os

(more imports of PyQt6 etc ...)
.......

class LoginWindow( QMainWindow ):
    def __init__(self):
        super().__init__()
                
        # Make window full screen
        self.setWindowFlags(Qt.WindowType.FramelessWindowHint  | 
                            Qt.WindowType.WindowStaysOnTopHint
                            )

   ..........
   .......... (unnecessary code to the problem)
        
    def cancel(self, window):
        if not window :
             ...

def start_x11():
    xorg =subprocess.run("Xorg :0 -nolisten tcp -background none -logfile /var/log/mydm/xorg.log vt1",shell=True)
    return xorg

def start_user_session(username) :
    loginctl = subprocess.run(f"loginctl enable-linger {username}",shell=True)# ,capture_output=True)
    #print(loginctl)
    if loginctl.returncode == 0 :
        subprocess.run(f"sudo -u {username} dbus-launch startxfce4",shell=True)

if __name__ == "__main__" :
    
    if start_x11().returncode == 0 : 
        app = QApplication(sys.argv)
        app.setStyleSheet('''
            QPushButton#loginDockButton { 
                border: none;    
                padding: 0px;
                margin: 0px;
            }
        ''')


        window = LoginWindow()
        window.show()

        sys.exit(app.exec())

As you can see, i'm using **subprocess.run()** in order to run **Xorg**. And when asked to an **AI** to resolve the problem,i was recommended to run : subprocess.run("loginctl enable-linger {username}",shell=True) According to that **AI**, it let the users child processes to run even if logged out, this in order to prevent closing **dbus** process. **(though still wonder how this can help 🤔)** ### Unit Service

[Unit]
Description=mydm
Conflicts=getty@tty1.service
After=systemd-user-sessions.service plymouth-quit.service
Requires=systemd-logind.service

[Service]
ExecStart=/usr/bin/python3 /etc/mydm/src/mydm_login.py
Restart=always
RestartSec=3
StandardOutput=syslog
StandardError=syslog
TTYPath=/dev/tty1
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes

[Install]
WantedBy=graphical.target

I have to admit that the unit service code, was all generated by an **AI** because i didn't have any idea how unit files work and neither **systemd** or **systemctl** ### Logfile After some minutes of sadness and grief from not seeing my GUI, i decided to look at into the **logfile** from **Xorg** and got the next :

[  3671.154] Current Operating System: Linux MrDikxon 6.13.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:55 +0000 x86_64
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

grep EE /var/log/mydm/xorg.log
[  3671.154] (EE) systemd-logind: failed to get session: PID 4060 does not belong to any known session
[  3671.171] (EE) Failed to load module "fbdev" (module does not exist, 0)
[  3671.172] (EE) Failed to load module "vesa" (module does not exist, 0)
[  3671.186] (EE) open /dev/dri/card0: No such file or directory
[  3671.191] (II) Initializing extension MIT-SCREEN-SAVER
[  3671.193] (EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
[  3671.193] (EE) AIGLX error: unable to load driver i965

grep WW /var/log/mydm/xorg.log 

[  3671.154] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  3671.154] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[  3671.154] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  3671.154] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  3671.154] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[  3671.154] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[  3671.169] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  3671.171] (WW) Warning, couldn't open module fbdev
[  3671.172] (WW) Warning, couldn't open module vesa
[  3671.186] (WW) Falling back to old probe method for modesetting

When doing it when (NI,??) didn't get any output. this is my first time working with Xorg or sysmted, so i dont know really what can i do. So i havent tried anything yet, and unix & linux stackexchange threads doesn't seem to relate much to what i need

I would like to run a Wayland based comp (KDE Plasma) and an X11 based one (Mate+Xmonad) on the same system. The scenario could be something like having user A with KDE and user B with Mate. A third user C might want xfce and so forth. If I understand it correctly, a greeter / display manager such as lightdm runs on X11, so does this pose a problem in switching users? Note: A and B might be the same system user, but wanting to work with a different comp.

I'm currently on Ubuntu, using a virtual machine, and am trying to use ly as my display manager.Whenever I try to run

systemctl ly.service

inside of the ly directory on my computer, I get an error. Would anyone know how to disable gdm3, which is the default display manager for Ubuntu?

I have the following setup (HP Microserver 8): - Integrated Matrox G200eH connected to Integrated Lights Out (the PH Remote Management Console) which also simulates an integrated keyboard to the system - Dedicated NVidia Quadro P400 GPU which is intended to be used for X applications via VNC/remove X-sessions When originally setting this up with all devices on seat0, I noticed that the integrated GPU didn't show the TTY anymore as the dedicated GPU has taken over the master (and the keyboard can now used within the Display Session) I'm now trying to set up a separate seat1 which only includes the dedicated GPU, while seat0 will control the integrated GPU + keyboard via TTY. Unfortunately I haven't managed with any display manager to limit startup of the display manager and X to seat1, so seat0 can still be used for remote administration via CLI. I tried both lightdm as well as gdm3 with no success (you can't exclude seats in either), and I couldn't find a way to use TTY as a greeter either. Is this something I can do by removing the master-of-seat tag via udev from the matrox card?

The current setup of my displays is as follows: I would like the 2nd Sony display to be a mirror of 3rd Dell display, while the 1st Samsung display should remain as separate secondary display. When I try to change 2nd Sony display into Mirror mode, the button Apply is grayed out: Is there a way to make it the way I want it to be?

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

Is there a simple linux command that will tell me what my display manager is? I'm using Xfce. Are different desktop environments usually affiliated with different display managers?

My problem is, that my Debian installation shows a grey screen on start up and boots into a console, instead into gnome. When I start X manually with startx everything starts fine, so the DE seems to be functioning.

There is a shadow around each window in Mate. If it matters I run Lightdm. How can the shadows be completely disabled for all windows regardless of the application?

At some point (I don't remember when it started), some kind of ghost window appeared that only has a border (displays as rounded but behaves as rectangular), blocks mouse clicks, and won't disappear when I minimize all windows. What might this be, what might have caused this, and most importantly, how might I be able to get rid of this? Here is some additional information that might help diagnose the issue: - This does not seem to affect the lock screen. - The behavior with the Alt-Tab window switcher is very strange when I click on a window: - If the I click outside the ghost window, it immediately switches to the window I clicked on. - If the I click inside the ghost window, it immediately closes the window switcher, but doesn't open the new window until I move my mouse outside the ghost window. The final position of my mouse doesn't seem to matter. - I'm using Xfce version 4.18 with GTK version 3.24.37, as part of Debian GNU/Linux 12 (bookworm). - I have xserver-xorg version 1:7.7+23 and xserver-xorg-core version 2:21.1.7-3. - The panel at the top of my screen doesn't respond to mouse clicks, but the data it displays does update, and the apps menu works when I activate it with a keyboard shortcut. - Here is the output of xwininfo -d :0 -all after clicking on the ghost window:

xwininfo: Window id: 0x1b75612 "xfce4-panel"

  Root window id: 0x6d1 (the root window) (has no name)
  Parent window id: 0x6d1 (the root window) (has no name)
     1 child:
     0x1b75613 (has no name): ()  1x1+-1+-1  +2926+461

  Absolute upper-left X:  2927
  Absolute upper-left Y:  462
  Relative upper-left X:  2927
  Relative upper-left Y:  462
  Width: 328
  Height: 637
  Depth: 32
  Visual: 0x6ba
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x1a00002 (not installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: yes
  Map State: IsViewable
  Override Redirect State: yes
  Corners:  +2927+462  -585+462  -585-341  +2927-341
  -geometry 328x637+2927+462

  Bit gravity: NorthWestGravity
  Window gravity: NorthWestGravity
  Backing-store hint: NotUseful
  Backing-planes to be preserved: 0xffffffff
  Backing pixel: 0
  Save-unders: Yes

  Someone wants these events:
      KeyPress
      KeyRelease
      ButtonPress
      ButtonRelease
      EnterWindow
      LeaveWindow
      PointerMotion
      ButtonMotion
      Exposure
      VisibilityChange
      StructureNotify
      FocusChange
      PropertyChange
  Do not propagate these events:
  Override redirection?: Yes

  Window manager hints:
      Client accepts input or input focus: Yes
      Initial state is Normal State
      Window type:
          Popup Menu
      Process id: 2661 on host 

  Normal window size hints:
      Program supplied minimum size: 328 by 637
      Program supplied maximum size: 328 by 637
      Program supplied base size: 0 by 0
      Program supplied window gravity: NorthWestGravity
  No zoom window size hints defined

  No window shape defined
  No border shape defined

- Here is the output of xwininfo -d :0 -all after clicking on the panel at the top of the screen:

xwininfo: Window id: 0x1a00003 "xfce4-panel"

  Root window id: 0x6d1 (the root window) (has no name)
  Parent window id: 0x1200587 (has no name)
     4 children:
     0x1a0000e (has no name): ()  90x50+1190+0  +3750+416
        1 child:
        0x2800003 "wrapper-2.0": ("wrapper-2.0" "Wrapper-2.0")  90x50+0+0  +3750+416
           1 child:
           0x2800004 (has no name): ()  1x1+-1+-1  +3749+415
     0x1a0000d (has no name): ()  69x50+1121+0  +3681+416
        1 child:
        0x2600003 "wrapper-2.0": ("wrapper-2.0" "Wrapper-2.0")  69x50+0+0  +3681+416
           4 children:
           0x2600029 (has no name): ()  22x22+24+1  +3705+417
              1 child:
              0x1c00003 "xfce4-power-manager": ("xfce4-power-manager" "Xfce4-power-manager")  22x22+0+0  +3705+417
                 1 child:
                 0x1c00004 (has no name): ()  1x1+-1+-1  +3704+416
           0x2600019 (has no name): ()  22x22+0+26  +3681+442
              1 child:
              0x3000003 "Ethernet network connection “Wired connection 1” active": ("nm-applet" "Nm-applet")  22x22+0+0  +3681+442
                 1 child:
                 0x3000004 (has no name): ()  1x1+-1+-1  +3680+441
           0x260000a (has no name): ()  22x22+0+1  +3681+417
              1 child:
              0xc00010 "IBus Panel": ("ibus-ui-gtk" "ibus-ui-gtk")  22x22+0+0  +3681+417
                 1 child:
                 0xc00011 (has no name): ()  1x1+-1+-1  +3680+416
           0x2600004 (has no name): ()  1x1+-1+-1  +3680+415
     0x1a0000c (has no name): ()  254x50+695+0  +3255+416
        1 child:
        0x2400003 "wrapper-2.0": ("wrapper-2.0" "Wrapper-2.0")  254x50+0+0  +3255+416
           1 child:
           0x2400004 (has no name): ()  1x1+-1+-1  +3254+415
     0x1a00004 (has no name): ()  1x1+-1+-1  +2559+415

  Absolute upper-left X:  2560
  Absolute upper-left Y:  416
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 1280
  Height: 51
  Depth: 32
  Visual: 0x6ba
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x1a00002 (not installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +2560+416  -0+416  -0-973  +2560-973
  -geometry 1280x51-0+416

  Bit gravity: NorthWestGravity
  Window gravity: NorthWestGravity
  Backing-store hint: NotUseful
  Backing-planes to be preserved: 0xffffffff
  Backing pixel: 0
  Save-unders: No

  Someone wants these events:
      KeyPress
      KeyRelease
      ButtonPress
      ButtonRelease
      EnterWindow
      LeaveWindow
      PointerMotion
      ButtonMotion
      Exposure
      VisibilityChange
      StructureNotify
      FocusChange
      PropertyChange
  Do not propagate these events:
  Override redirection?: No

  Window manager hints:
      Client accepts input or input focus: Yes
      Initial state is Normal State
      Displayed on all desktops
      Window type:
          Dock
      Window state:
          Sticky
          Skip Pager
          Skip Taskbar
          Focused
      Process id: 2661 on host 
      Frame extents: 0, 0, 0, 0

  Normal window size hints:
      Program supplied minimum size: 1280 by 51
      Program supplied maximum size: 1280 by 51
      Program supplied base size: 0 by 0
      Program supplied window gravity: StaticGravity
  No zoom window size hints defined

  No window shape defined
  No border shape defined

Here are some screenshots to illustrate how it behaves as I change display settings. It's not really visible in the thumbnails; click on them to see the full-size versions.

I've been looking at Display Managers like SDDM, GDM and LightDM, but it doesn't seem as if they support a non-interactive login. I want to issue a command to have it login to one of the users, without requiring the user to enter a password on the GUI. One usecase is logging in my son or my daughter on their computer, when I myself am logged in via SSH. Another usecase is logging myself in, when I am close to a computer, for example with bluetooth proximity. I need to use a command like dm_login username Another option is to launch an Xorg server with xinit on another tty, but I think it will be much cleaner having a scriptable Display Manager. EDIT: I'm on NixOS, but I could use any distro to solve this problem. EDIT2: I know all of them supports auto-login, but there are multiple users on the system.

I am looking for a display manager that works with multiple displays and multiple scaling. I am running Linux Mint on a laptop with a 4k screen. I also have a 1440p portable monitor and a 1440p ultra-wide desktop monitor. While I can connect these displays together if I use different scaling on the different monitors (as you want when you have a big 1440p display paired to a small 4k display) it tends to break badly, with a variety of issues occurring. Therefore I am looking for a different display manager which is capable of handling two or more displays with different scaling on each display.

I installed Fedora 38 via the Network Installer (also called Everything) and there was no desktop environment preinstalled so I installed plasma-desktop package which is labelled as **Plasma Desktop shell **. However, I have no idea what to do next to start the desktop environment. I don't know much about desktop environment but I frequently saw **display manager** (e.g., SDDM) and **graphical session** (e.g., Xorg) while googling for a solution. ### Update The issue is resolved after installing sddm package since the plasma-desktop package doesn't come with a display manager.

I am currently running LightDM on my AlmaLinux 8.8 machine and I wanted to know if it's possible to remove the Other user option as shown below. I have already tried to edit the /etc/lightdm/lightdm.conf file and set the following options, however with no effect:

[Seat:*]
greeter-show-manual-login = false
greeter-allow-guest=false
allow-guests=false

I have restarted the LightDM service after saving my changes and even rebooted my machine, but no luck.