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
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
I can finally say I’ve upgraded successfully to #Fedora40. It was not without hassle this time and it started with what seemed to be a system that did not even give me a prompt after #rebooting, although the update process had seemed to go smoothly and quickly. Luckily, the virtual screens were working and so I could #login to a #shell. Although #sddm didn’t seem to be working, #kdm was and so I was able to open a desktop session, but only in #Gnome
As someone who has been on Fedora since 27, reaching release 40 and upgrading without a problem makes me appreciate greatly about the team behind the OS. Thanks to you, my machine is always ready when I press that power button. If you are on Windows 11, enjoy the ads. Take Fedora for a spin, see how you like it. They have many variants of it. Surely one of them will feel right.
If everything goes well, the update to Fedora Kinoite 40 will be available in Plasma Discover once you update to tomorrow's Fedora Kinoite 39 update.
Note that we currently don't have proper download progress reporting in Discover's interface so please be patient while the update downloads. You can check "progress" via the network traffic in the network widget.
Stay tuned for incoming improvements to rpm-ostree support in Discover 🙂.
Today I updated to #Fedora#KDE 40 using dnf. After I log into my main user, I get a black screen (and Discord, which opens automatically). I’ve had this issue before. I’m using a Radeon card, so it’s not that Nvidia issue. And most importantly, the desktop does work with a brand new user, which means it’s something in the user configuration. In journalctl, qt.qpa.wayland: Wayland does not support QWindow:requestActivate() is a recurring error. Is this enough info? Thanks.
Is this a regression on Fedora 40 that anyone else is seeing? Apps that launch full-screen are launching at @1x resolution even though my screen is set @2x. Un-maximizing the app fixes it.
There’s a long-standing bug in Fedora (also in Fedora 40), where the sign-in screen is displayed at the wrong resolution (it doesn’t use the settings you have set in the Settings app).
So, for example, if you have 4K@2x set in your settings for your monitor, the sign-in screen will still display at a tiny 4K@1x.
To fix, download an app called GDM Settings from the Software app and press Display → Apply current display settings → Apply.
Just rebooted and I’m up and running with Fedora Silverblue 40.
(Just tried reinstalling mozilla-openh264 – so videos work in Firefox – but it failed with the same error. Not a big deal, I’m using @Vivaldi as my main browser these days anyway and I guess the Fedora folks will fix this in time.)
More importantly, I wonder if the screen reader has been fixed yet. (Yes, Fedora ships with a broken screen reader.)