Well, as you may already know, but gentoo has a policy about it:

https://wiki.gentoo.org/wiki/Project:Council/AI_policy
It is expressly forbidden to contribute to Gentoo any content that has been created with the assistance of Natural Language Processing artificial intelligence tools. This motion ...

Hi all

Not sure whether this is really the right place to announce this, but 'Unsupported Software' definitely fits. Mods, if this isn't cool, please let me know.

I've been playing with Anthropic's Claude a lot of late, and was irritated to discover that there is no Linux native support for the ...

For anyone who is interested, I've also followed the Qt devs' advice and opened a GCC bug for the root cause of all of this here: It wasn't the root cause, just a different (related) thing, albeit there tend to be no end to flaky cpus.

e.g. -march=haswell enables avx as you'd expected, but .. I ...

For anyone who is interested, I've also followed the Qt devs' advice and opened a GCC bug for the root cause of all of this here:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116854

I don't have very much faith in my own ability to convince the GCC dev team that this is a bug in GCC, mostly ...

I applied the patch to dev-qt/qtbase
and compiled with -march=native
and it works. Nice, thanks for testing.

Will give it a bit longer to possibly get a 2nd confirmation and/or in case upstream has anything else to add, but will add the patch to the ebuild later for everyone in a qtbase-6.7.2-r5 ...

It doesn't look like anyone else has any further input, so: sam_, Ionen, asturm, Hu, and Arsen, thank you all very much for your help and patience with this, I think we're done.

Curious as to why it goes wrong a bit earlier in the others but maybe something just gets inlined. If this was built with -ggdb3 (to get as much debugging info as possible), I'd just report upstream at this point. If you can reproduce with -Og -ggdb3, the backtraces may be better again, but reduced ...

Here you go. Nothing special to note about any of the three runs.

# gdb ./tst_qpixmap
GNU gdb (Gentoo 14.2 vanilla) 14.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and ...

sam_ wrote:That first one looks like a perfect fit for the crash we were seeing.

If Ionen has no further input, could you report that upstream to Qt please?

Sure. Any others you want to see while the tests are still on my hard disk?

The two you suggested work out as follows:

# gdb --args ./tst_qcolordialog
GNU gdb (Gentoo 14.2 vanilla) 14.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and ...

Lot of stuff failed:

The following tests FAILED:
74 - tst_qsettings (Failed)
86 - tst_qsortfilterproxymodel (Failed)
95 - tst_qdatastream (Failed)
97 - tst_qtextstream (Failed)
219 - tst_qbackingstore (Failed)
233 - tst_qscreen (Failed)
235 - tst_qwindow (Failed)
238 - tst_qrasterwindow ...

I will build it with FEATURES=test, but may take a couple of days to do so.

If I recall correctly, somewhere amongst all of the rebuilds and troubleshooting, I did emerge qtbase with USE="test" and -march=native. It didn't report any failures at build time as far as I know; the build didn't fail, and I didn't see any errors.. USE=test does not run tests, it only builds ...

After an eternity of compiling, I'm back. It works! I can confirm that qtbase omitting march gives me a completely functioning Plasma 6 and sddm. Damn that feels good, I can use my main laptop again.


Compiling dev-qt/qtbase with -march=x86-64-v2 works.
I use package.env to compile qtbase with the ...

If can confirm that -march=x86-64-v3 works too by rebuilding qtbase again and not just none, I already prepared a dirty workaround that I could push to qt6-build.eclass' _qt6-build_sanitize_cpu_flags, aka will sanitize if this is true: [[ ${PN} == qtbase ]] && tc-is-gcc &&
[[ $($(tc-getCXX) -S ...

Does the baseline -march=x86-64-v3 work fine, rather than none at all? Be good to know if issue is limited to -march=bdver4

Also, I know tranquilcool's -march=native is bdver4 but what about yours localtoast to be sure? To be simple, can emerge app-misc/resolve-march-native and run the "resolve ...

Built qtbase with no march and non mtune. I never use mtune. And that was it.
I confirm, it works.
Thanks everybody.

I'm gonna try this when I finish using the machine for work.

If it does work for me - and I assume it most likely will - then I will thank everyone for their input and help, then ...

Well... wow, ok. I go to sleep for a few hours and this thread blows up with answers. This is pretty amazing if it works.

I have none of the kaccount-* installed.

Spectacle: I have masked: >=kde-apps/spectacle-24.05.2. Version 23.08.5 works fine.
But I prefer the old ksnap which is a lot better ...

Sweet, thanks, that looks like it could solve a problem or two. Are you having any issues with purpose or kaccounts-integration, kaccounts-providers, or anything related? Or spectacle or gwenview? Those seem as if they're going to be problematic on my install.

I need a usable laptop. It's been two weeks since I had a working DE. @asturm, if you're still watching this thread, any tips on undoing all the masking of Plasma 5 that you've done in preparation for removing it? I'm in dependency hell trying to roll back to 5.

tranquilcool wrote:<gdb and valgrind output>

Added this to the KDE bug, thank you.

Bug report filed with KDE: https://bugs.kde.org/show_bug.cgi?id=492886

Please feel free to add details I've missed - I was trying to summarise what we all have as concisely as possible.

Bug report is here: https://bugs.kde.org/show_bug.cgi?id=492886

@sam_, thanks for keeping an eye on this.

Exactly the same thing I had.

And equally few clues about what the actual problem is. I was hoping we'd get some magical revelatory piece of data. :/

Let’s hope some expert can look it up, otherwise you could file a bug. I
Don’t have plasma6 installed at the moment.

I most likely will go ...

tranquilcool wrote:
Exactly the same thing I had.

And equally few clues about what the actual problem is. I was hoping we'd get some magical revelatory piece of data. :/