Talk:X display manager

Rename: Session Manager

I impudently suggest that this type of program be renamed: Session Manager, since that is what is does: it initiates and manages sessions of different users. And while we are at it, Display server could also get a better name (because it also handles the input from evdev and not just the ouput to framebuffer), but I haven't come up with one yet (UserInteractionCore and MainUserInterfaceThingy are not better names).

Now jokes aside, the X (version 11) (a.k.a. X11) - display server - protocol is about to be replaced with the Wayland - display server - protocol. Some existing (X) window managers, like KWin and Mutter are on the way in becoming wayland compositors. Since the session manager a.k.a. the X display manager will likely also have to be ported from X11 to Wayland (I am assuming that because of the "X" in the naming), should the article be renamed and should we create a different article? ScotXW (talk) 20:15, 22 August 2013 (UTC)

The session manager is started by the display manager. They are completely different. Also the window manager is not a display manager. None of these concepts directly translate to wayland.174.29.193.158 (talk) 23:56, 29 September 2015 (UTC)

References to this topic in the main article needs to be updated although of course years after these comments were originally posted, today the Display Manager still exists and will not be renamed. But, it should be noted that today deploying an X server for both local and remote connections is likely optional. At least one current TigerVNC deployment configuration (Multi-user) replaces the X server with a socket-based service which spawns individual network connections on demand. It's my understanding also that local X support, particularly for Wayland implements Unix sockets, replacing the X server. Putztzu (talk) 18:26, 27 November 2019 (UTC)

Merge

I understand why the merge has been proposed: as the articles currently stand, XDM contains little that is not in X window manager. However, it seems that other window managers have their own articles, and that the XDM article could possibly be expanded. I therefore disagree with the merge. - Liberatore(T) 09:17, 21 December 2005 (UTC)

I also oppose merging as the display manager has nothing in common with the window manager. The biggest difference is that the window manager is a user task and the display manager is a system task. 174.29.193.158 (talk) 23:59, 29 September 2015 (UTC)

Move discussion in process

There is a move discussion in progress on Talk:XDM which affects this page. Please participate on that page and not in this talk page section. Thank you. —RFC bot 21:31, 4 September 2009 (UTC)

this is obsolete. 174.29.193.158 (talk) 00:03, 30 September 2015 (UTC)

This article is confusing.

One cannot move from using the word "server" to "Xserver" in the description.

Servers must have clients. Roles of servers and clients can alternate, but they should be clear.

An Xserver is a daemon/service running on which machine? What other daemons are running and where? What other clients are running and where?

Connections across remote media, using TCP/IP for e.g. must be clear.

The only people who will understand this article are experts who already understand.

It needs to be clearly explained as it is both crucial and complex. How else can we get interactions with Operating Systems without GUI consoles? In the future Cloud Technologies, it will become absolutely essential to have good remote GUIs. —Preceding unsigned comment added by 86.9.13.234 (talk) 14:53, 20 July 2010 (UTC)

Some of the Negatives are Incorrect

Some of the negatives are either ancient news or due to xdm / xdmcp misconfiguration (and unix networking mis-configuration). Note for passwords XDM uses pam(1) or login(1) and it can't be intercepted locally - only if you use X to transport over a remote connection. XDM always uses a DES encryption for the key for X. Yea X is a standard unix networking app and like any should be either openssl secured or configured or ssh secured. But it's not a big deal for most people what XDM and X do is good enough without the extra site-specific security configuration headaches. —Preceding unsigned comment added by 70.177.175.218 (talk) 10:58, 28 February 2011 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 3 external links on X display manager (program type). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive http://web.archive.org/web/20121106004540/http://repos.e-x-a.org:80/view.cgi/orthos to http://repos.e-x-a.org/view.cgi/orthos/
• Added archive http://web.archive.org/web/20091223224641/http://www.enricozini.org:80/sw/nodm/ to http://www.enricozini.org/sw/nodm/
• Added archive http://web.archive.org/web/20051102064732/http://www.xfree86.org:80/current/xdm.1.html to http://www.xfree86.org/current/xdm.1.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 16:17, 16 July 2016 (UTC)

Graphical login manager

This source suggests it be renamed Graphical login manager. In my opinion, such name is much clearer. What do you think? genium ⟨✉⟩ 21:27, 3 March 2019 (UTC)

IMO it's not for the Wikipedia community to rename anything, conventional nomenclature by people who use the technology should always be accepted and used consistently. Putztzu (talk) 18:36, 27 November 2019 (UTC)

How about merging this thread with #Rename: Session Manager? They are both talking about rename of the title. --Franklin Yu (talk) 05:55, 4 December 2019 (UTC)

SDDM "Active"

Am surprised to see SDDM listed as "Active" Am not modifying the article itself because don't know what "Active" is supposed to mean. SDDM has never supported XDMCP and RFB which means remote desktop apps like VNC are not supported... Whereas perhaps every "Inactive" DM does support. Putztzu (talk) 18:10, 27 November 2019 (UTC)

Will remove as in https://github.com/sddm/sddm/issues/1069 and https://github.com/sddm/sddm/issues/1180 are closed because of inactivity instead of implementation.

CDM incorrect URL and activity

I'm the author of CDM. A while back, I changed my GitHub username (and my username pretty much everywhere) from ghost1227 to evertiro. Hence, the URL on the CDM link is incorrect. I attempted to update it myself, but it got flagged for advertising. Additionally, CDM is listed as inactive. It is... but it isn't. CDM still gets maintenance updates on occasion, but the lack of updates isn't due to inactivity, it's simply feature complete for what I originally intended. Since it has basically zero external dependencies, it doesn't require updates just because a dependency updates. — Preceding unsigned comment added by Evertiro (talk • contribs) 21:54, 17 December 2021 (UTC)