Bug 72269 - Starting Kontact moves stand-alone KMail to current desktop
Summary: Starting Kontact moves stand-alone KMail to current desktop
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 1.3
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2004-01-09 21:32 UTC by Cornelius Schumacher
Modified: 2017-01-07 22:06 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Cornelius Schumacher 2004-01-09 21:32:24 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources

Start KMail, then start Kontact on another desktop. Kontact is started and the Kontact main window appears. After that the KMail main window also appears on the desktop where Kontact was started.
Comment 1 Daniel Molkentin 2004-07-19 21:06:42 UTC 
I will look into this. Seems to be some kuniqueapplication interior. Kontact has it's own magic in interfaces/uniqueapphandler.cpp but that doesn't seem to have any effect.
Comment 2 S. Burmeister 2006-10-28 12:52:23 UTC 
I still see this in 3.5.5. The kmail window is moved to the desktop kontact is started on. Cornelius, expected behaviour for you would be to leave the kmail-window on its desktop?
Comment 3 George Kiagiadakis 2008-09-28 11:51:44 UTC 
Still happens in svn trunk r865463. Is someone still working on this?
Comment 4 Denis Kurz 2016-09-24 19:20:53 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 kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:06:45 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.