Introduction

This lesson is about Linux graphical desktops.

The main question is:

What are the major Linux desktop environments, and what technologies are commonly used to access graphical sessions locally or remotely?

What you should be able to do after this lesson:

Recognize major Linux desktop environments.
Understand the difference between a desktop environment and a remote desktop protocol.
Recognize XDMCP, VNC, Spice, and RDP.
Understand the basic role of a graphical session.

Big Idea: "Desktop" and "Remote Access" Are Different Questions

A desktop environment answers:

what does the graphical session look like?
how do menus, panels, windows, and settings behave?

A remote desktop protocol answers:

how do I reach that graphical session from somewhere else?

That is why LPIC groups both ideas together here.

Major Linux Desktop Environments

GNOME

Very common on enterprise and mainstream desktop Linux systems.

KDE Plasma

Known for a rich feature set and strong customization.

Xfce

Often chosen for simplicity and lower resource use.

Beginner rule:

you do not need to be an expert in each desktop
you do need to recognize the names and the idea of a graphical session

Session Components

A graphical desktop usually involves several layers:

display server
login/session start
window management
desktop environment tools

This explains why "desktop" is bigger than just "what wallpaper do I see?"

Remote Desktop Protocols to Recognize

XDMCP

Older X11-oriented remote display protocol.

VNC

Sends a desktop view over the network.

Spice

Common in virtualization environments.

RDP

Commonly associated with Microsoft systems, but Linux clients and servers can use it too.

Simple memory trick:

GNOME, KDE, Xfce = desktop environments
XDMCP, VNC, Spice, RDP = ways to reach a graphical session

Remote vs Local Session

Local session

You are physically on the machine or using its directly attached display.

Remote session

You are reaching the graphical environment over a network or virtualization channel.

That is why remote desktop protocols matter even for Linux desktop awareness.

Why This Matters for Admin Work

You may need to know:

what desktop the user is running
whether the problem is the desktop itself or the remote access method
whether a virtualization platform prefers VNC or Spice
whether a system is meant for local login only

Practice Step by Step

1) Separate desktops from protocols

Put these under desktop environments: GNOME, KDE Plasma, Xfce
Put these under remote access protocols: XDMCP, VNC, Spice, RDP

2) Think through a support question

A user says: "My GNOME desktop is slow over VNC."
Notice that this contains two layers: desktop environment = GNOME remote protocol = VNC
That helps you ask better troubleshooting questions.

Cheat Sheet

GNOME = major Linux desktop environment
KDE Plasma = major Linux desktop environment
Xfce = major Linux desktop environment
XDMCP = older remote X11 session protocol
VNC = remote desktop technology
Spice = remote graphics protocol often used in virtualization
RDP = remote desktop protocol also used from Linux
desktop environment = local session look and behavior
remote desktop protocol = how the session is reached remotely

106.2 Graphical Desktops