This document discusses the Lumina desktop environment and how it challenges desktop orthodoxy. It begins by defining what a desktop is and how desktops are typically assembled. It then explains how Lumina 2 differs from other desktops by being a single process, using a formalized API for interactions rather than dbus, and being OS-agnostic rather than Linux-centric. The document concludes by discussing the crossroads facing open-source desktop developers and how Lumina is forging ahead with goals of portability, simplicity and standardization.

1. Lumina Rising:Lumina Rising:
Challenging Desktop OrthodoxyChallenging Desktop Orthodoxy
Ken Moore
<ken@ixsystems.com>
Ohio Linux Fest
Columbus, OH
September 29-30

2. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 2/17
Key QuestionsKey Questions
●
What is a desktop?
●
How is a desktop assembled?
●
How does a desktop integrate with the
operating system?
●
How is Lumina 2 any different?

3. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 3/17
What is a desktop?What is a desktop?
Common Answers:Common Answers:
●
A complete graphical system with a collection of
various utilities for common tasks. Examples:
KDE, GNOME, and XFCE.
●
An interface with application shortcuts and
manages graphical windows. Examples: Plasma,
Lumina, and WM + dock.
●
Only the window manager.

4. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 4/17
What is a desktop?What is a desktop?
Proposed Answer:Proposed Answer:
●
A graphical interface to an operating system
which supports industry standards for
application interactions and controls.
●
Examples:
●
Window Management: ICCCM and EWMH
●
Application Registration: XDG desktop menu and entry specs
●
Theming Specs: Icons, cursors, and color schemes (debatable)

5. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 5/17
How is a desktop assembled?How is a desktop assembled?
●
As time passes, the base desktop grows:
Package
Manager
WM
PanelsX11
Wallpaper
+ Icons
Screensaver
Screen Lock
Clipboard
Keychain
Session
Manager
Application
Launcher
File
Manager
Service
Manager
Device
Manager
Network
Manager
File
Sharing

6. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 6/17
How is a desktop assembled?How is a desktop assembled?
●
As time passes, the base desktop grows:
Package
Manager
WM
PanelsX11
Wallpaper
+ Icons
Screensaver
Screen Lock
Clipboard
Keychain
Session
Manager
Application
Launcher
File
Manager
Service
Manager
Device
Manager
Network
Manager
File
Sharing
Desktop Session
Application
Interfaces
Operating System
Control

7. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 7/17
How is a desktop assembled?How is a desktop assembled?
●
As time passes, the base desktop grows:
Package
Manager
WM
PanelsX11
Wallpaper
+ Icons
Screensaver
Screen Lock
Clipboard
Keychain
Session
Manager
Application
Launcher
File
Manager
Service
Manager
Device
Manager
Network
Manager
File
Sharing
Desktop Session
Application
Interfaces
Operating System
Control
Where is the operating system?
When does the desktop
become the OS?

8. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 8/17
How does a desktop integrate withHow does a desktop integrate with
the operating system?the operating system?
●
The OS provides a
“system console”
●
Keyboard Only
●
Users/Groups
●
Networking
●
Services
●
Filesystems
●
Shells
●
Hardware drivers
●
Standard C libraries
●
The desktop provides a
“graphical console”
●
Keyboard optional
●
Multi-user
●
Multi-application
●
Visualization of the OS
●
X11/Wayland libraries

9. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 9/17
How does a desktop tie into theHow does a desktop tie into the
operating system?operating system?
●
Recent trends in OS “intrusion” by desktops
●
Filesystem interference: GVFS and inotify
●
Bypass user restrictions: policykit and dbus
●
Bypass removable device management: hald, automount, and
autorun
●
Bypass shared network protocols using alternate libraries,
tools, or versions
●
Bypass hardware management: upower
●
Desktops try to enforce standardized OS
interactions, but fail. Desktops need an API!

10. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 10/17
How is Lumina Different?How is Lumina Different?
●
Other desktops
●
KDE/Plasma, GNOME and
derivatives
●
The “all-in-one” approach
●
Lots of dependencies
●
XFCE, LXQT, and Lumina 1
●
More modular and
independent from applications
●
Primarily just the “interface”
●
Still require several runtime
processes
●
Lumina 2
●
Interface only
●
No OS services required,
modular OS interaction
framework
●
Requires Qt5/X11 libraries
only
●
Completely independent
from applications
What is the desktop?

11. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 11/17
How is Lumina Different?How is Lumina Different?
What is the desktop?

12. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 12/17
How is Lumina Different?How is Lumina Different?
●
Other desktops
●
Lots of binaries/processes
●
Uses dbus as IPC “glue”
●
Moving toward “Apps-as-
services”
●
Highly fragmented core,
desktop-dependent extra
applications
●
Lumina 2
●
One binary/process
●
Formalized JSON API
●
Transient applications
●
Unified core, independent
extra applications
How is the desktop assembled?

13. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 13/17
How is Lumina Different?How is Lumina Different?
How is the desktop assembled?

14. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 14/17
How is Lumina Different?How is Lumina Different?
●
Other desktops
●
Linux-centric. Backend
services/tools must be
ported to a non-Linux OS
first.
●
Attempt to “control” OS
capabilities. The desktop is
dominant.
●
Provide a multitude of
utilities for OS tasks
●
Lumina 2 is:
●
OS-agnostic. Optional
internal mapping for OS
interactions.
●
An “interface” for any OS
capabilities. The OS is
dominant.
●
Minimal. OS control utilities
are installed by the OS.
Desktop and OS Interactions

15. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 15/17
How is Lumina Different?How is Lumina Different?
Desktop and OS Interactions

16. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 16/17
ConclusionsConclusions
●
Open-source desktop developers are at a
crossroads. Do we follow the example of
Windows and become a central component of a
single operating system? Or, do we create and
use operating standards for desktop/OS
interaction?
●
The Lumina project is forging ahead with goals
of portability, simplicity, and standardization.

17. September 29-30, 2017
Lumina Rising: Challenging Desktop Orthodoxy
Page 17/17
Questions?
Slides Available at:
https://www.slideshare.net/beanpole135