Seven Days with GNOME - day 7: the Wayland special!

2020/07/17 12:43 AM (UTC -5) | tildearrow

*sighs* finally... I'm at the end...

you can't even play on GNOME

all of a sudden the freaking thing will steal your gaming session and the activities thingy will pop out of nowhere.
like why if I am in a full-screen game?!

and what about this? who wants to play with an Activities bar on top!!!
like you can't even properly detect when the game is in full-screen?!

Wayland time!

you know what? let's test the Wayland session.
some people say it's better. some say it's not...

I personally have not tried Wayland, but...

first step, from GDM. set WaylandEnable to true and restart GDM...

...nope, still X11. now try doing it manually because honestly it's not gonna work via GDM...

"A connection to the bus cannot be made"? what?!
ok honestly I just used the manual instructions from the Arch Linux wiki and it doesn't work?!

oh maybe it is because I have two graphics cards! let's disable the Intel one...

"A connection to the bus cannot be made"

~$ glxinfo | grep OpenGL
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Radeon Vega Frontier Edition
OpenGL core profile version string: 4.6.13572 Core Profile Context FireGL
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.13572 Compatibility Profile Context FireGL
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: 4.6.13572 Compatibility Profile Context FireGL
OpenGL ES profile shading language version string: 4.60
OpenGL ES profile extensions

oh..................................................................................................................................... oops o-o
i forgot to disable the pro driver :<

let's do that.... ldconfig and boom, be gone...

restart GDM...

GNOME on Wayland

...and done! I am in the half-working Wayland session!

now why did you reset my DPI settings? wasn't this supposed to work out of the box? let's check it out...

HiDPI works! after setting the scale... wait I got to complain.
why in the world are the apply/cancel buttons AT THE TOP?! really?! like what?
are you serious? at the top?!
WHO PLACED IT THERE LIKE "oh the user reads from bottom to top"?!?!

couldn't they find a better place to put that button in? like who wants the button at the top! what if I have an errand and should leave? NO! I can't because the close button is gone!!!
who was the idiot who thought this was a good idea? seriously?...
and you sell this product to enterprise customers? (RHEL, SLES and Ubuntu)

how do you slip off like that?! HOW??!?!!?!
like explain! how is this even possible!
like look at the bottom... there is like so much air for you to put a button called "Apply"... but no, of course not :l
OR AT LEAST AT THE RIGHT SIDE OF THE NAME!!! much easier to find....

and this, is why I call GNOME a disaster. the desktop assumes the user is an idiot who reads from bottom to top.
it puzzles the people who can't find buttons easily, like my parents or this dumb classmate who asked me for help like 6 years ago on clicking a button. they have problems to find buttons when they are where one doesn't expect.
like not even macOS puts the button at the top, and if it has to (like the lock in admin-only areas), IT PUTS THE THING AT THE BOTTOM!!!!!!

whatever, it sorta works. now my mouse is crap.
*sighs* let's fix this garbage.

acceleration test

ugh. I see what is wrong now.


you. have. to. set. the. acceleration. to. -0.5.
YEAH. as if setting it to 0 would work.

who added this random offset of 0.5 to THE VALUE?!!?! like what were they thinking?!... :l
is it like you want to shove mouse acceleration down my throat?!

you know, I just don't have to deal with that. I do not want mouse acceleration. I play osu!, Xonotic and other games that REQUIRE me to have mouse acceleration off.
plus it messes with my memory, and doesn't allow me to move precisely.
like, really?!

and now what if I come back to X? do I have to set it again because you stubborn devs added that random offset to the factor?

let's try Firefox.......... they say it supports Wayland, or sort of does...

Firefox works. honestly I'm surprised, because when I tried it in KDE Plasma Wayland, it began to flicker and do random stuff...
how come it works here? does it detect GNOME and stop flickering?
that's not fair.

what about Chromium?


it works too, but it uses XWayland, due to the fact that Chromium doesn't support Wayland yet.

can I turn the monitor off or will the thing crash? hmmm...


yep, it works.
it feels that GNOME has the most complete Wayland implementation ever, but...

.....yeah, it's kinda cheating 'cuz they were the ones who invented Wayland after all!

OH WAIT WHAT WAS THAT! did you see that? Firefox just flickered when switching to it! I am not sure what I did, but it flickered.... if it gets worse I will put a screenshot up.....

can I record the screen? oh wait look.

GNOME Terminal

why is my cursor tiny all of a sudden? what did I do for you to change the size of my cursor?!

whatever, can I record the screen?

...yep. there's no cursor, so that means GNOME is using the hardware cursor. nice!
I do remember that in the past GNOME used a software cursor... but thankfully not anymore, which means less lag and stuff.

oh wait again what did I do?

ok, now tell me. how is gears NOT responding?! are you drunk or what?
can't you see?! the gears are spinning perfectly! what is wrong?!

why do you tell me that they are not responding when they are! how do you evaluate if an app is responding?
is your algorithm that crappy?! -_-

also, input is handled in the main thread. so this means if an animation is lagging, everything else lags too.
I can't believe you don't even know how to properly program a compositor...

I kinda have a feeling that this thing will collapse soon and hurl me back to the login screen...


you know what I hate? the fact that GNOME doesn't support SSD (server-side decorations), without any reason.
they just don't want to support it... like... why?
there are applications that are NOT willing to draw their own borders, like games. why do you want to force us to draw our own border?!

my app looks terrible on GNOME... not only it unwillingly scales the app, but also doesn't have a border.
but now tell me something.


how come you do support SSD for X11/XWayland apps?! couldn't you add SSD support to the rest based from this?!
this is just being stubborn... like I mean this is so dumb... can support SSD for X11 apps but not Wayland ones. heck, even KWin supports SSD... yeah, on Wayland...

this is why Wayland is a failure. forcing CSD on us.
yep. it's in the standard. not even Weston supports it (but does for X11 apps, again).

isn't this proof that the guys who made Wayland are the GNOME authors, and they made it for just GNOME?!
yes, it is, right?

is this why KDE is struggling at Wayland support? and Enlightenment's Wayland support is actually a hack (reverse XWayland, as in Wayland apps running on X)?
can you have mercy and care about the other desktop?... :<

let's try KDevelop on GNOME Wayland

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

ugh. yeah. let's try that.


it works after setting the style. however, the border is ugly and looks no better from the stock Qt lazy border.
aaaand the mouse cursor is bigger than usual.

this is the biggest problem with supporting Wayland. lack of SSD support.
this means lack of consistency, which means no way to have one UI look for all apps.
every app feels different, and even games because there is no border.

how many more years of ignorance before you finally implement SSD?!

even mpv is aware of this huge problem:

[vo/gpu/wayland] GNOME's wayland compositor is known to have many serious issues with mpv. Switch to GNOME's xorg session for the best experience.

I bet they don't even support hardware acceleration yet:

~/Videos$ mpv 2020-07-16-23-08-32-final.mkv
(+) Video --vid=1 (*) (hevc 3840x2160)
(+) Audio --aid=1 (*) (pcm_f32le 2ch 44100Hz)
[vo/gpu/wayland] GNOME's wayland compositor is known to have many serious issues with mpv. Switch to GNOME's xorg session for the best experience.
Using hardware decoding (vaapi).
AO: [pulse] 44100Hz stereo 2ch float
VO: [gpu] 3840x2160 vaapi[nv12]

wait what? oh nice!

at least I am glad that middle-click paste works... yeah, it uses the same clipboard as the normal copy shortcut, but it's better than nothing.

final thoughts

overall, after one week of using this, I can say...

it's f**king HORRIBLE!!!





...well, it's not as bad as I thought... but yeah, it was overall a pretty unpleasant experience...
I definitely have seen improvements, but the desktop is still not in shape.

I mean, it's still not as usable as KDE is....

...yeah 144Hz, now prove me wrong after this whole week of GNOME survival!!!