KDE's kstart5 Now Works On Wayland, No More HiDPI Screen Flickering At Start-Up

[Azrael5]

Well I got it working with all my machines so far, but I'm using Arch Linux, so can't speak for outdated packages. The only system that doesn't work at the moment is my Ryzen 3 2200G, it worked with I believe an older Mesa, but stopped some months ago.

I'm using Kde Neon provided by the latest PLASMA software. Nvidia card and nvidia drivers.

[betam4x]

KDE under Wayland won’t be useable for me until fractional scaling is implemented. Until then I will stick with KDE running on X

[ngraham]

ngraham Where exactly is the kdesrc-build bug tracker located? I didn't see an "issues" section on github. Figured here was as good of place as any to ask...

For the past two days I've been trying to get it to build on my Manjaro box, never getting past QT, and had to update the QT version to 5.12 in qt5-build-include. Currently on -- Building kxmlgui from frameworks (31/363)

Just tell it not to build Qt; it's not needed if you're using an up-to-date version. See https://community.kde.org/Get_Involv...p_kdesrc-build and read the NOTE section.

This is something kdesrc-build should definitely be smart enough to figure out by itself, for which I've filed https://invent.kde.org/kde/kdesrc-build/issues/31.

[R41N3R]

KDE under Wayland won’t be useable for me until fractional scaling is implemented. Until then I will stick with KDE running on X

I have several 4K displays. Scaling of 2x works only ok on my 13,3 inch notebook, but on the desktop with 28 inch everything looks way to big, but with disabled scaling and a higher dpi it works fine for me. Only issue are Gtk applications not respecting the dpi. Fractional scaling on Wayland is highly needed.

[skeevy420]

Just tell it not to build Qt; it's not needed if you're using an up-to-date version. See https://community.kde.org/Get_Involv...p_kdesrc-build and read the NOTE section.

This is something kdesrc-build should definitely be smart enough to figure out by itself, for which I've filed https://invent.kde.org/kde/kdesrc-build/issues/31.

Don't take this the wrong way, but I know that. I did read the documentation. For me, RTFM is always step 1. That said, some parts of it still reference KDE4 and haven't been updated in over 5 years. It really made me notice how much y'all need help with documentation.

I completely agree with your new users getting involved comments -- kdesrc-build isn't the most intuitive tool to use, reading the error logs to figure out missing packages simply sucks, and I completely get how it can be discouraging for people to want to get involved when they follow the steps and it doesn't "just work".

Building QT5 is more about trying to do the entire, complete, kf5-qt5 build process from start to finish with as much as possible to make sure I have everything necessary for a working build environment for KDE development as well as just trying to use the tool and get my head wrapped around how it wants to do things.

I intentionally skipped the easy way to document my failures to hopefully make it easier for others in the future. Y'all (KDE Developers) have all your ducks in a row and some random person on a random distribution, like myself, probably won't. After reading your new user comments, suffering through it seems like the right thing to do even if it isn't the most encouraged method to do.

Once I figured out what I needed to add to my .kdesrc-buildrc to use a newer version of QT, all was well in regards to that.

So far I've found these issues:

if using "gcc=9.1.0" then "qt5<=5.12" is needed
qt5=5.13 has a license choice that breaks kdesrc-build during the QT5 configure

ruby-test-unit  # needed for Dolphin;  Arch/Manjaro missing dependency
ruby-sass   # needed for breeze-gtk;  Arch/Manjaro missing dependency
qt5-networkauth # needed for kdepim-runtime;  Arch/Manjaro missing dependency

Is bugs.kde.org the preferred place to post issues? Between the different repositories & places with "Issues" tabs and the various KDE sites, I'm just not 100% positive where the preferred place would be.

[ngraham]

Thanks, I'm glad the documentation is at least okay. kdesrc-build only builds Qt from source to support old distros that ship old versions of Qt which are too old to build modern versions of KDE software. If your distro provides 5.11 or newer, you really don't gain anything by building Qt from source too (except a big headache, as you're seeing . It really is not supposed to even try for distros like yours that ship a nice new Qt. This is what https://invent.kde.org/kde/kdesrc-build/issues/31 is all about.

As for where to report bugs, in general it's https://bugs.kde.org. However KDE is in the middle of transitioning to use GitLab for infrastructure, and kdesrc-build is one of the projects that has already migrated there as a sort of vanguard, testing the waters. As a part of this, the kdesrc-build developers decided to use GitLab issues (https://invent.kde.org/kde/kdesrc-build/issues) instead of Bugzilla, but this hasn't been formally coordinated, and the old kdesrc-build Bugzilla page is still open for bugs. This is an ongoing issue we're working on creating a formal recommendation about, but for now go ahead and report your issues on https://invent.kde.org/kde/kdesrc-build/issues.

Thanks again!

[stingray454]

Looks like no one is working on this?

https://bugs.kde.org/show_bug.cgi?id=387313

https://phabricator.kde.org/T10530

It's been more than half a year since last activity.

Also, are there any plans to implement drawing tablets support in KWin Wayland session (Wacom)?

I check in on that bug from time to time (every few weeks) and I agree - it's really strange that such a big bug is not getting any attention. Hope to see it fixed soon.

[MadeUpName]

I love my KDE desktops and I am very grateful to the devs. But KDE on Wayland is years from being ready for prime time. With RH getting ready to stop support for X, if no one else steps up then I suspect that will be the beginning of the end for KDE. That is a shame.

[skeevy420]

Thanks, I'm glad the documentation is at least okay. kdesrc-build only builds Qt from source to support old distros that ship old versions of Qt which are too old to build modern versions of KDE software. If your distro provides 5.11 or newer, you really don't gain anything by building Qt from source too (except a big headache, as you're seeing . It really is not supposed to even try for distros like yours that ship a nice new Qt. This is what https://invent.kde.org/kde/kdesrc-build/issues/31 is all about.

As for where to report bugs, in general it's https://bugs.kde.org. However KDE is in the middle of transitioning to use GitLab for infrastructure, and kdesrc-build is one of the projects that has already migrated there as a sort of vanguard, testing the waters. As a part of this, the kdesrc-build developers decided to use GitLab issues (https://invent.kde.org/kde/kdesrc-build/issues) instead of Bugzilla, but this hasn't been formally coordinated, and the old kdesrc-build Bugzilla page is still open for bugs. This is an ongoing issue we're working on creating a formal recommendation about, but for now go ahead and report your issues on https://invent.kde.org/kde/kdesrc-build/issues.

Thanks again!

Building QT5 isn't so bad, granted I have 16 cores and 48GB of ram . It's only an hour and a half-ish. Could be worse. Could be Firefox with PGO. That takes an hour and a half and then I run out of ram.

IMHO, the biggest headache is getting 130-160 packages in and finding out that either I need to enable yet another module under the qt5-set module-set or install another missing dependency. Switched it from individual modules to "all" last night.

The only thing I really gain is added packages to my list, but that'll benefit others once I figure out all the dependencies that Arch/Manjaro is missing from the meta-package/kdesrc-build dependency resolver. I'm up to nine; eleven including the two gcc ones.