Bug 99062 - Timeout on server may result in many, many popup messages
Summary: Timeout on server may result in many, many popup messages
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-10 22:08 UTC by Hans
Modified: 2017-01-07 22:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans 2005-02-10 22:08:44 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Unlisted Binary Package
OS:                Linux

I have a connection set up through kontact to a calendar on an http server, and it is set to check for changes every ten minutes.  If the connection to this server is lost, the Korganizer Alarm Daemon displays a popup message as it should.  However, if this message isn't dismissed by the time the server is checked again, then when the first popup message is dismissed, another appears immediately.

This isn't so bad unless the connection is lost while I'm away from the computer overnight or over a weekend, in which case it appears a message is queued up for each time the server check failed.  This may result in dozens and dozens of duplicate messages that appear one after another.

The text of the error message is as follows:

--------
Error - KOrganizer Alarm Daemon
--------
Timeout on server

Connection was to 172.16.75.32 at port 80
--------
Comment 1 Reinhold Kainhofer 2006-11-02 18:54:07 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 FiNeX 2008-09-28 23:30:04 UTC
Currently (using trunk of KDE4) the error message is displayed once. If you had set a timeout for the sync, when you click "ok" you'll have to wait since the next sync.

This behaviour seems right to me.
Comment 3 Denis Kurz 2016-09-24 18:54:13 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:10:40 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.