This has been going on for a while( ~ 3 - 4 months ) but I've been ignoring it using other IM clients. Now I tried to use kopete again but it still crashes when I try to add a jabber account. As soon as I choose jabber account setup and press next kopete crashes. I am using KDE desktop and emerged kdenetwork-3.5.7-r1(not the seperate kopete ebuild). I have the same problem on my desktop pc(kopete ebuild, gnome desktop). On my desktop I am able to add jabber accounts but as soon as I connect to jabber kopete crashes. The same thing occured here(laptop) too. But now I am completely unable to add an account. Things I tried to solve the problem: * remove everything related to kopete in my home directory(config etc.) * reinstall dev-libs/pth and app-crypt/gnupg * reinstall/remove kopete-otr and libotr * reinstall app-crypt/qca and app-crypt/qca-tls as well as reinstall of kdenetwork. And I couldn't find a solution. Reproducible: Always Steps to Reproduce: 1. Start kopete 2. Choose add an account 3. Choose jabber and press next Actual Results: Kopete crashes. Expected Results: Show the jabber account settings window. After starting kopete from console it leaves these messages after crashing... monolit@helyum ~ $ kopete QMultiInputContext::changeInputMethod(): index=0, slave=xim QMultiInputContext::changeInputMethod(): index=0, slave=xim monolit@helyum ~ $ QMultiInputContext::changeInputMethod(): index=0, slave=xim kopete: tpp.c:63: __pthread_tpp_change_priority: Sav `new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)' başarısızlığa uğradı. KCrash: Application 'kopete' crashing...
Your emerge --info, please, and the output of "emerge -pv kdenetwork".
Created attachment 128621 [details] emerge info
OUTPUT OF "emerge -pv kdenetwork" : These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] kde-base/kdenetwork-3.5.7-r1 USE="arts jingle kdehiddenvisibility sametime slp ssl wifi xinerama -debug -kdeenablefinal -rdesktop" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB
(new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)' başarısızlığa uğradı(failed). It says it failed.
I have the same problem when trying to add a Jabber-account. Here, the console states a similar output after the crash: kopete: tpp.c:63: __pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)' failed. KCrash: Application 'kopete' crashing..
I get exactly the same error here when I try to call someone via Jingle. (amd64 kopete-3.5.7)
Other than reporting this at bugs.kde.org so the kopete devs can work on it, I don't know what we can do.
Also reported the same problem under http://bugs.kde.org/show_bug.cgi?id=150359 ; although that bug entry is not written as the same problem (but crashes with the same failed assert(). As I posted there... Same problem under gentoo, but when trying to add a jabber account. Didn't try yet wiping my settings as I keep history there, but I can move them if necessary. kopete: tpp.c:63: __pthread_tpp_change_priority: La declaración `new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)' no se cumple. Program received signal SIGABRT, Aborted. [Switching to Thread -1477904688 (LWP 27850)] 0xffffe410 in __kernel_vsyscall () (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0x48dcaf4f in raise () from /lib/libc.so.6 #2 0x48eebff4 in ?? () from /lib/libc.so.6 #3 0xa7e8f6d0 in ?? () #4 0x48dcc958 in abort () from /lib/libc.so.6 #5 0x00000000 in ?? () Also tried remerging pth, gnupg or qca / qca-tls with no success. Kopete is merged with USE="debug arts autoreplace connectionstatus contactnotes crypt debug history jingle kdeenablefinal kdehiddenvisibility kernel_linux netmeeting nowlistening sms ssl statistics texteffect translator winpopup xscreensaver" and CFLAGS="-march=athlon-tbird -O2 -pipe -mmmx -m3dnow -fno-strict-aliasing" CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden". libdenetwork is 3.5.7, gcc 4.1.2, glibc-2.6.1-r0 and kernel 2.6.22-kamikaze9. I have no clue on what it might be, but maybe related to http://sourceware.org/ml/glibc-bugs/2006-11/msg00099.html ? I just found it googling for the exact error, and seems too much coincidence to burp on the same assertion... That leads to http://sourceware.org/bugzilla/show_bug.cgi?id=3610 and is reported as an invalid bug on glibc; rest of the bug reporting sounds like klingon to me, but might help.
