KDE Moves To GitLab-Based CI, Lands More Plasma Wayland Fixes

[mdedetrich]

No Bugzilla is fine. I'm old, I'm used to it, and I like it. Ugly, but effective.
I assume using gitlab issues can work well for them too.

Compared to modern ticketing solutions like the one found in Gitlab (which KDE is using), bugzilla is extremely primitive

[ireri]

You mean specifically the Kwin wayland compositor right? Otherwise, your post does not make any sense.

Let's be honest, Wayland is a shitshow everywhere, even still in Gnome at times.

[bple2137]

I wonder what's better for them about Gitlab CI instead of Jenkins?

Probably same as always. Don't get me wrong, I worked with Jenkins for quite a bit and I like a lot of its concepts, but Gitlab CI can do a lot of stuff (not as many as Jenkins that's for sure), but ends up being a whole lot clearer and easy to maintain solution in many scenarios.

People in the devOps area also complain about the Groovy language syntax. In Gitlab CI it's usually simple YAML file that's easy to write or correct by person without any previous experience with the tool. I was surprised how few lines of code I needed in order to get what I wanted. There's the price of elasticity though.

[birdie]

It is incredible how much of a shitshow Wayland is this many years later. X will never fully go away at this rate.

I could have said something like that but I'm afraid of getting a ban for speaking against The Bolshevik, sorry Phoronix Wayland lovers, Party.

Nah, X will go away, only a tad later than Wayland lovers would have wanted to. I guess by year 2035 most distros will come with Wayland by default only by that time I would have been happy to replace Linux with something based on Zircon/Fuchsia. I'm too tired of Linux.

[gfunk]

Let's be honest, Wayland is a shitshow everywhere, even still in Gnome at times.

I think you mean Wayland works well on Gnome and is a shitshow everywhere else...

I'm using Wayland on Pop_OS and I cant find any bugs except for a Thunderbird one

[Frenzie]

You mean specifically the Kwin wayland compositor right? Otherwise, your post does not make any sense.

Given that Gnome Wayland is guaranteed to randomly freeze on all of my systems, regardless whether it's on Intel, AMD or Nvidia, Debian, Ubuntu, Fedora, …, KWin's occasional half-crash of some parts of Plasma and being bad at placing windows is hardly a shitshow in comparison, imho. Maybe that Sway thing is totally great Wayland-wise but I don't like tiling window managers.

[Termy]

No Bugzilla is fine. I'm old, I'm used to it, and I like it. Ugly, but effective.
I assume using gitlab issues can work well for them too.

Its fine for reporting and all, but the search for existing bug reports is a big nuisance in my experience - so i'd welcome a more modern issue management, too ^^

[birdie]

I think you mean Wayland works well on Gnome and is a shitshow everywhere else...

I'm using Wayland on Pop_OS and I cant find any bugs except for a Thunderbird one

So there are still bugs? OMG, I thought Gnome worked perfectly under Wayland.

Given that Gnome Wayland is guaranteed to randomly freeze on all of my systems, regardless whether it's on Intel, AMD or Nvidia, Debian, Ubuntu, Fedora, …, KWin's occasional half-crash of some parts of Plasma and being bad at placing windows is hardly a shitshow in comparison, imho. Maybe that Sway thing is totally great Wayland-wise but I don't like tiling window managers.

What's your distro? Have you tried e.g. Fedora 35?

[bug77]

KDE, please move your bug reporting away from Bugzilla. That's the biggest hurdle in stopping people from reporting bugs. For bugs to be fixed, we need to make the process of reporting them super easy. Bugzilla, IMO is unwelcoming.

I'd be fine if they moved to a text-based solution. As long as bugs reported by several people wouldn't go unacknowledged/unable to reproduce for half a year or more. Fat chance of that happening.

[skeevy420]

This sounds like firefox runs under XWayland, which has no support for hidpi/upscaling. I think your missing the relevant environment variables. Firefox shows crisp fonts under my sway session. So this is how I do it: I long gave up on SDDM and use a systemd unit to start sway:

This pulls in various .env files the relevant is wayland.env:

CLUTTER_BACKEND="wayland"
GDK_BACKEND="wayland"
QT_QPA_PLATFORM="wayland"
QT_WAYLAND_DISABLE_WINDOWDECORATION=1
#SDL_VIDEODRIVER="wayland"
XDG_SESSION_TYPE="wayland"

I think the first to lines should force firefox to use native wayland and in turn correctly upscale.
Just try it in a terminal and on success write a little shell script or .destop file
I hope this helps.

That did the trick. Thanks.

I also noticed during all of this that the mouse cursor settings either don't scale on X11 or the settings trip up when going between X11 and Wayland since I always have to enlarge the cursor to 48 on X and shrink it back to 24 on W when using the same scaling setting of 200%.