Version: 0.10.3 (using KDE KDE 3.4.2) Installed from: Fedora RPMs OS: Linux Race condition at start when both kopete and kontact running at previous saved sesssion. Can kill 2nd kontact, allowing kopete to start, but of course kontact does not.
Created attachment 12110 [details] Shows kopete in la-la land Unrefreshed from Alt-F7 - Original kopete showed start of contact tree.
Created attachment 12111 [details] Running processes at startup. "kill 2586" allowed kopete to continue...
I should also mention that I, at one time, had a Contact marked as "in address book", but don't any longer. I also have IMAP KDE resources for Contacts, Calendar, and Notes.
is kontact also freezed ? would be nice to have backtrace of both kopete and kontact, you can do that which gdb gdb kopete `pidof kopete` and type bt in gdb
Created attachment 12376 [details] gdb/bt of child kopete process
Created attachment 12377 [details] gdb/bt of child kontact process
Created attachment 12378 [details] gdb/bt of parent kopete process
Created attachment 12379 [details] gdb/bt of parent kontact process
Yes, kopete is frozen, in the systray and greyed out. Clarification on opening comment: both second and first (child/parent) processes are killed to allow kopete startup to continue...
I don't think the problem is in Kopete or Kontact, but this is probably a dcop deadlock.
I just want to put a pointer to http://bugs.kde.org/show_bug.cgi?id=97764 as it seems related. Anyway, I also happened upon a work-around: o Save Session with only Kontact started, and *only* Kalarm running in System Tray o In KAlarm add new command alarms which run "knotes &", "kopete &", and "korganc --miniicon korganizer &" at login, and set expires to around 2030 (it case this doesn't get fixed for awhile ;-) That does it. The timing of each application works for me this way, anyway.
It is really pathetic that, in a great desktop like KDE, email and instant messaging cannot both start automatically at login. Let me guess - it's targeted to be fixed in KDE4 ...
funny, it works fine for me. maybe your settings are messed up - if you create a new user on your comp, can it start kontact and kopete happily? I find it hard to believe kopete is doing anything wrong here.
yup. It'll be KDE 4 since DCOP will be replaced with D-BUS and we won't have these problems hopefully. sorry for your frustration. At least you have a workaround, most people aren't so lucky :(
@Chani: you probably aren't using an IMAP resource, since that's the only time the deadlock is triggered. (and, no, kopete isn't doing anything wrong, that's why the bug is in DCOP. kopete-devel is just on the CC list)
Where's Waldo? Sorry, after over a year and half with no update, I couldn't resist upon seeing the "Assigned to:" ... :-)
It works for me on current trunk (~ kde4.2 beta2)... and yes, I'm using an IMAP account too. Could you confirm that the bug doesn't exist anymore on KDE4?
Marking as NEEDSINFO If this was a DCOP bug then it should be marked as UNMAINTAINED
Sorry, lost this in the NEEDSINFO void. I'll re-test when time permits.