It seems like in current Rawhide KDE tests, an "Akonadi migration agent" popup notification appears and spins seemingly forever. I don't know what it's trying to tell us and I don't know why it never goes away, but it's messing with the openQA tests. For e.g. this one: https://openqa.fedoraproject.org/tests/407894 . Note the video recording: https://openqa.fedoraproject.org/tests/407894/file/video.ogv . This notification is present throughout the entire test, and slows it down considerably (the test relies on waiting for a 'still screen' quite often, and it never gets one because of this constantly-changing notification).
Moving to kdepim-runtime, as that's the package this akonadi_migration_agent is in. This still happens frequently and still screws up the openQA tests.
Triggered by this? /usr/share/akonadi/agents/migrationagent.desktop So, dug around a bit, and on my user acct, I see ~/.config/akonadi-migrationrc that contains: [gidmigratortext/directory] MigrationState=Complete maybe we can hack that config into the live user to trick it into not running?
Well sure, but it's running on *the installed system* too. That test I linked to runs on an installed system, not in the live environment.
This may or may not be the same as bug #1709054 that I ran into a while ago and that was encountered again by a user on #fedora-kde, so I interlinked the bugs.
*** Bug 1709054 has been marked as a duplicate of this bug. ***
So I just had the empty dummy job notification happen again in a VM. This time, I actually looked at the running processes, and there was indeed an akonadi_migration_agent running with PID 1578. So I did "kill 1578" and the dummy job went away! There was just a "failed" notification that I was able to click away. So it is the akonadi_migration_agent that is to blame in both cases. It gets stuck for some reason, sometimes with a proper name on the job and sometimes without.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Still happening in 32, fresh install.
I don't think we're seeing this any more in F33, but leaving open for F31/F32.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Setting to 32 per Charles Ferrari comment.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug has just happened to me on Fedora 37 KDE Spin. Akonadi Migration Agent notification spinning endlessly. Reading through the thread, I was able to find the process with 'ps aux | grep akonadi' and kill it, which the notification said that it had closed unexpectedly. The system was installed months ago with Fedora 36, and updated to F37 on release. I haven't seen this bug before, but it does still occur although it's rare.
Installed Fedora-Server-KVM-38_Beta-1.3.x86_64.qcow2 in a QEMU/KVM virtual machine and this behavior is reoccuring
Er...did you hit the wrong bug by accident? This is a KDE bug.
Search led me here with its history
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Per #c16 someone saw this on F38 at least.