ports/86354: kopete exits on startup (possible thread/KSE problem)
Daniel O'Connor
doconnor at gsoft.com.au
Tue Sep 20 00:20:18 UTC 2005
>Number: 86354
>Category: ports
>Synopsis: kopete exits on startup (possible thread/KSE problem)
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Sep 20 00:20:16 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Daniel O'Connor
>Release: FreeBSD 7.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD inchoate.localdomain 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu
Sep 15 12:51:11 CST 2005
darius at inchoate.localdomain:/usr/src/sys/i386/compile/INCHOATE i386
>Description:
kopete exits on startup with..
[inchoate 9:21] ~ >kopete
[inchoate 9:21] ~ >Fatal error 'kse_exit() failed for system scope thread' at
line 1212 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22)
Fatal error 'Thread 0x8100200 has called pthread_exit() from a destructor.
POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 98 in
file /usr/src/lib/libpthread/thread/thr_exit.c (errno = 3)
Further to this, I found that I was pulling in libpthread.so.1 and
libpthread.so.2. Qt had the former so I tried rebuilding it, but uic gets
stuck
when building libboxeditor.cpp..
/usr/tmp/work/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.4/bin/uic
-L /usr/tmp/work/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.4/plugins
listboxeditor.ui -i listboxeditor.h -o listboxeditor.cpp
ktrace shows..
12256 uic CALL kse_release(0xbfbfce0c)
12256 uic RET kse_release -1 errno 22 Invalid argument
12256 uic CALL kse_release(0xbfbfce0c)
12256 uic RET kse_release -1 errno 22 Invalid argument
on and on.
I tried copying the boostrap version of uic and libqtmt out of the build tree
just in case it was using the system ones by accident but no change.
With kopete using the bootstrap version of libqtmt it starts, but appears to
stall when connecting to Jabber after it prints..
Mutex unlock failure: Operation not permitted
ktrace shows it is doing *nothing*, although ctrl-t shows it is in the
running state, then ksesigwait..
I can't kill it normally either, I have to -9 it.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list