I have a single linux desktop at home, with every member of the family having their own user name / login combo (shared external drive for sharing pics, docs etc). I have realised that the GDM login screen shows the username for some and the 'full name' for others. e.g. for me it shows 'David Myers' (my full name, obviously), for my wife it shows helenm (her log in). In the most part this is not a problem, but I would like for it to be consistent between all users. I've clearly done something different when creating the users (which I did via the command line). Using sudo users-admin the application refuses to open up , but on the basic version (non root) all the details seem the same (obviously I can't view the advanced details). What I would like, is for it to display the login name in a larger bold font, followed by the full name in a smaller font in parenthesis. Is this possible (I'm sure it is)? Pertinent details: - OS : Debian - jessy. - desktop : XFCE - login screen : GDM (to allow user switching, and I can confirm that the system takes much longer to boot up to GDM rather than the native XFCE version).

I have a powerful machine that I want to use as a multi-seat system. It has two graphic cards and two pairs of keyboards and mice. I've been able to successfully configure two "seats" using udev and Xorg.conf, and launch two X servers from a script so two users can have independent sessions. Just for the record, here's my udev rules file, where I identify each USB hub and label the devices and the seats: SUBSYSTEM=="drm", KERNEL=="card[0-9]*", ATTRS{vendor}=="0x10de", DRIVERS=="nvidia", TAG+="master-of-seat" # SUBSYSTEM=="drm", KERNEL=="card0", ENV{ID_SEAT}="seat0" # SUBSYSTEM=="drm", KERNEL=="card1", ENV{ID_SEAT}="seat1" SUBSYSTEM=="input", ENV{ID_INPUT.tags}="input_default" # KVM HUBS KERNELS=="3-2", ATTRS{bDeviceClass}=="09", ENV{KVM_HUB}="1", ENV{ID_SEAT}="seat0" KERNELS=="3-8", ATTRS{bDeviceClass}=="09", ENV{KVM_HUB}="2", ENV{ID_SEAT}="seat1" # Devices of HUB 1 KERNEL=="event*", ENV{KVM_HUB}=="1", ATTRS{bInterfaceProtocol}=="01" SYMLINK+="kvm_keyboard_1" KERNEL=="event*", ENV{KVM_HUB}=="1", ATTRS{bInterfaceProtocol}=="02" SYMLINK+="kvm_mouse_1" # Devices of HUB 2 KERNEL=="event*", ENV{KVM_HUB}=="2", ATTRS{bInterfaceProtocol}=="01" SYMLINK+="kvm_keyboard_2" KERNEL=="event*", ENV{KVM_HUB}=="2", ATTRS{bInterfaceProtocol}=="02" SYMLINK+="kvm_mouse_2" # Default seat SUBSYSTEM=="input", TAG=="seat", ENV{ID_SEAT}=="" , ENV{ID_SEAT}="seat0" # set all tags accordingly ENV{ID_SEAT}!="", ENV{ID_INPUT.tags}+="$env{ID_SEAT}" TAG+="$env{ID_SEAT}" The relevant part of my xorg.conf file looks like this: Section "ServerFlags" # Option "AutoAddDevices" "false" # Option "AutoEnableDevices" "false" Option "DefaultServerLayout" "Layout0" Option "AllowMouseOpenFail" "true" Option "Xinerama" "0" EndSection # --------------------------------------------------------------- # LAYOUT Section "ServerLayout" Identifier "Layout0" Screen "Screen0" MatchSeat "seat0" Option "Clone" "off" EndSection Section "ServerLayout" Identifier "Layout1" Screen "Screen1" MatchSeat "seat1" Option "Clone" "off" EndSection As I said, **I can successfully launch** two independent sessions using the following script, but I'd like this to happen automatically on boot. #!/bin/bash set +x rm /etc/X11/xorg.conf cp ./xorg_independientes /etc/X11/xorg.conf # X (:0) systemctl stop gdm killall Xorg killall X systemctl restart gdm sleep 7 # X (:1) su - sit -c "startx /usr/bin/gnome-session -- :1 vt4 -layout Layout1 -seat seat1 -sharevts" & sleep 10 DISPLAY=:1 xhost + My approach would be setting the default target runlevel to 4 (so it has everything but graphics) and then placing these commands in a script somewhere.

After updating from Ubuntu 16.04 to 18.04, the login screen automatically changes to only accepting the password via clicking a virtual onscreen keyboard.  It is very inconvenient and annoying having to switch between several virtual screens simply to input a password.  I have searched online on how to disable this inconvenient feature of onscreen keyboard, but haven't found a good solution.  Any expert here has a green thumb for this issue? What I tried: * settings → universal access → screen keyboard: \ Setting the screen keyboard to "off" does not solve the above mentioned problem.

I have a fresh installation of Gentoo to which I would like to add the Gnome desktop and the GDM display manager. Installing Gnome works, but installing GDM results in errors I am having a hard time to get usable knowledge out of. My question is simple. What must be done to have Gnome 3 start at boot together with GDM? For installing Gnome I use this command: sudo emerge gnome-base/gnome And for trying to install GDM I use this command, which shows me errors with opus (some audio codec library) and ninja (some build system with a lower footprint than make): sudo emerge gnome-base/gdm This is the error I get: ninja: build stopped: subcommand failed. * ERROR: media-libs/opus-1.5.2::gentoo failed (compile phase): * ninja -v -j17 -l0 failed * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 2924: Called meson-multilib_src_compile * environment, line 1623: Called multilib-minimal_src_compile * environment, line 1817: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' * environment, line 2084: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 1777: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 1775: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' * environment, line 486: Called multilib-minimal_abi_src_compile * environment, line 1811: Called multilib_src_compile * environment, line 2304: Called meson_src_compile * environment, line 1690: Called eninja * environment, line 1195: Called die * The specific snippet of code: * "$@" || die -n "${*} failed" * * If you need support, post the output of emerge --info '=media-libs/opus-1.5.2::gentoo', * the complete build log and the output of emerge -pqv '=media-libs/opus-1.5.2::gentoo'. * The complete build log is located at '/var/tmp/portage/media-libs/opus-1.5.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/opus-1.5.2/temp/environment'. * Working directory: '/var/tmp/portage/media-libs/opus-1.5.2/work/opus-1.5.2-abi_x86_64.amd64' * S: '/var/tmp/portage/media-libs/opus-1.5.2/work/opus-1.5.2' >>> Failed to emerge media-libs/opus-1.5.2, Log file: >>> '/var/tmp/portage/media-libs/opus-1.5.2/temp/build.log' * Messages for package media-libs/opus-1.5.2: * ERROR: media-libs/opus-1.5.2::gentoo failed (compile phase): * ninja -v -j17 -l0 failed * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 2924: Called meson-multilib_src_compile * environment, line 1623: Called multilib-minimal_src_compile * environment, line 1817: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' * environment, line 2084: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 1777: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 1775: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' * environment, line 486: Called multilib-minimal_abi_src_compile * environment, line 1811: Called multilib_src_compile * environment, line 2304: Called meson_src_compile * environment, line 1690: Called eninja * environment, line 1195: Called die * The specific snippet of code: * "$@" || die -n "${*} failed" * * If you need support, post the output of emerge --info '=media-libs/opus-1.5.2::gentoo', * the complete build log and the output of emerge -pqv '=media-libs/opus-1.5.2::gentoo'. * The complete build log is located at '/var/tmp/portage/media-libs/opus-1.5.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/opus-1.5.2/temp/environment'. * Working directory: '/var/tmp/portage/media-libs/opus-1.5.2/work/opus-1.5.2-abi_x86_64.amd64' * S: '/var/tmp/portage/media-libs/opus-1.5.2/work/opus-1.5.2'

I'm using 64bit Debian Jessie and followed these instruction to install fglrx for Radeon HD 7000 series: https://wiki.debian.org/ATIProprietary However GNOME doesn't work after it. I installed different desktop environments and it worked. With GNOME, GDM doesn't start, and launching GNOME with startx crashes. What is the problem?

I'm trying to figure out why the graphical login prompt won't show up at the login page. I see the wallpaper just fine, but the graphical login prompt won't show up no matter how long I wait. So, In the console, I've done init 3 to shut down gdm and then restarted it with init 5. The problem still persists. I downloaded and installed kdm and set it as the default display manager through editing /etc/systemconfig/displaymanager. It worked fine, except that the main menu and many other items in the panels are gone. So I removed gdm with zypper and then reinstalled it again. I set the gdm as the default display manager and restarted gdm. The same problem shows up again. So I tried to bypass the login page entirely by enabling autologin. I put my username in the autologin section of /etc/systemconfig/displaymanager and restarted gdm. No go, I still get the same problem. I'm thinking it mightn't be gdm related and that something else is interfering with gdm startup, but I'm stumped at this point. Any ideas?

I have a few issues with the GDM login screen. I am using CentOS 6.5 and installed GNOME. I was able to change the background of the login screen by replacing the default.png image on the system. However: 1. Whenever the login screen loads, the "Appearance Settings" window shows - as if it is asking for a specific theme for GNOME. I really want this to go away... 2. I cannot figure out how to change the icon loaded in the login panel, nor how to change the name of the OS on this same panel (CentOS 6.5). Can anyone offer suggestions on how to make these changes? I've read a few articles on using the "Login Screen" manager, but I don't have that installed (and can't find it in the repo's). **EDIT #1**: The first was solved by removing a link from within /usr/share/gdm/autostart/LoginWindow/ called gnome-appearance-properties.desktop. **EDIT #2**: Looking in /usr/share/gdm/gdm-greeter-login-window.ui, I found the following code: True 64 computer If I comment this chunk out, the icon disappears on the login window. However, I cannot figure out which file it is referencing. I did a find / -name "computer*" and looked at every file this returned and none of them were the icon matching what is displayed. Another interesting thing: I can change the icon_name property from computer to start-here and the icon stays the same. However, if I change it to something more absurd such as my-custom-icon, it shows a broken (perhaps default) image in its place. Again, I searched for any file named start-here and they all are different.

I need to remove Suspend / Restart / Power Off… menu from Gnome Shell & GDM. I’ve been trying using Settings, Gnome Tweaks, Dconf Editor, but nothing found AFAIK. Trying to enter the Polkit conf file gave the same results. polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.login1.power-off" || action.id == "org.freedesktop.login1.reboot" || action.id == "org.freedesktop.login1.hibernate" || action.id == "org.freedesktop.login1.suspend") { return polkit.Result.NO; } }); Any clue? Thank you, Regards

I have a local user issue which I don't know how to solve: all users can log without any problem, except one user who is each time kicked back to gdm screen though password authehtication succeeds (no password error message). 'su - {user}' works fine, so not a pwd issue. I tried to remove ~{user}/.ICEauthority and all /tmp files|dirs belonging to this user, but still doesn't work. I guess there is kind of trivial solution, but can't figure out what it is. :-( I'm in Fedora 30 under Wayland, more than happy to provide more information if needed. A bit more details/context: last shows that indeed the user actually connected on a tty watch -n 0.1 'who -a' doesn't show the user, even a single time So it seems that login succeeds, a tty is attributed, but it never goes to the who command input source. Could this help? Thanks! Any idea?
Thanks a lot
Emmanuel Answering to myself, finally succeeded in sorting this out.
Was right, wasn't a system issue but a local one.
In despair, I listed all files/dir in faulty user home which had been modified within a short time range before issue appeared, and finally removed following dirs in ~user/.local/share: - gnome-shell - gvfs-metadata - keyrings Then tried to log with the user, and guess what, worked like a charm! So it was related to one (or all) of these directories. I would suspect .gnome-shell, but no evidence of it.
If now someone wants to try to clarify my answer explaining what may have happened, I would be more than happy and would help the community.
Also I changed the topic to make it more relevant.
Thanks!

I have Googled this one and tried so many combinations, with no success. I need the GDM login greeter to display one and only one username. In effect, what I need is something like this in **/etc/gdm/custom.conf**: [greeter] ExcludeAll=true Include=guest This does not work, however, because ExcludeAll is not a valid option. IncludeAll=false does nothing either. I've tried every combination that I can think of. Despite being discouraged, I modified **/etc/gdm/gdm.schemas**, trying a variety of combinations similar to the above. No go. I am aware of: gconftool-2 --config-source xml:readwrite:/etc/gconf/gconf.xml.defaults --direct --type bool --set /apps/gdm/simple-greeter/disable_user_list true but this is not an applicable solution, as it removes the user list completely. I need one specific username to appear. The only practical solution I can find is to, upon user login, run a script which will append that username to the "Exclude" list in **/etc/gdm/custom.conf**. This is hacky, and not preferable. This is for a public-use machine. People can log in with their LDAP accounts if they have them, or they can select "Guest" from the login screen. The people who log in with their LDAP accounts should NOT have their names visible on the login screen, but the "Guest" option must remain. Using gnome 2.28.

My final goal is to make use of a Geforce GTX 550 Ti on a modern Linux Gnome desktop. Since recent Ubuntu versions stopped supporting the **Nvidia 390 driver** that is required for this I instead chose **Debian Sid** (a.k.a. Unstable), which offers seemingly straightforward install instructions for it . After trying to install them I'm left with a white "Something has gone wrong" low-resolution GUI error screen instead of the login screen (no buttons, no cursor), and switching to a console doesn't give me a login prompt, but only black screen and non-responsive caret at top left. I then need to restart and do a safe-boot to access the console. *Update:* After a full-upgrade I now end up with software rendering, which is technically better than having to reboot, but not much. ### What I've done 1. Installed **Debian Testing** amd64 weekly DVD build. This was working just fine in Gnome desktop using nouveau and Wayland. 2. Filled my sources.list with the appropriate content since it was completely empty apart from a reference to the install media (USB iso). Before that I couldn't even do an apt update. I don't know why I was left with an essentially empty sources.list immediately following a clean install. 3. Enabled unstable by adding one line in sources.list, according to Debian's instructions to enable unstable on Testing . 4. Followed the instructions for Nvidia 390 driver for Sid in the above linked wiki page. Yes, I **forgot to install the kernel headers** before doing this. 5. Ended up with a non-working system as described above, so I uninstalled the two driver packages again using safe-boot (nvidia-legacy-390xx-driver firmware-misc-nonfree) and removed all three nvidia symlinks in etc/modprobe.d (one of which was blacklisting nouveau). I got a working system back. 6. I realized my mistake and **installed the kernel headers** (linux-headers-amd64) according to instructions. 7. I again tried installing the driver (nvidia-legacy-390xx-driver firmware-misc-nonfree) but ended up with the same result as before after a reboot. 8. I didn't see much actual build-action going on when installing the driver packages, so I tried to --reinstall the nvidia-legacy-390xx-kernel-dkms package, which finally actually menioned "building" something. 9. I still ended up in the same situation, i.e. no login screen and no access to console during normal boot. I'm unsure if I accidentally messed something up and didn't fix it properly, or what the problem could be at this point. **What would be the best course of action to troubleshoot this situation?** I also did a full-upgrade for good measure to make sure all packages were up to date. ### Observations - When the system is working (with nouveau), Gnome desktop works fine on Wayland but gives a fullscreen "Something has gone wrong" GUI error screen when logging in with Gnome on Xorg. It has a button to "log out" which I can click with the space bar (no mouse cursor). MATE desktop works fine though, and it also uses Xorg. I'm fine with Gnome on Xorg temporarily not working — it's Testing + Unstable after all, but I would like to think that at least the login screen (gdm) and console should work if the graphics drivers work (just as with nouveau)? - One reason I have specifically chosen Debian *Testing*, i.e. Debian 13 Trixie, instead of Debian 12 is that I needed to ensure I had the very **latest nouveau possible**. This is because even on the most up-to-date Ubuntu 24.10 the nouveau driver will invariably freeze the entire system after some time (I have determined this experimentally; Ubuntu is locking up only when nouveau is loaded and never when running only on Intel integrated graphics). I'm trying to maximize my chances that nouveau will work (Windows 10 does not freeze, so I attribute this to the nouveau drivers, and not to the hardware). ### Additional info #### sources.list I had to reconstruct this file immediately after OS install, for some reason, because it only contained the first line (now commented out).

# deb cdrom:[Debian GNU/Linux testing _Trixie_ - Official Snapshot amd64 DVD Binary-1 with firmware 20250310-03:29]/ trixie contrib main non-free-firmware

# unstable
deb http://deb.debian.org/debian  unstable main contrib non-free non-free-firmware


deb http://deb.debian.org/debian  testing main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian  testing main contrib non-free non-free-firmware

deb http://deb.debian.org/debian-security/  testing-security main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian-security/  testing-security contrib non-free main non-free-firmware

deb http://deb.debian.org/debian  testing-updates contrib non-free main non-free-firmware
deb-src http://deb.debian.org/debian  testing-updates contrib non-free main non-free-firmware

#### Xorg log errors These might not be relevant since I can't even get to the login screen and console, and since MATE works on Xorg, but I include these for completeness until I know they can be dismissed.

$ grep EE /var/log/Xorg.0.log
[    74.735] Current Operating System: Linux debian 6.12.17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.17-1 (2025-03-01) x86_64
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    75.166] (EE) systemd-logind: failed to take device /dev/dri/card0: Invalid argument
[    77.033] (EE) Failed to load module "nv" (module does not exist, 0)
[    77.552] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[    77.552] (EE) open /dev/dri/card0: Invalid argument
[    77.552] (EE) open /dev/dri/card0: Invalid argument
[    77.562] (EE) Unable to find a valid framebuffer device
[    77.563] (EE) Screen 0 deleted because of no matching config section.
[    77.563] (EE) Screen 0 deleted because of no matching config section.
[    77.653] (II) Initializing extension MIT-SCREEN-SAVER
[    77.667] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[    78.331] (EE) systemd-logind: failed to take device /dev/dri/card0: Invalid argument

$ grep EE /var/log/Xorg.0.log.old
[    23.670] Current Operating System: Linux debian 6.12.17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.17-1 (2025-03-01) x86_64
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    23.970] (EE) systemd-logind: failed to take device /dev/dri/card0: Invalid argument
[    25.852] (EE) Failed to load module "nv" (module does not exist, 0)
[    26.471] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[    26.471] (EE) open /dev/dri/card0: Invalid argument
[    26.472] (EE) open /dev/dri/card0: Invalid argument
[    26.490] (EE) Unable to find a valid framebuffer device
[    26.491] (EE) Screen 0 deleted because of no matching config section.
[    26.491] (EE) Screen 0 deleted because of no matching config section.
[    26.522] (II) Initializing extension MIT-SCREEN-SAVER
[    26.535] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[    27.025] (EE) systemd-logind: failed to take device /dev/dri/card0: Invalid argument

Feel free to ask for anything else that seems relevant and I'll add it.

I have been using my usual Debian 11 installation then I launched a command of systemctl reboot, after reboot I have got a black screen which stayed for around 30 seconds before the grub screen appeared, then after selecting the os I get an output that looks like so... [FAILED] to start Update UTMP about System Boot/Shutdown See 'systemctl status systemd-update-utmp.service' for details. then after a few successful lines it tries to start gdm then stops and fails then it repeats till it reaches a plymouth terminate and stays like this unless I to ALT+F2 After logging in I ran systemctl status systemd-update-utmp.service and this is the output that I recieved

. systemd-update-utmp.service - UPDATE UTMP about System Boot/Shutdown
   Loaded: loaded (/lib/systemd/system/systemd-update-utmp.service; static)
   Active: failed (Result: exit-code) since Tue 2022-02-08 14:30:01 EET; 8min  ago
     Docs: man:systemd-update-utmp.service
           man:utmp(5)
   Process: 818 ExecStart=/lib/systemd/systemd-update-utmp reboot (code=exited, status=1/FAILURE)
  Main PID: 818 (code=exited, status=1/FAILURE)
     CPU: 5ms

Feb 08 14:30:01 D20 systemd: Starting Update UTMP about System Boot/Shutdown...
Feb 08 14:30:01 D20 systemd-update-utmp: Failed to write utmp record: No space left on device
Feb 08 14:30:01 D20 systemd: systemd-update-utmp.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 14:30:01 D20 systemd: systemd-update-utmp.service: Failed with result 'exit-code'.
Feb 08 14:30:01 D20 systemd: Failed to start Update UTMP about System Boot/Shutdown.

and when I run systemctl status gdm.service the output I recieve is...

. gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: failed (Result: exit-code) since Tue 2022-02-08 14:31:53 EET; 19min ago
  Process: 1292 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=1/FAILURE)
      CPU: 5ms

Feb 08 14:31:53 D20 systemd: gdm.service: Scheduled restart job, restart counter is at 5
Feb 08 14:31:53 D20 systemd: Stopped GNOME Display Manager.
Feb 08 14:31:53 D20 systemd: gdm.service: Start request repeated too quickly.
Feb 08 14:31:53 D20 systemd: gdm.service: Failed with result 'exit-code'.
Feb 08 14:31:53 D20 systemd: Failed to start GNOME Display Manager.
Feb 08 14:31:53 D20 systemd: gdm.service: Triggering OnFailure= dependencies.

I am a beginner at linux (and asking questions) I could not find this problem replicated anywhere, please help me or at least clarify any ways I can improve this question. Edit: - I have tried to add nouveax.modeset=0 to grub and still same problem occurs. - I have ran df and found out that /dev/mapper/D20--vg-root which is mounted on **/** is **100% used**.

Where is the distribution logo stored, which is displayed at the bottom of the GNOME login screen? Besides, how to remove the logo correctly. Not just remove the image, but remove links to it, etc. I saw this [answer](https://unix.stackexchange.com/questions/701718/how-can-i-change-or-remove-the-orange-login-screen-logo-in-ubuntu-22-04) . Apparently this is true only for Ubuntu. Tell me how it works in other distributions like Fedora, Debian, Manjaro, Arch.

I tried to customize my login screen for gnome on fedora this week using the GDM-Settings application from flathub. I enabled the DisableUserLogin setting (don't ask why, i don't know either) while my root user is locked. Now when I reboot, I of course can't log in to my user account anymore with the gnome login screen. I tried to disable the DisableUserLogin setting again in several ways, but none have worked so far. I tried to disable the setting again by removing /etc/gdm/custom.conf, executing the gdm reset command for that specific setting using the cli, and more. I think gdm-settings overrides the settings somewhere else? I looked at their [repo](https://github.com/gdm-settings/gdm-settings) , but couldn't really find the snippet where they execute the command or store the config. Sidenote: While messing around I also added an image as logo to the login screen, which covers the entire log in field, so there might be something on the screen that I'm not seeing due to that. I removed the source image but it still shows on the login screen, so I need to log in and use GDM-Settings to fix that. For any more info don't hesitate to ask and I'll try to provide you with it asap. I'd love to be able to log in on my workstation normally again :)

I'm using my Linux only managed by root user (I know is not the best practice). The first point is, since beginning, my *gdm* is not showing root user on the initial list, so there is not available users on initial list. How can I set root to appear on the list or selected by default? Here is a screenshot of what I'm talking about.It only shows "Is not on the list?", so I must click there to type root. The second point is, I want to use *gnome-classic* by default but now I must select it always and it is not remembering last login. I read it should remember... is because is root user? How can I put *gnome-classic* as default environment?  I tried so many things... editing /var/lib/AccountsService/users/root and putting XSession=gnome-classic This is the content of my /usr/share/xsessions dir: gnome-classic.desktop icewm-session.desktop sle-classic.desktop gnome.desktop icewm.desktop xsession.desktop So the *gnome-classic* is there... I don't know how to make it work as default.

I am using Debian 9. After installing Gnome I only see my mouse cursor on my computer screen. I uninstalled Gnome and enabled X11 but it didn't work. I need to connect to the board I use via ssh and type > startx in order to get an image on the screen. I may have messed something up while installing gnome. **Update:** apt install gdm is not working: root@linaro-alip:~# apt install gdm Reading package lists... Done Building dependency tree Reading state information... Done Package gdm is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libgdm1 cinnamon-control-center-data E: Package 'gdm' has no installation candidate **Update 2:** dpkg-reconfigure lightdm >> I manually selected lightdm root@linaro-alip:~# systemctl enable lightdm

Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable lightdm
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

The problem is still not fixed. When I use the below command it says the file does not exist. How can I fix this? update-rc.d '/etc/init.d/xserver start' defaults

update-rc.d: error: initscript does not exist: /etc/init.d//etc/init.d/xserver start

I’m working on configuring Rocky Linux 8 for newly imaged machines and would like to have X11 set as the default session, but still keep Wayland enabled for users who prefer it. The goal is to allow users to select Wayland or X11 from the login screen. Currently, I have the following configuration in /etc/gdm/custom.conf:

# /etc/gdm/custom.conf

# GDM configuration storage

[daemon]
AutomaticLoginEnable=false
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

However, when I set WaylandEnable=false, the cogwheel option to switch between Wayland and X11 disappears entirely at the login screen. If I set WaylandEnable=true, it automatically defaults to Wayland instead of X11, which is not what I want. Is there a way to default to X11, but still allow users to switch to Wayland at the login screen? Any suggestions or insights would be greatly appreciated! Is there a way to default to X11, but still allow users to switch to Wayland at the login screen? Any suggestions or insights would be greatly appreciated!

I am using the french bépo layout for my keyboard on a freshly installed Debian 12. Everything is fine once I am logged in, but unfortunately the GDM login screen is using a qwerty layout. How can I change it so it also uses the bépo layout ? Here is my current configuration :

❯ cat /etc/default/keyboard
XKBLAYOUT="fr"
BACKSPACE="guess"
XKBMODEL="pc105"
XKBVARIANT="bepo_afnor"
XKBOPTIONS=""

❯ cat /etc/X11/xorg.conf.d/00-keyboard.conf
Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "fr"
        Option "XkbVariant" "bepo_afnor"
EndSection

❯ localectl
System Locale: LANG=fr_FR.UTF-8
    VC Keymap: fr
   X11 Layout: fr
    X11 Model: pc105
  X11 Variant: bepo_afnor

As you can see, I already tried solutions mentioned in another question (regarding Arch Linux), but without success. Here are more information on my gdm and its configuration :

❯ /usr/sbin/gdm3 --version
GDM 43.0

❯ ls -al /etc/gdm3
total 48
drwxr-xr-x   6 root root  4096 Oct 20 00:31 .
drwxr-xr-x 138 root root 12288 Oct 22 21:21 ..
-rw-r--r--   1 root root   552 Oct 20 00:31 daemon.conf
-rw-r--r--   1 root root  1472 Jan 29  2023 greeter.dconf-defaults
drwxr-xr-x   2 root root  4096 Oct 22 21:01 Init
drwxr-xr-x   2 root root  4096 Oct 20 00:24 PostLogin
drwxr-xr-x   2 root root  4096 Oct 18 15:44 PostSession
drwxr-xr-x   2 root root  4096 Oct 18 15:44 PreSession
-rwxr-xr-x   1 root root  5996 Jan 29  2023 Xsession

❯ ls -al /etc/gdm3/Init
total 16
drwxr-xr-x 2 root root 4096 Oct 22 21:01 .
drwxr-xr-x 6 root root 4096 Oct 20 00:31 ..
-rwxr-xr-x 1 root root 2933 Oct 22 21:01 :1
-rwxr-xr-x 1 root root 2932 Oct 22 21:00 Default

In order to switch to a new keyboard layout I have added an setxkbmap command to my Openbox's autostart.sh. However, this only takes effect once I log in (when Openbox starts). *While* logging in, in GDM (I suppose), the layout I chose when installing the system is still active - which is distracting in my efforts. What do I have to do to have this default layout changed? (OS: Debian 7.1)

Recently I experimented with changing the maximum number of tty's on the system from **63** to **128**. I was successful in doing this, and now I'm running into a very strange problem. I'm running gdm on /dev/tty1 and an Xfce4 session through it (running on /dev/tty2). I also have getty running on /dev/tty63 and /dev/tty64 The problem is that when I run the chvt 2 command from tty**63** (previous MAX_NR_CONSOLES specified in include/uapi/linux/vt.h), everything switches successfully and I can use Xfce4. But if I run chvt 2 from tty**64**, the system freezes (no kernel panic) and I can't use mouse/keyboard/other input devices (upd: when I replug keyboard it starts working). Funny enough, when you execute session binary via strace -f everything starts working fine (switching from **64** to **2** tty works). The problem occurs exclusively when using gdm in **Xorg/Wayland** sessions. When using a different display manager/manual start everything works fine. My question is: **what could be going wrong?** Why when switching to the second tty from any other tty that is <=63 everything hangs? Who to blame? Which syscall/software?