Kontact crashes if started while already running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdepim (Ubuntu) |
Fix Released
|
Medium
|
Jonathan Riddell |
Bug Description
If 'kontact' is executed while Kontact is already running, around 25% of the
time the existing Kontact instance will simply be maximised and brought to the
front. However, the other 75% of the time the running instance of Kontact
crashes (a new instance doesn't actually start, it just gives an error on the
commnad line).
When this happens, the already running instance of Kontact gives the following
command line output:
FAILURE (KCmdLineArgs):
Application requests for isSet("module") but the "module" option
has never been specified via addCmdLineOptions( ... )
And the command line output from the second instance is:
ERROR: Communication problem with kontact, it probably crashed.
For some reason, this crash isn't caught by the KDE Crash Handler, so I don't
have a backtrace (but can get one, if someone would kindly tell me how to do it
manually).
I'm running Breezy on AMD64 (the bug was also present in Hoary).
Changed in kdepim: | |
status: | Confirmed → Fix Released |
This bug is not present on my machine running kubuntu dapper amd64. This has probably been fixed for dapper.