Dennis HilkLinux Fix LabDE

Desktop, X11 & Wayland

Xorg exits with no screens found

The final no-screens message summarizes an Xorg startup failure. Read the earlier device and configuration errors to identify the blocked step.

Editorial source review: Start with the evidenceShare this guide
On this page
  1. Symptoms & scope
  2. Possible causes
  3. Diagnose safely
  4. Evidence-guided next steps
  5. References & review
  6. Related problems

Symptoms & scope

  • The display manager returns to the greeter after choosing X11.
  • Xorg’s final fatal error says no screens found.

Relevant environment

Xorg session startup, not a native Wayland compositor. Logs may live under the user’s local share directory or /var/log.

Recognizable messages (synthetic examples)
[ 14.812] (EE) no screens found(EE)

The preceding errors matter; this final line does not distinguish driver, permissions or stale configuration.

Possible causes

These are possible explanations, not a confirmed diagnosis. Several independent faults can coexist.

  • A static Device/Screen configuration may select an unavailable driver or PCI device.
  • Earlier driver, device-access or connector errors may leave no usable screen.

Diagnose safely

Run one command at a time in the relevant session. Read the explanation first. Uppercase placeholders need your own values; tools and privileges vary by distribution. These commands are displayed here and never executed by the website.

Check 1

Replace with the current failed session’s log, often ~/.local/share/xorg/Xorg.0.log or /var/log/Xorg.0.log.

rg -n "\(EE\)|no screens found|No devices detected|LoadModule|Using config" /path/to/Xorg.0.log

Interpret the result: Read earlier errors and the used configuration path; the legend containing (EE) is not itself an error record. Old logs can describe a previous boot.

Check 2

Reads static overrides; missing xorg.conf is normal on automatically configured systems.

rg -n "Driver|BusID|Screen|Device|ServerLayout" /etc/X11/xorg.conf /etc/X11/xorg.conf.d

Interpret the result: Compare selected driver and BusID with the earlier log. A stale override is a hypothesis only when it affects the configuration Xorg actually loaded.

Evidence-guided next steps

Isolate a confirmed stale Xorg override

If the log proves a stale administrator-created Device/Screen fragment is loaded, back it up and move only that fragment outside Xorg’s configuration search paths. Retry an X11 login to let supported automatic device selection operate.

Precautions: Preserve input configuration and distribution-managed files. Save open work and keep a text console before retrying the graphical session.

Recovery / rollback: Move the saved fragment back to its original location and retry the prior session configuration.

Did this solution help you?

Share this solution#

Repair the specific earlier driver or device error

If an earlier line names a missing Xorg module or device, use the distribution’s matching driver package and seat/device-access setup for that exact failure. Inspect that subsystem’s documentation rather than treating no screens found as a driver recommendation.

Precautions: Do not mix proprietary and distribution driver stacks or grant everyone access to /dev/dri.

Recovery / rollback: Restore the saved driver/configuration snapshot or matching package set through the distribution’s recovery process.

Did this solution help you?

Share this solution#

References & review

This guide was prepared from primary project or distribution sources and reviewed on the date shown. This is an editorial source check, not evidence that a fix was reproduced on your hardware. Diagnostic log examples are synthetic fixtures. Version-dependent details must be checked against your installed release.