Bug 342701 - mail_dispatcher_agent does not restart
Summary: mail_dispatcher_agent does not restart
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Dispatcher Agent (show other bugs)
Version: 1.13.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-10 16:24 UTC by mail
Modified: 2017-01-07 22:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mail 2015-01-10 16:24:42 UTC
When logging in, I did not enter the requested passwords for the mail dispatcher, kmail or anything. This seems to cause the dispatch agent to fail on startup, whereas it is not started after I logged in.

The problem is, that I cannot restart it. I need to reboot and enter the appropriate passwords after logging in, so the agent starts and I can actually use Kmail and so on...

Reproducible: Always

Steps to Reproduce:
1. Do not enter passwords in kwallet after login
2. check whether mail_dispatch_agent is running -> it is not (for me). I cannot restart it
3. reboot and enter the passwords in the kwallet dialog after login. The dispatch agent runs now as expected


Expected Results:  
mail_dispatch_agent should be restartable, asking for the password from kwallet.

I'm not entirely sure whether this is a kwallet issue or a akonadi/mail_dispatch_agent one. Feel free to ask me to investigate further, but please provide every piece of information I need to do it, I'm a KDE newbie.
Comment 1 Denis Kurz 2016-09-24 20:42:43 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:39:50 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.