Bug 149692 - No main window shown sometimes
Summary: No main window shown sometimes
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
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: 2007-09-09 10:27 UTC by Martin Krischik
Modified: 2017-01-07 22:12 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 Martin Krischik 2007-09-09 10:27:09 UTC
Version:           Unbekannt (using KDE 3.5.7 "release 74.2" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.18.8-0.5-default

Yes I saw the other bugs ;-) - but they where all "RESOLVED" - but they are not.

I still encounter race conditions when starting up kontact. As allways with race conditions there are diffcult to reproduce or even to describe propperly. For the simple reason that you get different results depending on who wins the race.

Sometimes kontact starts but won't show any windows. I can try to click on the kontact icon and another instance is started but still no window. First time this happend to me "ps ax" would reveal 5 running kontacts. I killed them all after which everything worked fine.

Today I got several "kontact allready started" messages. I closed them all but no kontact appeared. Again I needed to kill all runnning kontacts before normal opration resumed.

Martin
Comment 1 Denis Kurz 2016-09-24 19:24:23 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 2 Denis Kurz 2017-01-07 22:12:32 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.