------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=133795
------- Additional Comments From patrol sinus cz 2006-12-11 05:35 -------
Hi!
I have this problem since early 3.5.5 and it's still present here. It doesn't
appear always, What I can report, is:
1) Sometimes it happens almost always, other times I can start it ten times in
a row without a problem. But normally it's hard to start it.
2) rm'ing .kde/share/apps/kopete increases the probability that it will start,
but it's not sure anyway.
3) When it's run from konsole with all possible debugging messages turned on,
it shows only
libkopete: [void
Kopete::ContactList::setSelectedItems(QPtrList<Kopete::MetaContact>,
QPtrList<Kopete::Group>)] 0 metacontacts, 0 gr
oups selected
kopete: [void KopeteEditGlobalIdentityWidget::setIconSize(int)] Manually
changing the icon size.
When it starts OK, it then continues with
kopete: [Kopete::Global::Properties::Properties()]
and a lot of other messages from jabber (not using other protocols, just
jabber). So I hope you can find at least approximate place of the freeze.
4) When gdb is attached, it shows it's waiting __lll_mutex_lock_wait () from
libpthread. It's the same as in the bt already attached here.
5) I'm compiling kde regularly every week from the 3.5 branch SVN. I'm making a
binary package and distributing it over about 5 machines I'm using. The problem
appears only on some of them, which are the fastest and with dual-core CPUs. On
slower, single-CPU machines it seems to work reliably.
My conclusion is that this problem is caused by some kind of race.
Please look at again, because kopete is much more better than, for example,
centericq, which I should use now.
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
