#923291 kmail: syncing inbox(es) never finishes

Package:
akonadi-server
Source:
akonadi
Description:
Akonadi PIM storage service
Submitter:
Juha Jäykkä
Date:
2019-11-10 11:36:03 UTC
Severity:
normal
#923291#5
Date:
2019-02-25 22:19:06 UTC
From:
To:
Dear Maintainer,

Very often, almost as often as not, syncing an imap inbox never finishes. It will
get stuck at any progress level, from 0% to 100% (yes, it even gets stuck at
100%). This happens with at least google's imap servers as well as three different
dovecot servers.

Steps to reprocude: start kmail, let it run for a while, checking inboxes either
manually or letting the automatic interval check do it for you. In less than 15
minutes at least one of the inboxes gets stuck.

Sometimes normal operation can only be recovered by manually restarting the stuck
agent, but sometimes only restarting the whole akonadi sorts it out.

This makes kmail unusable for me due to the frequency of restarts: often I need to
restart aknoadi between each two emails I read. Assuming this is not widespread,
because if this is, the bug should be RC.

Cheers,
Juha

#923291#10
Date:
2019-03-03 22:12:02 UTC
From:
To:
Hey Juha,

thanks for giving input about the current state of kmail. Unfortunately these
are not enough information to tackle down the issue.

Your issue sounds that  a Akonadi Resource is stuck. Please use akonadiconsole
for debugging. At frist enable logging at the logging tab.

go to the Agent tab select the resource that got stuck and select "Show task
list" and print the output. The queues should all be empty if the sync was
successful.

We may properly to distinguish the issue for google, as goolge's imap
implementation is wired, so let's focus on opensource mailserver dovecot first.

I can't reproduce it on my setup. And I use 5 different accounts dovecot and
kolab.

Do you have stable inet for your tests? If inet went away while syncing, than
sometime Akonadi don't recover. Also putting my laptop to sleep while
currently if syncing breaks Akonadi sometimes.

But in the end of this, it will not be a Debian issue, so you need to to
report the bug upstream: https://bugs.kde.org. Please leave a note about the
concrete link to the upstream bugreport, so we can track the state inhere.

hefee

#923291#23
Date:
2019-11-10 01:35:06 UTC
From:
To:
Hello,

Bug #923291 in gimp reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gimp/commit/c7908497af6eebbc2adbd57b8935e5161cbb5b35
------------------------------------------------------------------------
New upstream release

Closes: #923291
Closes: #943731
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923291

#923291#30
Date:
2019-11-10 04:24:39 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
gimp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923291@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha <jbicha@debian.org> (supplier of updated gimp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 09 Nov 2019 20:33:53 -0500
Source: gimp
Architecture: source
Version: 2.10.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Jeremy Bicha <jbicha@debian.org>
Closes: 923291 943731
Changes:
 gimp (2.10.14-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #923291, #943731)
   * Bump minimum libbabl-dev to 0.1.72), libgegl-dev to 0.48
     & libheif-dev to 1.3.2
   * debian/gimp.install: Update
   * debian/libgimp2.0.symbols: Update
Checksums-Sha1:
 228cf1d5655234af80eda42ca364bdcb5c8e85e9 3291 gimp_2.10.14-1.dsc
 bafee9ee3d954233c6f80a47a7f97e00e3693b38 32786424 gimp_2.10.14.orig.tar.bz2
 e9d06a8faeb76555c0f479c27fa4ce33f46e91ea 42028 gimp_2.10.14-1.debian.tar.xz
 ab2176095ef2380ffb8c10bf85d8d6d59a61a907 16685 gimp_2.10.14-1_source.buildinfo
Checksums-Sha256:
 335a4aea3916546ccca205ec3af893c49c23494aaaffa9993277dc98d67d140c 3291 gimp_2.10.14-1.dsc
 df9b0f11c2078eea1de3ebc66529a5d3854c5e28636cd25a8dd077bd9d6ddc54 32786424 gimp_2.10.14.orig.tar.bz2
 5f756f814b21408351d090f1843f47a8d39b74c476bfbd15d742116835bf273f 42028 gimp_2.10.14-1.debian.tar.xz
 110c118e7b2aecf6adee7ad406e83ef8fad795f5dee6fa2263f0c77233034771 16685 gimp_2.10.14-1_source.buildinfo
Files:
 4fac7c079d431a12acdca59b6c817cc8 3291 graphics optional gimp_2.10.14-1.dsc
 a64f2be299755a2da130306cad9b1d26 32786424 graphics optional gimp_2.10.14.orig.tar.bz2
 c0d33a1aa95d07a901c375469e5f95ce 42028 graphics optional gimp_2.10.14-1.debian.tar.xz
 6053c66b5abdfd805c28f04b8aeab41a 16685 graphics optional gimp_2.10.14-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAl3HagUACgkQ5mx3Wuv+
bH29lxAAh6fXWcAPXqBXkWYh5CoNLrxGdcWxBDt/j1Y3p8ZhLtVZ1Gw5Jvcx88Va
XtNFkI5haYG81WvZloq1gU/bnDmFd+RbXg2+5DrEd1vkRHErUF4LbssuVj7y1/f/
89UjwXdTZPnYHD3LooDTsjQ0xjN4eWLow8gf1XJDrfM/UxjxuRcpOo1HHnXyWXit
C6A/ApG/H9kt8OEMSG3hI+tZJI4XNbiRZQTaWP8DAd4aCZ4oJdI5CTxL13JmJAnw
S5cfCFwPb0Kq4lKlXgr37ZtEXYc5ABkMRmNnni3n7Rp0vNAEhJTxeYfc6u5tW/Ee
BkODDwcG/kFCx8NMs6GNIRihyxl2dLxt95hqvOqOleqohozlJuoDN0hXeVWj5xb6
uKgpMrjTfMfykTuuHMdJgfjfY2Oua+ysQyuBaxeVAX84xMzwPt9mp4E59JH/R9o/
hZta+pedhObcFy8j1kM6rvCanWJNPiQnwZ2sn5ytCOgOlILgbjMpYSiAM++dG0Gy
0HWcTwPq4DOOLMQUufGSBFjfe9tj9iO3KjAKt+pxs55pUUiOSnBsCicUvjefX9hK
n9SAFV9NA/SgSubheqHKfU5Yxbq8R907rvr2Ur11Nu2ZeSVzCMh3KcmEJqbrh/ln
gszONpYPJrzDqYBl/6+dgFpEh8PHCMSewUcp/UiRkglP+NsuD3Q=
=u3s0
-----END PGP SIGNATURE-----