GNOME/GDM Login Loop after update (Radeon GPU) - Manual gnome-shell works, GDM/LightDM fails

Hi everyone,

I’m struggling with a persistent login issue on Manjaro (GNOME, Radeon GPU) after a recent system update. I’ve tried several troubleshooting steps, but I’m stuck in a “Login Loop” or a blank GDM screen.

The Problem:

  • GDM: Shows a gray screen with the top bar (clock/icons), but the login prompt never appears.
  • LightDM: (Installed for testing) Shows the login screen, but after entering credentials, it flashes black and returns to the login screen (Login Loop).
  • Interesting Fact: If I switch to TTY and run gnome-shell, the desktop environment starts and works correctly. However, running dbus-run-session gnome-shell fails with an error.

What I’ve Done So Far:

  1. Drivers/KMS: Verified Radeon (Mesa) drivers. Added amdgpu to MODULES in /etc/mkinitcpio.conf and ran mkinitcpio -P. No change.
  2. Sessions: Discovered that /usr/share/xsessions was missing. Reinstalled gnome-session, gnome-shell, and manually recreated session files.
  3. Config: Tested both WaylandEnable=false and true in /etc/gdm/custom.conf.
  4. Permissions: Checked ~/.Xauthority and ran chown -R $USER:$USER on my home directory.
  5. New User: Created a fresh test user – the same login loop occurs, so it’s not a local config issue in my home folder.
  6. Reinstalls: Reinstalled gdm, gnome-shell, and video-linux (via mhwd).

Current Status:

It seems like the graphics stack is fine, but there’s a breakdown in communication between the Display Manager and D-Bus/User Session. The system “lives,” but the session initialization fails.

System Info:

  • OS: Manjaro
  • DE: GNOME
  • GPU: Radeon (using open-source drivers)

Does anyone have insights into why dbus-run-session might be failing or why GDM/LightDM cannot hand over the session to GNOME even though the shell itself can run manually?

Any help would be greatly appreciated!

1 Like

Please provide your system information to allow others to better respond to your query:


[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:


Suggested inxi command (use either):

inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)

Command output should be presented as pre-formatted text in accordance with forum guidelines. :eyes:


Running inxi within a chroot environment

  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0

Your privacy is respected


[Mini-HowTo] Present code or command output

Note: Grave accent (or, backtick) characters are used. :eyes:

For inline code or to show a single command:

  • please follow this simple example: code here.

For multi-line command output:

  • place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
  • use the </> button in the Compose window to achieve the same result.

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.