Bug 110292 - Race condition at start when both kopete and kontact running at previous saved sesssion
Summary: Race condition at start when both kopete and kontact running at previous save...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: dcop
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 3.4.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-06 16:25 UTC by jamundso
Modified: 2010-02-11 05:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Shows kopete in la-la land (44.98 KB, image/png)
2005-08-06 16:28 UTC, jamundso
Details
Running processes at startup. (8.20 KB, text/plain)
2005-08-06 16:29 UTC, jamundso
Details
gdb/bt of child kopete process (12.18 KB, text/plain)
2005-08-25 23:21 UTC, jamundso
Details
gdb/bt of child kontact process (19.48 KB, text/plain)
2005-08-25 23:22 UTC, jamundso
Details
gdb/bt of parent kopete process (9.03 KB, text/plain)
2005-08-25 23:23 UTC, jamundso
Details
gdb/bt of parent kontact process (8.63 KB, text/plain)
2005-08-25 23:24 UTC, jamundso
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jamundso 2005-08-06 16:25:02 UTC
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.
Comment 1 jamundso 2005-08-06 16:28:14 UTC
Created attachment 12110 [details]
Shows kopete in la-la land

Unrefreshed from Alt-F7 - Original kopete showed start of contact tree.
Comment 2 jamundso 2005-08-06 16:29:49 UTC
Created attachment 12111 [details]
Running processes at startup.

"kill 2586" allowed kopete to continue...
Comment 3 jamundso 2005-08-06 16:32:59 UTC
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.
Comment 4 Olivier Goffart 2005-08-25 15:32:00 UTC
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


Comment 5 jamundso 2005-08-25 23:21:24 UTC
Created attachment 12376 [details]
gdb/bt of child kopete process
Comment 6 jamundso 2005-08-25 23:22:16 UTC
Created attachment 12377 [details]
gdb/bt of child kontact process
Comment 7 jamundso 2005-08-25 23:23:09 UTC
Created attachment 12378 [details]
gdb/bt of parent kopete process
Comment 8 jamundso 2005-08-25 23:24:21 UTC
Created attachment 12379 [details]
gdb/bt of parent kontact process
Comment 9 jamundso 2005-08-25 23:30:35 UTC
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...
Comment 10 Olivier Goffart 2005-09-06 14:37:38 UTC
I don't think the problem is in Kopete or Kontact,  
but this is probably a dcop deadlock.
Comment 11 jamundso 2005-12-04 16:52:11 UTC
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.
Comment 12 jamundso 2006-05-23 18:23:13 UTC
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 ...
Comment 13 Chani 2006-05-23 18:35:12 UTC
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.
Comment 14 Matt Rogers 2006-05-23 18:37:32 UTC
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 :(
Comment 15 Matt Rogers 2006-05-23 18:43:08 UTC
@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)
Comment 16 jamundso 2007-12-27 06:15:28 UTC
Where's Waldo?
Sorry, after over a year and half with no update, I couldn't resist upon seeing the "Assigned to:" ... :-)
Comment 17 FiNeX 2008-12-26 14:37:35 UTC
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?
Comment 18 Dario Andres 2009-05-02 23:10:30 UTC
Marking as NEEDSINFO
If this was a DCOP bug then it should be marked as UNMAINTAINED
Comment 19 jamundso 2010-02-10 18:26:39 UTC
Sorry, lost this in the NEEDSINFO void.
I'll re-test when time permits.