@electrona Ah yea that specifically will unfortunately have to happen on device.
I would recommend aiming for having your first on-device build not do anything nvidia at all - so you have an established base which will just boot & run - without GPU acceleration. Then you can do your nvidia config iterations based on that - able to return to this base build when a test of yours doesn't boot properly.
@hroncok@brnohat Not many people, but it was the best release party in a log time, interesting talks and even more interesting discussions. Normally we're done with the talk section in 1.5-2 hours, this time it took 4 hours and it was never boring.
I will be removing @fedora 38 from the list of buildroots used in my cloud tools #COPR this evening (2024.05.14). Today is the release's EOL date, please migrate to #fedora39 or #fedora40 ASAP!
Drugi raport z używania #fedora40 Jest dobrze, nawet bardzo dobrze nie licząc Nvidii... Fedora jest oficjalnie wspieraną dystrybucją przez cuda i nvcc. Strona Nvidii mówi wręcz, że wspierane są aktywnie wspierane majory. Więc wspierana jest też 40, której charmonogram premiery jest dość dobrze znany z wyprzedzeniem?
Otuż, nie. Okazuje się, że nvcc i gcc aktualnie są rozjechane wersjami i próba zbudowania jednego projektu kończy się klęską, nawet jeśli zignoruję wersję... Tak więc, jakbędę miał chwilę będę musiał sprawdzić podmana i jak działa z toolkitem od GPU Nvidii dla kontenerów...
Ostatnio sporo bawię się #fedora40 🙂 (dzięki Mordeczki za polecenie tego distro). Czy istnieje jakaś możliwość synchronizacji kalendarza z konta iCloud z kalendarzem systemowym w Fedorze? Niestety nie można dodać konta iCloud 😟 Jakieś Google czy inne Microsofty spoko, ale nie iCloud,
I just installed COSMIC Desktop on Fedora 40. It works smoothly and is very fast. All apps open instantly with no glitches or hangs, and everything functions perfectly. Well Done, COSMIC team. #cosmic#desktop#fedora40#system76
@thomas Next year, Linux will take over the desktop. I am certain!
Being sarcastic is destructive, but fun. Sorry. Ignore me for now. :-)
... looks a bit as if your font was a jack-ass trying to form ligatures where there are none. Or maybe it messes up the kerning in a very freaky way? I would not be surprised if this is some kind of an asian font that tries to render western language? Maybe even a right-to-left font in left-to-right mode? I have seen things, you know...
Hmm. It seems I ran into an issue with Fedora 40 and KDE 6 after today's update. Am I the only person with this issue?
When I run systemsettings, I get the following error:
$ systemsettings
systemsettings: symbol lookup error: /lib64/libKF6KCMUtils.so.6: undefined symbol: _ZN32KCategorizedSortFilterProxyModel16staticMetaObjectE
I guess it could be related to the following?:
Problem 1: package telegram-desktop-4.16.8-1.fc40.x86_64 requires libQt6Core.so.6(Qt_6.6_PRIVATE_API)(64bit), but none of the providers can be installed
- package telegram-desktop-4.16.8-1.fc40.x86_64 requires qt6-qtbase(x86-64) = 6.6.2, but none of the providers can be installed
- cannot install both qt6-qtbase-6.6.2-7.fc40.x86_64 and qt6-qtbase-6.7.0-3.fc40.x86_64
- cannot install the best update candidate for package telegram-desktop-4.16.8-1.fc40.x86_64
- cannot install the best update candidate for package qt6-qtbase-6.6.2-7.fc40.x86_64
Problem 2: problem with installed package
- package telegram-desktop-4.16.8-1.fc40.x86_64 requires libQt6Gui.so.6(Qt_6.6_PRIVATE_API)(64bit), but none of the providers can be installed
- package telegram-desktop-4.16.8-1.fc40.x86_64 requires libQt6Widgets.so.6(Qt_6.6_PRIVATE_API)(64bit), but none of the providers can be installed
- cannot install both qt6-qtbase-gui-6.6.2-7.fc40.x86_64 and qt6-qtbase-gui-6.7.0-3.fc40.x86_64
- cannot install the best update candidate for package qt6-qtbase-gui-6.6.2-7.fc40.x86_64
@dwarf it looks like qt 6.7 only recently went stable as part of https://bodhi.fedoraproject.org/updates/FEDORA-2024-c9a2438d21 . so I guess maybe that update got incompletely applied on your system because of telegram-desktop. same advice applies, remove telegram-desktop and run another system update. when telegram-desktop is rebuilt in rpmfusion you can reinstall it, or just use a flatpak as you said. sorry for the trouble!
@adamw it happened after the latest KDE frameworks(?) update, from .1 to .2, it happened on KDE 5 also, but because that did not rely on qt 6 that wasn't as breaking as it is on Plasma 6. It's mostly always fixed within a week!