Bug 120373 - Kontact startup during KDE startup doesn't allow second instance and exits both instances
Summary: Kontact startup during KDE startup doesn't allow second instance and exits bo...
Status: RESOLVED DUPLICATE of bug 127110
Alias: None
Product: kontact
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-18 10:11 UTC by René Krell
Modified: 2006-10-28 22:58 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 René Krell 2006-01-18 10:11:45 UTC
Version:           1.2 (using KDE 3.5.0 Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.15-4-default

Sometimes I shutdown KDE with Kontact running, if I logon again Kontact starts up in background (which is right). If I start Kontact by mistake again from the taskbar earlier that the automatically started instance I get a dialog box that another instance has been seen and whether to continue start or "Exit". If I push "Exit" BOTH instances of Kontact are killed. Is that the right behaviour?
May this is not a bug but a feature. Anyway, I would expect only one to be killed.

Thanx,
René
Comment 1 Christoph Burger-Scheidlin 2006-01-19 19:38:44 UTC
In my kde 3.5.0 kontact exits without notification, whenever a second instance is started, regardless of the time this is done.
Comment 2 Chris Gow 2006-10-28 21:37:14 UTC
Kontact still exits without confirmation in 3.5.5/kontact 1.2.3 Kubuntu 6.10 (edgy). In previous versions I recall getting the dialog. I would expect that the kontact instance that is running would be given focus. I would not expect kontact to exit
Comment 3 Albert Astals Cid 2006-10-28 22:58:47 UTC
For sure seems a duplicate of bug 127110 as the kdepim bug-triage-day-crew found.

*** This bug has been marked as a duplicate of 127110 ***