Arch Linux

pentomasis

Member

Registered: 2019-10-17

Posts: 18

[SOLVED] Failed to start GNOME Shell on Wayland.

Hello everyone,
I just installed Arch on my laptop with an encrypted LVM and GNOME and so far I very much like what I see (Yes, I followed the Arch Wiki ). I do seem to have a problem when booting my laptop though. After decrypting my SSD there is a black screen with a blinking cursor for more then 30 secs. It always takes forever to show the desktop environment. I tried to investigate the reason and ran

 sudo journalctl -p 3 -xb 

This is the output:

 -- Logs begin at Mon 2019-10-14 01:12:43 CEST, end at Thu 2019-10-17 21:33:04 C>
Oct 17 21:30:21 archlnx kernel: do_IRQ: 1.55 No irq handler for vector
Oct 17 21:30:21 archlnx kernel: do_IRQ: 2.55 No irq handler for vector
Oct 17 21:30:21 archlnx kernel: do_IRQ: 3.55 No irq handler for vector
Oct 17 21:30:27 archlnx systemd[584]: Failed to start GNOME Shell on Wayland.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished with a failure.
-- 
-- The job identifier is 118 and the job result is failed.
Oct 17 21:30:29 archlnx systemd-backlight[646]: Failed to get backlight or LED >
Oct 17 21:30:29 archlnx systemd[1]: Failed to start Load/Save Screen Backlight >
-- Subject: A start job for unit systemd-backlight@backlight:acpi_video0.servic>
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-backlight@backlight:acpi_video0.service has fin>
-- 
-- The job identifier is 949 and the job result is failed.
Oct 17 21:30:29 archlnx systemd-backlight[647]: Failed to get backlight or LED >
Oct 17 21:30:29 archlnx systemd[1]: Failed to start Load/Save Screen Backlight >

Gnome is running and seems perfectly fine so I dont know how to get rid of that error.

I also tried adding a hook to avoid the backlight error. It did not work.

Does anybody know a solution to this GNOME error?
Thank you

Last edited by pentomasis (2019-10-19 13:27:29)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

This isn't an Installation issue, you have already installed Arch. It belongs in Newbie Corner.

Install and enable haveged.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,645

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Moving to Newbie Corner.

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Thank you for your fast response.
Following your advice I installed and enabled haveged but it did not change anything. Boot time is still slow and I still get errors about Gnome failing. Also according to the ArchWiki article about it, I have enough entropy and don't need it.
Do you have another recommendation?

loqs

Member

Registered: 2014-03-06

Posts: 17,372

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Post the journal for an affected boot without priority filtering or catalog messages.

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Okay, the journal is in the following pastebin:
https://pastebin.com/MyU0Vdnz

loqs

Member

Registered: 2014-03-06

Posts: 17,372

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Oct 18 21:38:28 archlnx gnome-shell[611]: Failed to create backend: No drm devices found
....
Oct 18 21:39:59 archlnx systemd[582]: gnome-session-manager@gnome-login.service: Failed with result 'timeout'.
Oct 18 21:39:59 archlnx systemd[582]: Stopped GNOME Session Manager (session: gnome-login).

Have you tried enabling early KMS start?

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

I have not tried it before but followed the guide to try it now. This broke the boot completly. I got stuck with a black screen showing the arch version before being able to decrypt my ssd. I booted with the usb I used for installing it and reverted the changes to mkinitcpio.conf. I successfully booted and after finishing this reply will give it another shot, just to make sure I did everything correctly.

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

I got the same result again

loqs

Member

Registered: 2014-03-06

Posts: 17,372

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

What is the system's GPU?

$ lspci | grep -e VGA -e 3D

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics]

I really appreciate your effort. Thank you

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Any other ideas about what is going on with my system?
I also know that my UEFI is not up to date. Unfortunately I cant update it without running Windows D:
Before installing Arch I was running Ubuntu and it booted a lot faster. After the boot the performance is comparable

loqs

Member

Registered: 2014-03-06

Posts: 17,372

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Another possibility GNOME_Wayland_session_not_available
as from the journal

Oct 18 21:40:01 archlnx /usr/lib/gdm-x-session[666]: (II) xfree86: Adding drm device (/dev/dri/card0)
Oct 18 21:40:01 archlnx /usr/lib/gdm-x-session[666]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
Oct 18 21:40:01 archlnx /usr/lib/gdm-x-session[666]: (II) xfree86: Adding drm device (/dev/dri/card1)
Oct 18 21:40:01 archlnx /usr/lib/gdm-x-session[666]: (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 12 paused 0

pentomasis

Member

Registered: 2019-10-17

Posts: 18

Re: [SOLVED] Failed to start GNOME Shell on Wayland.

Your reply gave me a hint towards the right direction! Thank you for that. I had the amdgpu driver installed on my Lenovo Z50-75 which apparently was wrong. I removed that package and installed

xf86-video-ati

Then I tried enabling the early KMS start with the module "radeon" and not "amdgpu" and now the boot is MUCH faster and the error about GNOME failing is gone. I still see the following message in my logs though:
"gkr-pam: unable to locate daemon control file"

Last edited by pentomasis (2019-10-19 13:26:58)