Bug 271226 - Akonadi errors after KVpnc disconnection
Summary: Akonadi errors after KVpnc disconnection
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-18 18:26 UTC by Jeffrey
Modified: 2017-01-07 21:46 UTC (History)
0 users

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 Jeffrey 2011-04-18 18:26:38 UTC
Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

After disconnecting from a remote PPTP network with KVpnc, I get two Akonadi popups that read something like this:

*akonadi_googledata_resource-10 - AkonadiTray
Invalid password or network proxy

*akonadi _gcal_resource_1 - AkonadiTray
Invalid password or network proxy

(*this is the name I get from the plasma panel; KWin itself won't allow me to expand this window to get info from there.)

Reproducible: Always

Steps to Reproduce:
Have a Google account set up in Akonadi

Connect to PPTP VPN with KVpnc; disconnect

Errors pop up.

Actual Results:  
Errors pop up.

Expected Results:  
Retry with the 'new' network setup and give errors if this still fails.  There should be different errors for Networking issues (cannot reach remote resource) vs password issues (remote resource can be reached but not authenticated against with this info).

Thanks for KDE!
Comment 1 Denis Kurz 2016-09-24 20:35:29 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 21:46:49 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.