Version: 4.4_rc1 / 4.3.90 (using Devel) Compiler: gcc 4.4.2 Gentoo 4.4.2 p1.0 OS: Linux Installed from: Compiled sources akonadi_imap_resource often spams error message windows. The text is approximately: "could not connect to server". It might be in relation to having no network access (yet). The problem is not that it errors out, but that it tells me about that 119 times (always the same number), which makes KWin hang for a long time, and also takes a long time to click all those messages away.
"akonadi_imap_resource" in the subject should probably replaced with "Akonadi IMAP", since it is just a guess, not a fact.
Never happened to me (actually the imap resource doesn't trigger dialogs, except the settings one).
I assure you it does happen. :) The window title contains the address of the imap server and my username, so I assume it is the Akonadi IMAP resource creating those windows.
P.S: It happened before already that Akonadi spammed error messages (which then made KWin crash, because they were thausands). So maybe it is Akonadi's error reporting as a whole which is flawed.
Marking this one as NEEDINFO as well as we definitely lack info on how to reproduce it and create the conditions to make it happen.
Maybe helpful information: * I enabled serverside-subscriptions. Afterwards I can reproduce the spam by just restarting akonadi via akonadiconsole. * Another way to make akonadi spam is to edit the options of the imap resource and press ok. Being more specific on comment #4: Maybe it is possible to make akonadi simply not produce error windows. Maybe it is possible to create one of them and update it. Or use some other way that prevents akonadi from hanging kwin. The number of messages is not very limited. On my desktop machine I get about 150 messages. On my netbook kwin starts to get very slow after akonadi spammed about 50 windows, but I can see a number in the tasktray (which I suppose is the number of error windows) increase to up to ~300, which takes about half an hour.
A similar bug has been reported earlier: bug #197367
Related issue: bug #197369 (kwin hanging when spammed with windows)
Setup of akonadi resources: akonadi-contact-feeder, nepomuk-calendar-feeder, mail-dispatcher-agent, local-folders, ~"keywords", imap-resource, kolabproxy-resource.
I also think that this bug does not occur, when bug #222600 happens when restarting akonadi. But a reliable reproduction over several restarts of the machine and configuration changes is difficult. Usually it will just hit you after a while of being logged into kde. On my netbook it just happened simply after booting and leaving the (auto-logged-in) kde running for a while. It is now at window nr 350, if we assume the tasktray is still updating in a contemporary manner.
Just did the same again: Rebooted the netbook, kde auto-login, akonadi pops up the kwallet authentication window. I wait. imap error messages start to appear after about 1-2 minutes. Wild guess: What does akonadi do if the imap resource cannot get the authentication data?
(In reply to comment #10) > I also think that this bug does not occur, when bug #222600 happens when > restarting akonadi. This is wrong. bug #222600 only occurs after giving the password to kwallet, while this bug may appear even before I did anything.
(In reply to comment #11) > Just did the same again: Rebooted the netbook, kde auto-login, akonadi pops up > the kwallet authentication window. I wait. imap error messages start to appear > after about 1-2 minutes. > Wild guess: What does akonadi do if the imap resource cannot get the > authentication data? That's not exactly the only way to reproduce this error though. Simply waiting a bit, even after providing the kwallet-password, the error windows can also appear. I now have the exact german text at hand (luckily there were only a few windows this time): title: "<mailserver>/<user> - Akonadi-Modul" text: "Derzeit besteht keine Verbindung zu dem IMAP-Server."
I assumed for a while that this bug is related to enabling server-side subscriptions. This is not the case, this bug is independend of enabling that.
(In reply to comment #14) > I assumed for a while that this bug is related to enabling server-side > subscriptions. This is not the case [...] I first thought that the issues appear only after enabling them, but they do not vanish when disabling that.
Issue persists in KDE 4.4.1.
Might have to do something with restarting the imap resource while it hangs during a sync. (At least that's what I did this time. But it could obviously be totally misleading...)
(In reply to comment #17) > Might have to do something with restarting the imap resource while it hangs > during a sync. (At least that's what I did this time. But it could obviously be > totally misleading...) Sorry, that was misphrased, should be: "restarting the akonadi server while the imap resource hangs during a sync". (Spinn-off-bug about being unable to restart the imap resource seperately: bug #229307)
Most likely fixed with commit b42370efe3a0b6cf9548b831970262c22a1bb302.
(In reply to comment #19) > Most likely fixed with commit b42370efe3a0b6cf9548b831970262c22a1bb302. I assume that commit is part of kdepim-runtime.git? Gitweb [1] cannot find it, however. [1] http://gitweb.kde.org/kdepim-runtime.git?a=search&st=commit&s=b42370efe3a0b6cf9548b831970262c22a1bb302