After installing this update it is required that you logout of
your current user session and log back in to ensure the changes
supplied by this update are applied properly.
How to install
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
Got this error during the upgrade. Everything else seems to be work though
Problem: problem with installed package kio-gdrive-23.04.0-2.fc38.x86_64
- package kio-gdrive-23.04.0-2.fc38.x86_64 requires libKPimGAPICore.so.5()(64bit), but none of the providers can be installed
- package kio-gdrive-23.04.0-2.fc38.x86_64 requires libKPimGAPIDrive.so.5()(64bit), but none of the providers can be installed
- cannot install both libkgapi-23.04.0-1.fc38.x86_64 and libkgapi-22.12.3-1.fc38.x86_64
- cannot install the best update candidate for package libkgapi-22.12.3-1.fc38.x86_64
This update has been submitted for testing by bodhi.
I shall also note that this ABI break was not even announced for Rawhide as far as I can tell. The first time I heard about it for Rawhide was from those FTI bugs, and the first time I hear this is being backported to F38 is from the comments on this update.
Problem 1: problem with installed package kmymoney-libs-5.1.3-2.fc38.x86_64
- package kmymoney-libs-5.1.3-2.fc38.x86_64 requires libKF5AkonadiCore.so.5()(64bit), but none of the providers can be installed
- cannot install both kf5-akonadi-server-23.04.0-1.fc38.x86_64 and kf5-akonadi-server-22.12.3-2.fc38.x86_64
- cannot install both kf5-akonadi-server-23.04.0-1.fc38.x86_64 and kf5-akonadi-server-22.12.3-1.fc38.x86_64
- cannot install the best update candidate for package kf5-akonadi-server-22.12.3-2.fc38.x86_64
Problem 2: problem with installed package kmymoney-5.1.3-2.fc38.x86_64
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_csvimportercore.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_icons.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_menus.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_models.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_mymoney.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_payeeidentifier.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_plugin.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_printer.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_settings.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires libkmm_widgets.so.5()(64bit), but none of the providers can be installed
- package kmymoney-5.1.3-2.fc38.x86_64 requires kmymoney-libs(x86-64) = 5.1.3-2.fc38, but none of the providers can be installed
- package kmymoney-libs-5.1.3-2.fc38.x86_64 requires libKF5IdentityManagement.so.5()(64bit), but none of the providers can be installed
- cannot install both kf5-kidentitymanagement-23.04.0-1.fc38.x86_64 and kf5-kidentitymanagement-22.12.3-1.fc38.x86_64
- cannot install the best update candidate for package kf5-kidentitymanagement-22.12.3-1.fc38.x86_64
I am trying right now to get it to build in Rawhide, then in F38.
The way kdepim has broken backwards compatibility is really a PITA. Especially in the KF5 branch that should really be in maintenance mode. They should have left the breaking changes for the Qt6/KF6 port!
The changes are not only incompatible, but also include some fun screwups:
They have installed backwards compatibility CMake modules for libkdepim and kpimtextedit, but NOT kwebengineviewer.
For kpimtextedit, if you do the exact replacements the deprecation message tells you to do, it does NOT work, because it was actually renamed to KPim5TextEdit and NOT KPim5PimTextEdit as the deprecation message claims.
/builddir/build/BUILD/blogilo-17.08.3/composereditorwebengine/src/composerwebengine.cpp:24:10: fatal error: kpimtextedit/texttospeech.h: No such file or directory
24 | #include "kpimtextedit/texttospeech.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
I would patch it to use ktextaddons instead (it seems to be basically the same API, just in a different namespace), but I cannot because it is not packaged in Fedora.
But even if you do not care about Blogilo, this accessibility regression must be fixed before the kdepim update can be pushed to a stable Fedora release.
Actually, it looks like ktextaddons was recently imported (without the kf5- prefix, which is why I have not found it at first – this is going to be a problem when there will be a separate kf6 version), but it is not built with text to speech support:
-- The following OPTIONAL packages have not been found:
* Qt5TextToSpeech, Add support for text to speech
So you need to build ktextaddons with Qt5TextToSpeech and then kpimtextedit with ktextaddons to fix the accessibility regression.
This update's test gating status has been changed to 'passed'.
To fix the accessibility regression, first ktextaddons-1.1.1-2 and then kf5-kpimtextedit-23.04.0-2 (which depends on the former) need to be built in a side tag and included here.
For Blogilo, another build attempt is now running in Rawhide, also depending on ktextaddons-1.1.1-2.
Note that this update brings a tiny regression that in the first 5-10 seconds after boot, QT-based apps cannot be launched / there is a considerable delay, and system tray icons of autostart apps don't appear until killed+relaunched manually. However, this is likely an upstream issue, since it happens on my Ubuntu system too after the update to the latest Gear.
Does disabling systemd user sessions (kwriteconfig5 --file startkderc --group General --key systemdBoot false – as your regular user, NOT as root) fix it?
I don't think it did. There is a slightly different behaviour, though for the app launch issue. Using systemdBoot=false, KDE apps can be launched as soon as the session starts, without delay. However, the session loading takes much longer (the additional loading time of the splash screen seems to correspond to the app launch delay with systemdBoot=true).
The icons from autostart apps are still missing in the tray with systemdBoot=false.
To add some potentially important information for debugging: the issue appears to be independent from the graphics server, as it happens both with Wayland and X11. I have the following apps in my autostart section:
This update's test gating status has been changed to 'waiting'.
Works for me. (The Google Contacts patch isn't here, correct?)
Got this error during the upgrade. Everything else seems to be work though
This update has been submitted for testing by bodhi.
@imabug I will rebuild kio-gdrive and add it to this update.
@gtwilliams: what google contacts patch are you reffering to?
marcdeop edited this update.
New build(s):
Karma has been reset.
@marcdeop you merged it in a copr: gear for f37. It fixed a bug, but it doesn't appear that it's included in this update.
https://download.copr.fedorainfracloud.org/results/marcdeop/gear/fedora-$releasever-$basearch/
It's the issue @imabug mentioned. With the new kio-gdrive rebuild libkgapi should be installable and your google stuff will work :-)
This update's test gating status has been changed to 'failed'.
kaddressbook updates now and the Google Contacts are now added as an address book.
The incompatible changes in KDE PIM libraries (already mentioned in a comment) are also going to break Blogilo and Trojitá: * https://bugzilla.redhat.com/show_bug.cgi?id=2182704 * https://bugzilla.redhat.com/show_bug.cgi?id=2182714
The packages also do not rebuild as is, see: * https://bugzilla.redhat.com/show_bug.cgi?id=2182704#c3 * https://bugzilla.redhat.com/show_bug.cgi?id=2171741#c1
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
See also https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#philosophy : "ABI changes in general are very strongly discouraged".
I shall also note that this ABI break was not even announced for Rawhide as far as I can tell. The first time I heard about it for Rawhide was from those FTI bugs, and the first time I hear this is being backported to F38 is from the comments on this update.
Working great here
Works great! LGTM! =)
Is it normal for this version of ghostwriter to install way too many kde dependencies that weren't needed for 23.03.90?
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update can be pushed to stable now if the maintainer wishes
@kkofler you may need to fork Blogilo if you want to keep it running in Fedora as it is no longer maintained by KDE. https://apps.kde.org/blogilo/
I get the following dependency conflict:
marcdeop edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by marcdeop.
This update's test gating status has been changed to 'waiting'.
ngompa edited this update.
Still breaks Blogilo.
I am trying right now to get it to build in Rawhide, then in F38.
The way kdepim has broken backwards compatibility is really a PITA. Especially in the KF5 branch that should really be in maintenance mode. They should have left the breaking changes for the Qt6/KF6 port!
The changes are not only incompatible, but also include some fun screwups:
kf5-kpimtextedit is missing text-to-speech support, which is a regression in this update.
Previously, this functionality was shipped with KPimTextEdit. But as of:
https://invent.kde.org/pim/kpimtextedit/-/commit/d1208e340a7328147037b1c23639c0a176319af5
it has been moved to a separate ktextaddons package which is not packaged in Fedora yet. As a result, the functionality is missing:
https://kojipkgs.fedoraproject.org//packages/kf5-kpimtextedit/23.04.0/1.fc38/data/logs/x86_64/build.log
Unfortunately, Blogilo requires this support to build:
https://kojipkgs.fedoraproject.org//work/tasks/8694/100858694/build.log
I would patch it to use ktextaddons instead (it seems to be basically the same API, just in a different namespace), but I cannot because it is not packaged in Fedora.
But even if you do not care about Blogilo, this accessibility regression must be fixed before the kdepim update can be pushed to a stable Fedora release.
Actually, it looks like ktextaddons was recently imported (without the kf5- prefix, which is why I have not found it at first – this is going to be a problem when there will be a separate kf6 version), but it is not built with text to speech support:
So you need to build ktextaddons with Qt5TextToSpeech and then kpimtextedit with ktextaddons to fix the accessibility regression.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Works for me now.
To fix the accessibility regression, first ktextaddons-1.1.1-2 and then kf5-kpimtextedit-23.04.0-2 (which depends on the former) need to be built in a side tag and included here.
For Blogilo, another build attempt is now running in Rawhide, also depending on ktextaddons-1.1.1-2.
This is now built in Rawhide as blogilo-17.08.3-26.fc39, but we need an fc38 build included here, too.
kkofler edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by kkofler.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works for me
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by marcdeop.
This update has been pushed to stable.
Note that this update brings a tiny regression that in the first 5-10 seconds after boot, QT-based apps cannot be launched / there is a considerable delay, and system tray icons of autostart apps don't appear until killed+relaunched manually. However, this is likely an upstream issue, since it happens on my Ubuntu system too after the update to the latest Gear.
Does disabling systemd user sessions (
kwriteconfig5 --file startkderc --group General --key systemdBoot false– as your regular user, NOT as root) fix it?I don't think it did. There is a slightly different behaviour, though for the app launch issue. Using systemdBoot=false, KDE apps can be launched as soon as the session starts, without delay. However, the session loading takes much longer (the additional loading time of the splash screen seems to correspond to the app launch delay with systemdBoot=true).
The icons from autostart apps are still missing in the tray with systemdBoot=false.
To add some potentially important information for debugging: the issue appears to be independent from the graphics server, as it happens both with Wayland and X11. I have the following apps in my autostart section: