You are not logged in.
So, today I installed a fresh arch, got things up and running with gnome, and wanted to try wayland. However, when I would try to log into wayland with my regular username, it would just throw me back into GDM. The weird thing is after I tried signing into wayland once, even if I changed back to a normal X session, my user could not log in. However, I could log in as root - and even log into a wayland session as root. Has anyone had anything similar happen?
I put the full systemd log on pastebin. The first mentions of GDM happen around like 1415. (Yes, it's really long- because I'm no expert and I have no idea what could help in solving why wayland wont start- so I just put it all in)
I couldn't find an xorg log in /var/log or in ~/.local/, so I figured a systemd log would have to do.
Offline
Do you have the xorg-server-xwayland package installed?
Jin, Jîyan, Azadî
Offline
yeah, xwayland was the first thing I installed after installing xorg and my video drivers. To be safe, I even reinstalled it, and gnome, after I got gnome up and running the first time
Edit: while taking a nice long shower, it came to me- I bet the reason I can't get wayland running is because I am using the proprietary nvidia driver. I can't CONFIRM if this is the case, but I believe I read somewhere that the Nvidia blob isnt wayland ready yet- and I'd have to use noveau (and who wants to use that)
Last edited by tonykuroi (2015-02-06 05:32:53)
Offline
Yup.
Currently Wayland will only work on systems utilizing KMS.
https://wiki.archlinux.org/index.php/Wa … quirements
The proprietary NVIDIA and AMD Catalyst drivers do not use the open driver stack. In order to use KMS you should replace them with open source drivers.
Jin, Jîyan, Azadî
Offline
I don't know if you have solved your problem.But I have just met a similar problem and I think my experience might be helpful.
I reinstalled arch too and I could log into gnome only as root. I found it was because my user folder belongs to root ( I have moved my user folder as root ) and gnome doesn't have access to it.
My problem was solved with a chown command.
sudo chown -R myname:mygroup /home/mynameHope this will help.
Offline