By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1564 - korgac and kopete deadlock on kontact start
Summary: korgac and kopete deadlock on kontact start
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdepim (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: Other Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-07-09 02:34 CDT by Roman Savochenko
Modified: 2018-05-27 11:12 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Kopete crash backtrace (23.23 KB, application/octet-stream)
2013-07-13 09:30 CDT, Roman Savochenko 		Details
Kopete force crash on hang by SIGSEGV (12.05 KB, application/octet-stream)
2013-07-16 02:31 CDT, Roman Savochenko 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Savochenko 2013-07-09 02:34:08 CDT 
After start using kopete I have observe hang/lock korgac and kopete eaсh other on kontact starting after the time, on TDE session restore.

Into ~/xsession-errors:0 about that I see:
kopete: KDCOPServiceStarter: starting /usr/share/kde/applications/kde/kontactdcop.desktop
[kinit] Got EXEC_NEW 'korgac' from launcher.
[kinit] korgac is executable and not a library. Launching with exec
[kinit] Got EXT_EXEC 'kontact' from launcher.
[kinit] kontact is executable and not a library. Launching with exec.
kopete: KDCOPServiceStarter: DCOP service is available now, as kontact
korgac: KDCOPServiceStarter: DCOP service is available now, as kontact

Also in lock stage I have not korgac and kopete icons into system tray but see kontact, korgac and kopete in two processes for each.

If I kill kopete processes then kontact and korgac will unlock and left in single processes.
Comment 1 Roman Savochenko 2013-07-13 09:30:54 CDT 
Created attachment 1343 [details]
Kopete crash backtrace

On other more fresh and X86_64 system environment I have seen Kopete crash into access to mutex lock.

I think the related problems.
Comment 2 Roman Savochenko 2013-07-16 02:31:29 CDT 
Created attachment 1347 [details]
Kopete force crash on hang by SIGSEGV

Here you can seen that hang into IceTransSocketRead() from several tasks.