race condition on login between kopete and kontact
I have suse 10.1 and with both kde 3.5.1 and now kde 3.5.4 I seem to have a race condition. When I log in both kontact and kopete appear to get stuck trying to request access to my wallet for the passwords. If I kill one of the processes then the wallet password dialog appears and then I can start the other successfully. Anyone else seeing this or know how to fix it? Andrew
On Monday 28 August 2006 10:02, Andrew Colvin said:
I have suse 10.1 and with both kde 3.5.1 and now kde 3.5.4 I seem to have a race condition.
When I log in both kontact and kopete appear to get stuck trying to request access to my wallet for the passwords. If I kill one of the processes then the wallet password dialog appears and then I can start the other successfully.
Anyone else seeing this or know how to fix it?
No, can you install debuginfo for kdepim3 and kdenetwork3, and see what gdb thinks the stuck processes are waiting on? cheers Will
On Tuesday 29 August 2006 15:05, Will Stephenson wrote:
No, can you install debuginfo for kdepim3 and kdenetwork3, and see what gdb thinks the stuck processes are waiting on?
I have found the exact same bug on kde.org: http://bugs.kde.org/show_bug.cgi?id=123583
On Tuesday 29 August 2006 16:46, Andrew Colvin said:
On Tuesday 29 August 2006 15:05, Will Stephenson wrote:
No, can you install debuginfo for kdepim3 and kdenetwork3, and see what gdb thinks the stuck processes are waiting on?
I have found the exact same bug on kde.org: http://bugs.kde.org/show_bug.cgi?id=123583
Noted. Backtraces would be helpful in this case. If you could get one for kded too that would be super. Will
On Tuesday 29 August 2006 16:11, Will Stephenson wrote:
I have found the exact same bug on kde.org: http://bugs.kde.org/show_bug.cgi?id=123583
Noted. Backtraces would be helpful in this case. If you could get one for kded too that would be super.
Will OK will try - not sure how i do this at login time but will try a few things
On Tuesday 29 August 2006 17:35, Andrew Colvin said:
OK will try - not sure how i do this at login time but will try a few things
Once they have hung and the rest of the session, attach gdb to each process
with gdb -p
participants (2)
-
Andrew Colvin
-
Will Stephenson