A list of puns related to "XDM (display manager)"
I had been using ratpoison without a display manager til now and all worked fine.
I am testing out using a display manager because I have read there is a way to save your X session when using dms such that you can restore it when you exit from the single-passthrough vm.
However when I run the vm after activating the dm there is no sound in the vm and also when I ran a game it would hand when I pressed the exit button in the game.
Any ideas for what has caused this change in behavior?
I have installed xdm but I can't find any documentation on how to save and restore the sessions only that it 'can be done'.
When I search for 'restore x session xdm' or the like I do not find any related results. I found a great project for python on github xsession-manager but unfortunately it relies on wmctrl which does not work with ratpoison so sticking with the display manager/xdm route but gotta find what exactly I have to set to make it work.
Hey I've installed gentoo recently and I'm trying to get to the desktop, I've followed a video by DorianDotSlash part 2 on getting the desktop but when I enter the command to start it doesnt load the desktop, it says it's starting but doesnt show, I redid the emerge --ask kde-plasma/plasma meta and followed the steps for xdm, I did notice the /etc/conf.d/xdm file didnt have blue text as well as etc/conf.d/display-manager but I'm not sure if that matters,
I retried the second time with display-manager and did the command in the title but again nothing happens,
I didnt create a user as I wanted to see if I can enter the desktop as root to continue with my desktop,
Anything I missed?
Btw the first error I had, it said something about getting some x11-apps thing and I did but it still wont budge. More in the comments
That is available through pkg or ports. I have used xdm up until this point but i would like to try something else.
Would I still be able to login in my system the same way I have to make login though a tty?
Fixed with gnl221's help
Hi, I'm running ubuntu 20.04.
I recently decided to try out the kde plasma desktop on my ubuntu installation, and after installing and playing with it for a while, i decided that it was not for me and subsequently tried to remove it.
This is where the screw up occurs: i followed this guide, and on disabling sddm i immediately encountered a blank, dark grey screen. At this point I think no worries, I'll go to linux's recovery root shell and enable gdm3 from there, but unfortunately the below is what comes up when i run sudo systemctl enable gdm3
https://preview.redd.it/wj9dhz5ep7e81.png?width=1812&format=png&auto=webp&s=b0bba9b66bae08d4e7d8af7449a6f5c7baecb62e
Realising that this was not working, i enabled and started sddm from the recovery root shell, but the login page is now in a very weird configuration. A photo of that is attached below as well.
https://preview.redd.it/9iokofxgp7e81.jpg?width=4000&format=pjpg&auto=webp&s=fce33b9ffb3de5a69436963c4342387ba85f479b
I would really appreciate some help in getting this login page back to the ubuntu default, and using gdm3 again since I'm going to be sticking to gnome.
Thanks to anybody who takes the time to read this.
After a recent post, I had occasion to revisit the Slim display manager, which has been abandoned as a project for many years, but still is available in many distributions, including Void. Although there are many alternatives, Slim really is a nice, light-weight DM, and while there are apparently no issues with Systemd, Slim is slightly broken for elogind (probably not just for Void).
Elogind registers seat/sessions just fine with Slim, but Slim does not proactively end the user's elogind session at logout. This leaves the seat/session hanging, until it essentially "dies of old age" after 20 seconds or so. So all is well unless, after a logout, a new login occurs in less than 20-30 seconds, in which case the login succeeds, but a new seat/session is not created, which can lead to some odd symptoms, often polkit issues. In practice, it may appear that every other login is affected.
Because the user may terminate their own session, there is an easy hack that fixes this, for anyone who runs across it. For an individual user, you may just amend ~/.xinitrc with the following:
# $1 is %session variable passed from Slim, or replace
# with DE start command.
# Do NOT use "exec" to start DE, or elogind session
# may not terminate properly (bring execution back here at logout)
$1
loginctl terminate-session $XDG_SESSION_ID
--------------------------------------------------------------------
A second issue with Slim is that it may not pick up dpi or some other X settings at login, so as an alternative, or globally or for multiple users, I have created an extra file which addresses both issues, which was modified from old versions of xdm Xsession. No changes to individual user ~/.xinitrc are needed with this approach. This requires editing /etc/slim.conf to provide:
login_cmd exec /bin/bash /usr/share/slim/slim-session
EDIT: should have been:
login_cmd exec /bin/bash /usr/share/slim/slim-session %session
And then creating (and making executable) the file, /usr/share/slim/slim-session with the following contents:
#! /bin/sh
########### Slim Xsession ##############
#
# Inspired by XDM Xsession from Xorg Foundation (MIT license)
# Modified by William Rueger (furryfixer)
#
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $s
... keep reading on reddit β‘When I get to my login screen, the display manager (both sddm and slim) intermittently does not recognize any keystrokes. Sometimes, (1) in a few seconds, the DM will start recognizing keys, or (2) it will never recognize keys until I reboot and get lucky, or (3) it instantly recognizes keys. This can happen on a boot or a wake from sleep, but on boot (using grub), I check that grub sees keystrokes (and it always does) but moments later the DM often cannot. When using sddm, I can bring up the onscreen keyboard and login with the mouse/trackpad. After login, there seem to be no problems with apps seeing the keyboard so far. Note:
As a workaround, I can just stick with sddm and use the onscreen keyboard if necessary. But, I'm concerned if unfixed, the problem may resurface in other manifestations. Any advice on how to isolate / fix the matter?
Specs:
Model: HP Laptop 14-dq2xxx (14-dq2053cl)
Distro: KDE neon User - Plasma 25th Anniversary Edition x86_64
Kernel: Linux 5.13.0-27-generic
Window Manager: KWin
Desktop Environment: KDE
CPU: 8 x 11th Gen Intel(R) Core(TM) i3-1125G4 @ 2.00GHz
GPU: Intel Corporation Device 9a78 (rev 01)
RAM: 521 MiB / 7595 MiB
Check the status here: https://status.nicehash.com
Right now, when starting up my Windows VM, I have to quit the DM, to be able to use single GPU passthrough.
The problem is, my session and running apps get closed too.
Is there a way to keep them still open after spinning up the VM and get back to the same state after shutting it down?
I was thinking about some sort of "routing" the Linux session to the internal GPU for the time being while the VM is running.
Is something like that possible?
I have a 2021 MacBook Pro 16" (32gb Ram 32c M1 Max) and I had crazy memory usage and CPU usage (Memory Pressure graph was spiking yellow with swap used, cpu usage was 70%+) from WindowServer.
I use an external Dell 4k monitor and had installed DDM to manage the windows. I closed out of it and instantly WindowsServer went from 27gb of memory used down to 1.5.
I know that there may be other memory leak culprits that still haven't been found, but if you're experiencing it and use DDM, try closing it and see if it helps. I recommend using other windows snapping tools if you need the functionality of DDM.
I use openrc and xfce, I'm new to linux. I installed lightdm by doing "rc-update add lightdm" and changing the session greeter in the lightdm.conf file. Upon reboot my login screen looked the same as before but now my resolution is stuck at 800x600 and it doesn't see my second display, logging in doesn't fix those issues. I attempted deleting lightdm but upon reboot didn't have a gui, so I reinstalled it and I got my gui back but the issues mentioned earlier still remain. How would I fix this? I have also tried downloading ly instead but when trying to add it as a service, I get an error saying it can't find ly as a service.
Hi! First time Arch user here, Iβm trying to install Qtile and Light Display Manager, but whenever I boot, Iβm greeted by:
[FAILED] Failed to start Light Display Manager.
printed out anywhere between 1 and 5 times, and the cursor flashes but the prompt doesnβt appear, so Iβm unable to type anything.
I was following the instructions of this video up until 3:00 (sans the VM section). Iβm using a fresh install, which I set up following this video.
Anything I can do?
EDIT:
I reinstalled xorg and ran lightdm
from tty2 and now lightdm runs, but after inputting my password, it just returns to the login screen. I have tried both solutions from the wiki, but the .Xauthority
file doesnβt exist and the session-wrapper
line is already there.
EDIT 2:
Thank you for all your help, but Iβve decided to use sddm instead of lightdm, since it works out of the box.
Trying to fix this last piece of my entaglement with pfsense and moving over to new hardware - so every restore route I've taken, even just doing the baseline Package Manager portion out of the xml file config- it will not display the currently installed packages under General- Package Manager--
I did follow netgates instructions here in the event of broken package database: https://docs.netgate.com/pfsense/en/latest/troubleshooting/pkg-broken-database.html
Rebooted, still no dice. What's strange is the other tab will load the available packages to download. Any advice?
Hi guys I have installed artix runit , everything work smoothly I just can't install slim , I add arch repo , when I used pacman it says slim not found When I use paru it say failed to validate sha256sums
Thanks for the help , I appreciate it
Hi,
i love xmonad and the minimalism in it. Now i am looking for a ultralightweight Display Manager / Loginscreen-thing. What Display Managers do you use in combination with xmonad? I already found ly but i am a bit scarred of the installation.
cheerio
A couple of days ago, I had an idea to write a very customizable TUI Display/Login manager in purely Rust. This is kinda inspired by Ly. I got to work and here is the working proof-of-concept. https://github.com/coastalwhite/lemurs
While there is still a lot of work to do, it now does work. Ready for feedback :)
Hi all,i was trying --current today and i found out that the slim display manager isn't available anymore. do you have any suggestion for an alternative aside from xenodm?
Hi,
Since I've updated to windows 11 the display manager is not showing you the difference between 2 monitors of different size.
My main monitor is a 32" and the second one is a 27".
https://preview.redd.it/5kqovs9pdcb81.png?width=806&format=png&auto=webp&s=b1a1b2c2a7e8491de2bbeb097b95d1ba4a51138a
Hello everyone, newbie here. Is it possibel to use ly instead of lightdm/sddm in nixos? It is present in the repo but I don't know the way to fire it up. I tried to change the "services.xserver.displayManager.lightdm.enable = true" to services.xserver.displayManager.ly.enable = true, but it refused to rebuild. I also tried to enable ly service but it does not exist though the package is installed. Wiki has no entry about ly, so I ask for help here
I can run window managers only on minimal distributions which give you a simple tty after installation. I have not figured my way out to use window managers in fedora, manjaro, etc.. Which have pre-installed desktop environments and display managers.
You apparently have to create some files in a certain directory, but I do not know what to do precisely. So?
Thanks!
https://preview.redd.it/qh8d07owh3981.png?width=755&format=png&auto=webp&s=4cb2f8bbdb302795b584a4586e5b77cf8548312b
is this going to format? I dont want to format, i just need to copy files
I recently switched to a new system, which notably has a different graphics card (AMD). Since I had no driver issues after the switch, I decided the remove the Nvidia drivers which I had still installed (since I didn't need them any more). After removing the drivers and rebooting, the system gets stuck at trying to start my display manager (LightDM). Reinstalling the nvidia drivers and rebooting fixes the issue.
WHY?
Can someone help me figure this out?
I decided to reinstall artix runit and went with ly for my login manager after a lot of digging around got to at least show on the screen on boot but for whatever reason when i try to login it goes right back to login screen with a authentication error but i know credentials are good.
Any help will be appreciated thanks
Leaning toward the New Smith and Wesson 4in or 4.6in barrel ? and my second choice is the XDM Elite combat ? Whatβs your guys opinion on these Handgun and which one would you guys get and why? Glock is my last option because I already have a lot of glocks lol
Please note that this site uses cookies to personalise content and adverts, to provide social media features, and to analyse web traffic. Click here for more information.