Systemd/wayland setup - currently no graphical login ...
I know they say rebooting doesn't fix anything (and it broke a load for me), but it does seem to (sometimes) fix "startplasma-wayland".
But typically, startplasma-wayland will bring up the big K, and then the screen goes black. Log in on a different vt, kill wayland, and I've got a page of error messages mostly about "can't load compositor" then "can't find compositor" etc etc. "Re-installing might fix the problem".
Run it again and it often works, or I get about four error messages. If it fails the second time, it tends to stay failed. I can't say "until I reboot", because SUSE kindly screwed me over yesterday morning - it upgraded the kernel, regenerated grub.cfg, and broke EVERYTHING - itself and gentoo ...
Once Wayland is running successfully, most applications seem fine, but Thunderbird keeps crashing with "broken pipe" or "lost compositor" or stuff like that.
I've also got X installed, but if I try and run that, it doesn't work either. BUT IT'S NOT (AFAICT) CRASHING. It just fires up, prints a bunch of information messages, and exits. Doesn't even give me a black screen! And if I look at the log file, again it's all information messages (apart from not being able to find fbdev or vesa which apparently is irrelevant because it's loading radeon fine afaict). The only oddity is it's reporting my logitech gaming mouse as a keyboard.
Is there a decent trouble-shooting guide for Wayland? The only one I found went on about DrKonqui and various dbus stuff. But if you don't have a running gui, you don't have DrKonqui? And I don't know, but dbus feels to me like it's also a gui thing ... (although I'm probably wrong there ...)
(What messed up my system this weekend was I booted into SUSE so I could snapshot my gentoo lv, and SUSE wanted to update. So I let it, it updated the kernel, and totally fucked up grub.cfg, to the extend I ended up in the rescue console editing it... Then once I managed to get back into gentoo, it was update world, compile kernel, generate new grub.cfg TO A DIFFERENT FILE, and edit the two files carefully together so I should have a working boot setup again. Word of warning - DON'T let grub-mkconfig loose on a boot partition shared between distros!)
Cheers, Wol
