FS#46762 - [gnome-shell] GDM/Wayland - Clutter-CRITICAL **: Unable to initalize Clutter

Attached to Project: Arch Linux
Opened by Christian (Darius) - Saturday, 17 October 2015, 13:03 GMT
Last edited by Jan de Groot (JGC) - Monday, 08 May 2017, 12:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
System stucks at starting graphical target with no loginscreen. Disabling Wayland in /etc/gdm/custom.conf makes the boot run through. System is up to date.


Additional info:
* package version(s)
* config and/or log files etc.

GDM 3.18.0
Linux N53J 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3 18:52:50 CEST 2015 x86_64 GNU/Linux

Steps to reproduce:
Booting with wayland enable
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 08 May 2017, 12:32 GMT
Reason for closing:  Fixed
Comment by Christian (Darius) - Saturday, 17 October 2015, 13:12 GMT
Package is Extra not Core sorry... :/
Comment by Christian (saedelaere) - Sunday, 18 October 2015, 09:02 GMT
Exact same problem here. I want to add this worked when I first upgraded to GNOME 3.18. I think this might be related to recent gnome-shell 3.18.1 / gnome-session 3.18.1 updates, but I am not sure.

Additionally disabling wayland does start gdm but after I provide my login credentials I just see the grey background of gdm and nothing happens. Pressing ESC once finally loads the desktop. Also a new issue. This did work until yesterday.
Comment by Christian (Darius) - Monday, 19 October 2015, 18:07 GMT
gdm 3.18.0-1
gnome-shell 3.18.1-1
nvidia 355.11-3

lspci | grep VGA:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 425M] (rev a1)


Seems related to  FS#46769 . I skipped some updates so i m not sure on what version it worked. I didnt need to press ESC. It feelt like gdm took some time to start up, and stayed some seconds on a black screen with mouse. but on the other hand my other working machine with nvidia optimus has a ssd and that could be the reason for that feeling. And that said the nvidia optimus one wich starts intel graphic has no problem.

Not sure whether this is Arch related or should be comitted Upstream.
Comment by Sunny Wong (ArchDoctor_needed) - Monday, 19 October 2015, 19:18 GMT
Same problem here. The workaround with /etc/gdm/custom.conf worked, thanks.
I have updated everything.
Using:
* 01:00.0 VGA compatible controller: NVIDIA Corporation G84M [GeForce 8600M GT] (rev a1)
* Linux 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3 18:52:50 CEST 2015 x86_64 GNU/Linux

Here are some extracts from my journalctl:
Oct 19 20:50:26 <host> kernel: gnome-shell[900]: segfault at 7f4f1e3bd240 ip 00007f4f3689f0c9 sp 00007ffcb247dd40 error 7 in libX11.so.6.3.0[7f4f3685d000+13b000]
Oct 19 20:50:26 <host> gnome-session[775]: gnome-session-binary[775]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
Oct 19 20:50:26 <host> gnome-session-binary[775]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
Oct 19 20:50:26 <host> systemd-coredump[939]: Process 900 (gnome-shell) of user 120 dumped core.
Oct 19 20:50:27 <host> gnome-session-binary[775]: Unrecoverable failure in required component gnome-shell-wayland.desktop
Oct 19 20:50:27 <host> dhcpcd[551]: enp9s0: no IPv6 Routers available
Oct 19 20:50:27 <host> systemd-logind[564]: Removed session c1.
Oct 19 20:50:27 <host> gdm[580]: Child process -766 was already dead.
Oct 19 20:50:27 <host> systemd[1]: Stopping User Manager for UID 120...
Oct 19 20:50:27 <host> gdm[580]: Child process 625 was already dead.
Oct 19 20:50:27 <host> gdm[580]: Unable to kill session worker process
[...]
Oct 19 20:50:27 <host> systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
Oct 19 20:50:27 <host> systemd-logind[564]: Failed to start session scope session-c2.scope: Transaction is destructive. org.freedesktop.systemd1.TransactionIsDestructive
Oct 19 20:50:27 <host> gdm-launch-environment][947]: pam_systemd(gdm-launch-environment:session): Failed to create session: Resource deadlock avoided
[...]
Oct 19 20:54:20 <host> gdm[580]: GdmLocalDisplayFactory: Failed to issue method call: The connection is closed
Oct 19 20:54:20 <host> gdm[580]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Comment by Jan de Groot (JGC) - Saturday, 06 May 2017, 07:01 GMT
  • Field changed: Status (Assigned → Waiting on Response)
Is this still an issue? GNOME has seen 3 new major releases since this was reported, Nvidia supports Wayland now, so this should not be an issue anymore.
Comment by Sunny Wong (ArchDoctor_needed) - Monday, 08 May 2017, 10:46 GMT
This issue is successfully resolved for me.
I even revoked the workaround by again commenting #WaylandEnable=false. everything works fine.

Loading...