| Summary: | Crash when starting Kontact while already running | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Torquil Macdonald Sørensen <torquil> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Version: (using KDE KDE 3.5.2) Installed from: Debian testing/unstable Packages OS: Linux Often, if I try to start Kontact while it is already running and minimised to the system tray, it crashes. It leaves the following message in ~/.xsession-errors: FAILURE (KCmdLineArgs): Application requests for isSet("module") but the "module" option has never been specified via addCmdLineOptions( ... ) WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 1) suspended. DCOP aborting (delayed) call from 'anonymous-10313' to 'kontact' ERROR: Communication problem with kontact, it probably crashed. Best regards, TMS