Bug 168712 - Remote kalendar save dialog pops up in front preventing the user from continuing work (kontact/korganizer)
Summary: Remote kalendar save dialog pops up in front preventing the user from continu...
Status: RESOLVED WORKSFORME
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: 2008-08-08 09:51 UTC by gmud
Modified: 2009-02-02 15:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description gmud 2008-08-08 09:51:00 UTC 
Version:           4.1.0 (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-19-rt

Steps to reproduce:

1. Delete all local calendar resources
2. Setup a webdav calendar resource (*.ics on remote)
3. Make a new entry in calendar, after hitting ok ...
4. ... immediately make another new entry

Results:
While typing the information for the second entry a file transfer window pops up in the front so that the user cannot continue typing in the event window.

Expected results:
Open the file transfer dialog in the back or show the information in a status bar
Comment 1 Dario Andres 2009-01-13 13:25:01 UTC 
Can you still reproduce this bug with a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn / 4.3svn) ? Thanks :)
Comment 2 gmud 2009-01-13 15:30:35 UTC 
At least it's still valid for KDE 4.1.3, I don't know about any later version, because I currently cannot build from trunk and there are no official ubuntu packages out yet. I will test when a newer version is available.
Darío, does the bug not appear with your version?
Comment 3 Dario Andres 2009-01-13 15:36:25 UTC 
I don't have resources to test this bug :(
Comment 4 gmud 2009-02-02 15:50:51 UTC 
I cannot reproduce in KDE 4.2. There is a new system tray message popping up that solves this issue. This bug can be closed. Thanks!