4

I updated Gnome to the newest version and I realized that wayland has been installed as the default window manager. I have many problems with it, so how do I go to back to X11?

I'm using Arch.

//EDIT

Problem solved. I just delete old x11 config and create new one :)

echo $XDG_SESSION_TYPE returns X11 :)

closed as off-topic by Philippos, Jeff Schaller, Archemar, Stephen Rauch, Satō Katsura Sep 7 '17 at 16:41

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Philippos, Jeff Schaller, Archemar, Stephen Rauch, Satō Katsura
If this question can be reworded to fit the rules in the help center, please edit the question.

  • You know these days you don't need a configuration file at all – Bigon Jan 10 '17 at 18:53
8

From an arch wiki Use Xorg backend

The Wayland backend is used by default and the Xorg backend is used only if the Wayland backend cannot be started. As the Wayland backend has been reported to cause problems for some users, use of the Xorg backend may be necessary.

To use the Xorg backend by default, edit the

 /etc/gdm/custom.conf file and uncomment the following line:

#WaylandEnable=false

I hope it is current.

  • Isn't that just forcing to use X11 for GDM and not the user session? – Bigon Jan 10 '17 at 9:51
  • I'm tired that and my GUI didn't run so I was force to back to comment that line – Rarez Jan 10 '17 at 10:06
1

In gdm, you should have a little gear bellow the field you are entering your password. There you should be able to select the X11 session

  • Yes Im able to choose beetwen Xorg and Wayland session problem is when Im choosing Xorg I have black mirror for 1-2 sec and then again back to field when you are entering your password – Rarez Jan 10 '17 at 9:57
-1

Here is output of:

journalctl -e -u gdm

sty 10 11:01:40 RarezPC gdm[348]: Child process -10757 was already dead.
sty 10 11:01:40 RarezPC gdm[348]: Child process -10776 was already dead.
sty 10 11:01:40 RarezPC gdm[348]: Child process 10761 was already dead.
sty 10 11:01:40 RarezPC gdm[348]: Unable to kill session worker process
sty 10 11:01:41 RarezPC gdm[348]: Child process -10816 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process 10796 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Unable to kill session worker process
sty 10 11:01:41 RarezPC gdm[348]: Child process -10835 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process 10821 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Unable to kill session worker process
sty 10 11:01:41 RarezPC gdm[348]: Child process -10854 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process -10854 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process -10873 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process 10858 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Unable to kill session worker process
sty 10 11:01:41 RarezPC gdm[348]: Child process -10892 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process -10892 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: GdmLaunchEnvironment: Unknown user gdm
sty 10 11:01:41 RarezPC gdm[348]: GLib-GObject: g_object_set: assertion 'G_IS_OBJECT (object)' failed
sty 10 11:01:41 RarezPC gdm[348]: Child process -10925 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Child process 10897 was already dead.
sty 10 11:01:41 RarezPC gdm[348]: Unable to kill session worker process
sty 10 11:02:12 RarezPC systemd[1]: Stopping GNOME Display Manager...
sty 10 11:02:13 RarezPC systemd[1]: Stopped GNOME Display Manager.
  • Now I have another problem :/ Failed to contact accountsservice, AccountsService: Failed to create accounts proxy: – Rarez Jan 10 '17 at 10:42

Not the answer you're looking for? Browse other questions tagged or ask your own question.