| Summary: | KMail restarts every session since i played around with kontact | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Wolfram R. Sieber <Wolfram.R.Sieber> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | dirk.heinrichs, finex, franke.daniel, jamundso, kollix, mail, pioppo, pookey, stephane |
| Priority: | NOR | ||
| Version: | 1.7.1 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Wolfram R. Sieber
2005-01-24 02:54:44 UTC
I just found out that starting knotes implicitely starts kmail, too. But only in my main user account. Both were plugged in into kontact. I turned them off both, now. But that didn't change anything on that strange knotes behaviour. Just found out that kmail starts in conjunction with konversation, too. Any idea of how to get rid of this in-conjunction starts of kmail? De-install kde? (*grmbl*) me too, it's very annoying, particularly because kmail brings in kwallet and I can't close it until I typed the wallet passphrase. Kopete and kalarmd also a factor. Has to do with IMAP resource. I played around with kcontrol -> KDE components -> KDE ressources and got rid of the criticized behaviour. Unfortunately I omitted to document each of the steps.
Current configuration is:
Drop down list = calendar
untitled list below: [x] standard calendar - file - yes
Drop down list = konnector
untitled list below: (is empty)
Drop down list = contact
untitled list below: [ ] kolab server - imap - (empty)
[x] resource-name - file - yes
Drop down list = notes
untitled list below: [ ] kolab server - imap - (empty)
[x] Notes - file - yes
*** Bug 100280 has been marked as a duplicate of this bug. *** This makes me think to a question related to resources. In kcontrol -> KDE Resources, selecting imap-resource as the standard resource for either Notes, Contacts and Calendar prints the following message: "There is no valid standard resource! Please select one which is neither read-only nor inactive.". Nevertheless, it works but with this bug. I think that's bad for user because they don't really know what to do if they simply want their calendar, notes and contacts stored locally using disconnected imap and synchronised by imap. I think it is important, specially for PIM, that things just work. A patch is here: http://bugs.kde.org/show_bug.cgi?id=100280 The bug is still present in the Kubuntu KDE 3.5 packages. It would be nice if patched got applied to upstream, because this bug really reduce the KDE usability by giving a feeling of overbloating (this is a troll generator bug ;-)). Thanks, Steph Someone has still this issue? If not this bug should be closed ok? I have still this bug. It has never been fixed. I'm running kde 3.5.8 on a gentoo system. What is the output of: ps xa |grep kmail Haven't you tried to do some test with a clean ~/.kde ? After kopete has automatically launched kmail on startup ps xa|grep kmail shows: chris@daywalker ~ $ ps xa |grep kmail 19954 ? Sl 0:06 kmail -caption KMail -icon kmail -miniicon kmail 19981 pts/1 R+ 0:00 grep --colour=auto kmail I also tried it with a clean .kde. Besides that the groupware folders (e.g kontacts in the disconnected imap ressource) dosn't work anymore, the bug is still present. Hi! I have this same behaviour on my machine but the cause is simple. If you have any application searching for pim information (contacts, calendar, etc...) and you have at least one groupware resource activated through kmail, then it will be launched on startup. In my case, the culprit is korgac that launches on startup for the calendar reminders, but kopete does it too, for the contact information. My initial solution was to disable groupware resources. Nowdays I just never logout. Probabily, with the upcoming akonadi, this behaviour will be corrected. *** Bug 176394 has been marked as a duplicate of this bug. *** Looks like a duplicate of Bug #93203 *** This bug has been marked as a duplicate of bug 93203 *** |