I successfully installed Debian 12 (with the KDE Plasma DE) on my PC, and the first time I logged into the desktop environment, I noticed there were two desktop sessions to choose from: 1. Plasma (Wayland) 2. Plasma (X11) By default, Wayland is used. When I tried to log in using my username and password, I was unable to, even though my password was 100% correct. However, when I switched the session from Wayland to X11, I was able to log in successfully. My questions are: 1. Since this is a fresh install of Debian 12, why are there two desktop sessions (Wayland and X11)? 2. Are they interdependent an can I remove Wayland?

I just switched almost all of my computers over to CachyOS, but I have a big issue now. AnyDesk isn't working. It worked perfectly before. I'm able to connect to other computers that are running SteamOS, Windows 10 and Windows 11, but can't connect to any of my own CachyOS computers from my own computers. I am however able to connect from CachyOS to my other computers. I keep getting this popup: --- I searched a bit and it seems like some people on Ubuntu are having the same issue by looking at this question . The answers there aren't very helpful though. As an example, I don't even have that gdm3 directory. So therefor I can't find this file: /etc/gdm3/custom.conf.

I realise that the method may differ between [XOrg ≤ V11](https://superuser.com/q/271436/904401) and Wayland implementers, especially amongst compositors. Consequently, my focus is ⪆ kwin-6.3.3-1. I ask because I want to be able to ascertain what the current colour profile is without needing to access kcm_colord's GUI. ##### Evaluations [colormgr get-devices returns $Null](https://www.reddit.com/r/wayland/comments/1fuvri0/comment/mjgafdk/?context=3#:~:text=On%20wayland%2C%20I%20don 't%20get,colormgr%20get%2Ddevices&text=colormgr%20get%2Ddevices%20returns%20$Null%20for%20me%20too) for me, on KWin's Wayland implementation.

I wonder whether the display server protocol that my system uses can affect some capabilities in my terminal, such as 1. Clipboard interaction. 1. Rendering images on terminal, etc... Since the primary role of a display server protocol is to manage graphical user interfaces, I am unsure if it affects the terminal.

# Background I am running Awesome WM inside my virtual machine. From Awesome WM's [guide](https://awesomewm.org/doc/api/documentation/07-my-first-awesome.md.html#) : > Mod4+h, Mod4+l, Mod4+Shift+h and Mod4+Shift+l to resize windows. In which \ is synonymous with \ or the Windows button. But the and combinations do not resize the windows as expected, while and does do something. So I went into my Fedora host's Gnome settings and removed the =lock screen shortcut, and now the VM registers "Mod4+h, Mod4+l, Mod4+Shift+h and Mod4+Shift+l" correctly. Then, I created the lock screen short cut once again, and the VM is still able to register all the above operations. EDIT: After the reboot of the VM, the shortcuts don't work anymore. # Questions 1. Why did removing the host lock screen shortcut make it work? 2. How to make it so that shortcuts are only registered in the VM when my mouse is captured inside the VM? Thank you very much. # System Specs Host: Fedora 37 Silverblue, Gnome 43.2, Wayland VM: QEMU/KVM, virt-manager, archlinux, Awesome WM, X Server

I'm fairly new to Linux and finding the whole concept of desktop environments very distorted and full of noise and confusion with no real clarity... I'm trying to fully understand how every aspect of a desktop environment works, in order to build the perfect desktop environment for me out of everything. After a lot of research I think I'm finally beginning to understand things a bit better but I'd appreciate it if someone could let me know whether I'm on the right track with this diagram I've created. My understanding is that a desktop environment is built upon a window manager, which communicates directly with the display server (e.g. xorg) via (e.g. x11). So a Window Manager allows you have have various Windows placed n the screen via a GUI, but a full desktop environment comes with a lot more features. In other words a Window Manager is a very simple and much more basic version of a "Desktop" - in that it basically draws application windows, you have the right-click context menu and a couple of other things. From here the desktop environment builds on this with things such as panel manager, for the start bar (containing notifications, system tray icons, start menu etc), along with file managers (such as File Explorer in Windows), Settings Manager (Control Panel styled software) and other GUI applications. When you boot the PC, the first thing to happen (in terms of GUI and assuming something like Plymouth isn't installed) would be for the Display Manager to kick in, such as LightDM, which is actually more of a Login Manager, but is termed Display Manager. Once you login this starts the specified Session Manager, and the Session Manager is what is responsible for starting all these other components off. Technically there's nothing to stop me from mixing and matching various components, such as e.g. KDE Session Manager with XFCE Desktop, but I would need the extra KDE Dependencies to do this. Is all of this correct? If this is correct, then what does the xfdesktop package do for instance? Is this somehow pulling everything together in the DE, or is that the job of the Window Manager? Is there anything I'm missing from this list? It feels like there is something missing from my understanding or there is some other component I'm not yet aware of. Would really appreciate any responses. Thank you in advance.

The question is pretty straight forward. What I would have used under X [xdotool] obviously does not work moving forward, and no obvious new solutions have arisen given the relative new adoption of wayland. Solutions which require programming are acceptable.

I am writing a bash script to help new Linux users install Debian desktop environments easily but most of some packages rely on xorg. I think it might not work properly if no xorg is found on the target user machine. I really need to know if there is a Debian Linux distro without xorg and if any, what do they use? Github link

Been working on a project to create s simple digital display using the Raspberry pi 4 and buildroot. It is a simple application that interacts with the user through bluetooth and displays some information on the attached HDMI screen. All the debuging and programming work has been done. APP works fine However after detaching the mouse and Keyboard; and setting up weston to launch automatically, it fails. If i attach a keyboard and reboot, it works fine and weston is launched. I did some digging and applied the configuration option require-input=false , but same problem. Is there something i am missing ? Regards

For X11, I can see the display manager gdm3 (indirectly) launches a process named Xorg, which is the display server. However when using gnome on wayland, I do not see any children (or grandchildren) of the gdm3 process that could server as a display server. Did I miss something here? What shall be the name of that process?

I am trying to understand how different components of a Linux system interact with the services offered by a display server. Before complicating the question with Wayland-based display servers, let me first focus on X11: 1. I know that in order to implement a very basic GUI application for an X11-based system, it is theoretically possible to program against X11's C library binding and make use of low-level primitives such as XMapWindow or XDrawString to create a specific X client. Is this also the API that common GUI toolkits (such as GTK or Qt) make use of at the lowest level of their Linux implementation? Or do they draw their buttons and text fields in a different manner? 2. According to this post , one the job of a window manager is to control the placement of a window. How exactly does this happen? Is the display server aware of every single window that the window manager wants to be shown and, for each of these windows, expects the window manager to provide it with a position and the desired dimensions? And when the window gets resized, for instance, it is the window manager's duty to update these dimensions? 3. Considering the post from above again, another job of the window manager is to decorate the window, i.e., draw the borders and controls of the application. How does the window manager do this? Does it again use above-mentioned X11 primitives to draw objects around the actual X client? And if it does: How does it know which menus the developer of the X client programmed into its GUI? 4. If we are not only running a window manager, but a complete desktop environment such as GNOME: How are environment-specific components such as panels and window switchers drawn? Do they run as individual X clients? And finally, consider Wayland instead of X11. If I understand this article correctly, Wayland-based display servers are called “Wayland compositors” and integrate the functionality of a compositing window manager. Does this mean that a Wayland compositor such as Mutter is entirely incompatible with traditional window managers such as Compiz?

I really liked following diagram from Wikipedia which shows how different graphical components are connected to each other.: > As per my understanding, here 1) "graphical interface" is closely related to what we know as "Desktop Environment" as KDE, GNOME etc. are given examples. 2) X11 etc. are "windowing systems" 3) Xorg, Mutter etc. are listed as display servers and 4) Compiz etc. are window managers A normal users or those who are new to GNU/Linux would probably know only about Desktop Environment, not about rest of components. I want to know which of each components are running on my system. So, How do I know which Windowing system, which display server and which display server I am using on my GNU/Linux system? (*preferably through command line*)

I recently revived a hp 700/RX x-terminal and I wanted to try and set it up for fun but I don't know how to make a x-Linux server to connect to. I also think I need a bnc connector to connect it. I do have a bnc Ethernet card to link the computers. I just want to know what Linux distro and what version I need how how to set it up. I found this on Wikipedia https://en.wikipedia.org/wiki/X_terminal

What is expected from the program to be called a display server? In other words what, for example, X11 and Wayland have in common? Is display server has the same meaning as windowing system? Atleast on wikipedia both X11 and Wayland are listed in both article. These articles on wikipedia are unclear for me.

In https://en.wikipedia.org/wiki/Display_server , - does "graphical interface" mean clients of display server? - shouldn't "user" interact with "hardware" instead of "graphical interface"? If not, how does a user interact directly with "graphical interface"? Thank.

For the past few days I've been reading discussions about X.Org vs Mir vs Wayland and the way they differ from each other. I've read the following at Wikipedia: > A display server or window server is a program whose primary task is > to coordinate the input and output of its clients to and from the rest > of the operating system, the hardware, and each other. The display > server communicates with its clients over the display server protocol, > a communications protocol, which can be network-transparent or simply > network-capable. What is the server and the client on this context? Why was the rendering process made at the server before and now the approach is to let the client worry about rendering? What was the role of the client at the old days when server did the rendering, and what is the role of the server now that the client does the rendering?

I have recently set up Xvfb on Centos 7 machine. It is working absolutely fine. Only problem is that if I quit putty session (remote access) it would keep running Xvfb in background but display will be gone. So next time when I take remote access via putty first I have to type export DISPLAY=:99 again, then I start my tests. How can I make it permanent? I don't see solution to my problem in this thread https://unix.stackexchange.com/questions/14594/how-to-make-exported-shell-variables-permanent **Update:** .profile contents: export M3_HOME=/home/aditi.a/apache-maven-3.5.4/bin export PATH=$PATH:$M3_HOME export JMETER_HOME=/home/aditi.a/apache-jmeter-5.0/bin export PATH=$PATH:$JMETER_HOME export JAVA_HOME=/usr/java/jdk1.8.0_192-amd64 export PATH=$PATH:$HOME/bin:$JAVA_HOME/bin export DISPLAY=:99 **echo variables output:** $ echo $JAVA_HOME /usr/java/jdk1.8.0_192-amd64 $ echo $M3_HOME /home/adit.a/apache-maven-3.5.4/bin $ echo $DISPLAY $ *which shell I am running* $ ps -p $$ PID TTY TIME CMD 30678 pts/14 00:00:00 sh

I ran the command below on [secureCRT](https://www.vandyke.com/download/securecrt/download.html) ssh client: $ DISPLAY=abc.xyz.com:0 ; export DISPLAY $ /bin/xhost +abc.xyz.com But it output this error: /bin/xhost: unable to open display "abc.xyz.com" # cat /etc/system-release Red Hat Enterprise Linux Server release 7.5 (Maipo) # whoami root How to troubleshoot this error?

I am researching differences between xorg and wayland and am being confused by one thing. X11 runs with the Xorg server and a separate window manager for compositing, and Wayland uses display servers that also handle compositing. What confuses me is that it sounds as if all Wayland display servers are window managers, whereas with Xorg the window manager is separate from the display manager. With Wayland do the window managers take the place of the display server as well? It’s confusing to think about. I guess what I’m wondering is under Wayland, are the display servers window managers or are the window managers display servers, or both?

we have an embedded PC with an Linux OS which seems to be an Debian/Ubuntu derivate with RT-Preempt patch. At this pc we attached a display (7" 1024x600 170 DPI) via DVI. We are need to run the output in portrait and only basic X11 (not a complete graphical shell with window manager and further). Regarding the CLI-Mode it is only a minor change in */etc/default/grub*. For X11 I don't get it work correctly. Using startx leads to an smaller terminal than full size in landscape mode. So I try: xrandr --output HDMI0 --rotate left --mode 1028x600 -- dpi 170 Now the orientation is correct, but the terminal area is only a third of the display. And running xrandr tells me Screen 0: minimum 320 x 200, current 800 x 600, maximum 8192 x 8192. How to set up the display correctly, so that: - X starts in portrait mode - on the correct resolution and size - the configuration affects all users - with the minimal (installation) effort Thanks ---------- ### Using */etc/X11/xorg.conf* Thanks for your reply. I try the way using */etc/X11/xorg.conf* (the configuration file doesn't exist before) with the following content: # modelines generated by using: http://xtiming.sourceforge.net/cgi-bin/xtiming.pl Section "Monitor" Identifier "IntegratedDisplay0" VendorName "LITEMAX" ModelName "DLH0765-ENN-G02" Option "Rotate" "left" Modeline "1024x600" 48.11 1024 1056 1232 1264 600 612 618 631 EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "IntegratedDisplay0" SubSection "Display" Viewport 0 0 Depth 24 Modes "1024x600" EndSubSection EndSection Because the resolution seems to be unusual I define a modeline. Somewhere I found the information that xrandr can only set to given modes. After running startx from one user the output is rotated correctly but there are two things left: 1. Then I go around with the mouse pointer (cross) it can be determined that a half cross is visible on the upper, the left, the lower and the lower half of the right border. On the upper right border the mouse seems to have more 'size' to the right. 1. That is the output of xrandr: Screen 0: minimum 320 x 200, current 800 x 1024, maximum 8192 x 8192 HDMI1 connected 600x1024+0+0 left (normal left inverted right x axis y axis) 153mm x 90mm 1024x600 60.01*+ 60.32 800x600 60.32 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00 800x600 60.32* 56.25 848x480 60.00 640x480 59.94 This looks like as the display is using the wrong resolution. How can I correct this issue? Beside: The connection is an DVI and not a HDMI as shown by xrandr.