worth switching to wayland?

[dmpogo]

[kj184050]

[Naib]

Chromium-based might be running in Xorg mode via xwayland (you can check using xkill for instance...)
You need to enable OZONE for chromium stuff and then it is smooth and fast
_________________
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;

[kj184050]

[Anon-E-moose]

Whoever is handling the ebuilds that are including xproto, is severely lacking in discernment,
as many of those packages do not need xproto, but the ebuilds pull them in whether needed or not.

Thus you either have a bunch of not needed libs on your system, or you learn to do what the ebuild devs are supposed to be doing and write an ebuild with PROPER dependencies.

Edit to add: as for the many other X libs, you would have to try and remove them to see what pulls them in.

Personally I have the X use flag off globally.
This is what is pulled in on my system

[kj184050]

I have only

[dmpogo]

[pjp]

[Anon-E-moose]

For those ebuilds in repos, I typically just copy the one ebuild I'm interested in, into my local repo, that way I don't have to keep any odd repos around.

Wayfire - stacking, able to turn off animations, etc.
Hyprland - dynamic tiling, able to turn off animations, etc
Labwc - stacking, no real animations, so nothing to turn off

Labwc has some rudimentary tiling being added
Hyprland has the ability to treat all windows as floating (stacking) or a combination with some workspaces floating, others tiling (global or per app)
Wayfire it's been too long since I've used it so not sure what the current state of it is.

All animation stuff no matter which compositor, should be able to be turned off with one or two keywords.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[mv]

[pjp]

I've done the copy an ebuild thing, but that seems like more work than using the repo. I've only automated creation of a ::gentoo squashfs image, not other repos. Someday I'll look into how to do that. Pulling the one-offs into one local repo might be nice, but I don't know how to determine dependencies that must also come from the non-gentoo:: repo without seeing a build failure. Anyway, that's not a big issue.

For now I'm mainly looking to familiarize myself with the wayland environment. I have sway installed, but haven't tried to do anything with it yet.

Since Wayfire is in ::gentoo, it can't hurt to see what it looks like. It does have a nice logo :). That requires wayland support for mesa and gtk+:3... I presume that won't break anything.

When I eventually update to GCC, I'll try hyrland. It's really the only one that I'm genuinely curious about. Maybe I'll do that sooner than later, after the next gcc-13 patch level is stabilized.
_________________
Quis separabit? Quo animo?

[pjp]

[dmpogo]

[Anon-E-moose]

Workspaces/desktops allow one to separate windows cleanly, which is why I don't care so much about tiling or stacking.

I have one workspace for each app type - web, mail, p2p, music, and one for general purpose.

Some of the compositors allow one to move the window so only part shows on screen,
ie a type virtual space, not scrollable but window is easily moved back and forth
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[pjp]

[kj184050]

This is a quick update from my side.

I gave up with Wayland for some time.
I installed Xorg, Gnome, etc.
And?
EVERYTHING is OK. Smooth playback, etc. No issues.
But, as I said, I don't give up so easily, especially when I have time.
I decided to install Hyprland on a different distro.
I chose NixOS.
It was my first time with this distro. It took me less than 20 min. to install Hyprland using a graphical install without a desktop and then putting Hyprland into config.
And?
Well, everything is working fine! Smooth playback, etc.
I started playing with settings to figure out why it is not working on Gentoo.
I managed to "solve" one mystery regarding a blank screen with 120Hz and no display manager.
On NixOS, I had gdm set up. This worked.
When I switched auto login with gdm, I had no screen after reboot.
But, when I set the monitor in hyprelnad.conf to preferred (60Hz) it started with the picture.
So, in Gentoo (I can't use gdm), I have to do something to recognise a signal other than 60Hz.

Any ideas?

[Anon-E-moose]

Have you tried greetd with one of the greeters? Or just a shell script (set vars and then run hyprland"

As far as gdm, which version both gentoo and nix,
have you tried using nix's gdm config file (wherever it is) under gentoo?
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[NeglectedRudderPug]

Personally, for me Wayland has offered a better experience in the grand scheme of things. I bounced in and out of Wayland over the years watching its progress and it finally feels ready, for my use case.

Installing Wayland resolved the following issues:
1) Multiple monitors at different refresh rates, allowing a 144Hz monitor to run at 144Hz while the other ran at 60Hz.
2) I eventually swapped that 60Hz monitor for a new 144Hz monitor, which led me to another problem: With Xorg, enabling automatic sleep/suspend the monitors would go to sleep (show the no signal warning) and immediately wake back up to my lock screen, it would repeatedly do this from the lock screen as the timer was called each time. With Wayland, both monitors go to sleep and only wake up when I move a mouse or hit the shift key[1].
3) Variable Refresh Rate (VRR). It worked on Xorg for single monitors. But multiple monitors? No VRR for you. With Wayland I have VRR working on both monitors, at the same time.

So, for me personally Wayland just offers me a much better experience overall. Even the one thing that's often seen as a "complaint" is that with Wayland another application cannot auto-type or read the user input into another application. I personally prefer that though.

I've only been using Wayland for about a year or so at this point. And like many of you, I was skeptical and hesitant to switch over. But for me, personally, it just works and it works well. Granted, it cannot share applications over the network and such, but I never used that anyway. If I need to control another computer over the network, I'll just use SSH, as I do with business servers, where display servers and graphical applications simply aren't installed. I've never actually needed to forward X11 over a network.

So, out of my ~19 years with Xorg and ~1 years with Wayland, it's been a pleasant ride!

With all that said - I do hope Xorg continues to live on, and I hope it continues to be maintained in some manner. Wayland certainly doesn't fit every use case, and for those cases a tried and tested alternative should continue to exist. Xorg is not a bad display server, and it does the job it is meant to do. It's just in some cases, Wayland is a better fit. But they both have a place and both should continue to be an option for users. Freedom of choice and ability to set things up as you want/need are very important.

I realize my view is a little controversial, but it is my view.

[1] Just an old habit from CLI, I don't know what's behind a switched off monitor, so I'd rather not hit a key which is likely to do or trigger something, such as enter.

[kj184050]

[kj184050]

OK. Log in with:

[Anon-E-moose]

If not set, you might look at these

[CooSee]

TLDR - did someone already said YES

i use the following mini patch (/etc/portage/patches/gui-wm/hyprland/hypr.patch) - using *.9999 ebuilds here, but it'll work with stable too.

[flexibeast]

[wanne32]

[kj184050]