[SOLVED] Is it just me or doesn't Wayland work under Gentoo?

[fusion809]

I love Gentoo but I must admit I've noticed that Wayland isn't so well-functioning under it, compared to how well it works under say Arch Linux (when we control for hardware, that is). To be precise whenever I try to start a Wayland session whether it be Sway or Plasma on Wayland using SDDM, it immediately crashes. On Arch Linux this issue does not occur and all Wayland sessions launch fine at least and with the exception of Plasma on Wayland they run flawlessly. Is this a bug I should report at Gentoo Bugzilla? I ask because frankly it's not like as though I have an awful lot of information to report to them (in order to help them fix this bug), unless you's can tell me about some logs I can attach that I'm not aware of. My graphics cards, if relevant, are NVIDIA 740M and Intel integrated graphics 4th generation.
_________________
Open-source advocate with an inquisitive disposition

[asturm]

Do you use systemd or openrc?

[fusion809]

systemd, which I would have thought would have worked better with Wayland if anything given the fact that the distros with the best Wayland support, Arch Linux and Fedora, both use systemd.
_________________
Open-source advocate with an inquisitive disposition

[asturm]

Then nothing speaks against Wayland sessions working flawlessly on Gentoo, you'll have to compare your Arch setup with your Gentoo one, most likely graphics stack. On openrc I am using elogind to enter Plasma Wayland sessions working just as fine as with systemd.

[fusion809]

Are you using dual NVIDIA and Intel graphics cards like me? If not well maybe it could explain it as I heard from a guy in the #gentoo channel a few weeks ago that Sway always crashed on startup for him and he had dual NVIDIA and Intel graphics cards.
_________________
Open-source advocate with an inquisitive disposition

[fusion809]

I use both without a problem though when launching runescape-launcher (games-rpg/runescape-launcher) with Optirun though so I am doubtful it's due to a problem setup.
_________________
Open-source advocate with an inquisitive disposition

[asturm]

I don't go anywhere near Nvidia and it has served me well. Depending on nvidia-drivers would make it impossible for me to test Plasma Wayland sessions. Works with Intel and AMD.

[fusion809]

Being able to run runescape-launcher with Optirun (using both graphics cards NVIDIA and Intel) has something to do with graphics cards and graphics cards, I was speculating (and you seem to have confirmed), may have something to do with the Wayland crashes. If I could launch runescape-launcher with NVIDIA and Intel cards it would suggest that the way I've set up my Gentoo system, with respect to hardware support, wasn't the problem and you were suggesting earlier my configuration (or at least that's what I thought you meant by graphics stack, although I suppose you could have been referring to hardware) might be the problem. Has that cleared it up? Not asking sarcastically but I would like to think that I've helped ya see why I mentioned it.
_________________
Open-source advocate with an inquisitive disposition

[asturm]

It's two entirely different things, unless runescape-launcher also starts a Wayland session you do not gain any information from it.

[fusion809]

It works fine on the same hardware under Arch Linux and Fedora though, so it does seem to be specific to Gentoo.
_________________
Open-source advocate with an inquisitive disposition

[asturm]

It works for other people, so it's specific to your setup. :p The only thing you know via runescape-launcher is that Optirun seems to work, that's good, but Wayland is a different matter.

No, really, there's probably something USE flag related that is not working on your Gentoo setup.

[fusion809]

Well I've got these global USE flags and VIDEO_CARDS variables (in /etc/portage/make.conf, of course):

[fusion809]

Well I'll be I re-emerged efl with the wayland USE flag enabled and now Plasma on Wayland launches fine, although Sway is still crashing. I hadn't tried Plasma on Wayland for like a week though so maybe it was just an update that fixed it. Does this mean I should report this as a bug in Sway? How do I get logs for it? I know the Bugzilla guide tells ya how to get logs for a program you can launch from the command-line but to my understanding this cannot be done for Sway.
_________________
Open-source advocate with an inquisitive disposition

[fusion809]

Nvm the Arch Wiki taught me I could launch it that way didn't realize compositors could be.
_________________
Open-source advocate with an inquisitive disposition

[fusion809]

Reported at https://bugs.gentoo.org/show_bug.cgi?id=622808. Marking as SOLVED as now it's up to the devs. Funny thing is that it seems like a very trivial issue with the package. It seems like they created a USE flag (swaylock) for an 'option' that is actually not an option as without it Sway crashes.
_________________
Open-source advocate with an inquisitive disposition

[asturm]

[fusion809]

Ya that's why I posited an alternative explanation, namely that maybe a fix had been pushed for the Plasma on Wayland issue. Sway seems to be failing for a trivial reason, which I mentioned in my last comment, must admit I was surprised that it wasn't picked up earlier, must mean Sway is under-used on Gentoo or everyone uses the USE flags that by-pass this issue.
_________________
Open-source advocate with an inquisitive disposition

[asturm]