I had the same problem with licq-cvs on FreeBSD 4.4/XFree 4.1.0/KDE 2.2.2.
here is the backtrace:
[Switching to process 42146, thread 2]
Program received signal SIGSEGV, Segmentation fault.
0x2897c28d in _XimParseStringFile () from /usr/X11R6/lib/libX11.so.6
(gdb) bt
#0 0x2897c28d in _XimParseStringFile () from /usr/X11R6/lib/libX11.so.6
#1 0x2897acd1 in _XimCreateDefaultTree () from /usr/X11R6/lib/libX11.so.6
#2 0x2897ada4 in _XimLocalOpenIM () from /usr/X11R6/lib/libX11.so.6
#3 0x2897a07f in _XimOpenIM () from /usr/X11R6/lib/libX11.so.6
#4 0x289798b7 in _XimRegisterIMInstantiateCallback () from
/usr/X11R6/lib/libX11.so.6
#5 0x2895243b in XRegisterIMInstantiateCallback () from
/usr/X11R6/lib/libX11.so.6
#6 0x284fda09 in qt_init_internal () from /usr/X11R6/lib/libqt2.so.4
#7 0x284fdd29 in qt_init () from /usr/X11R6/lib/libqt2.so.4
#8 0x2853b528 in QApplication::construct () from /usr/X11R6/lib/libqt2.so.4
#9 0x2853b3cd in QApplication::QApplication () from
/usr/X11R6/lib/libqt2.so.4
#10 0x28301d30 in CLicqGui::CLicqGui (this=0x28295164, argc=1,
argv=0x80ba0c0) at licqgui.cpp:211
#11 0x283014f7 in LP_Main (_licqDaemon=0x80d5c00) at licqgui.cpp:141
#12 0x2830121d in LP_Main_tep (p=0x80d5c00)
at /usr/home/chirin/tmp/licq-cvs/licq/include/licq_plugin.h:119
#13 0x28213ea7 in _thread_start () from /usr/lib/libc_r.so.4
#14 0x0 in ?? ()
It seems that the problem is related to XIM in some way. I managed to get
licq with qt-plugin running by entering the following:
# licq -- -noxim
KDE plugin still doesn't work - it keeps writing the following:
# licq -pkde-gui -- -noxim
X Error: BadAtom (invalid Atom parameter) 5
Major opcode: 20
licq in free(): warning: junk pointer, too high to make sense.
X Error: BadAtom (invalid Atom parameter) 5
Major opcode: 20
licq in free(): warning: junk pointer, too high to make sense.
...
And so on. Any ideas?
> Date: Sat, 15 Dec 2001 15:32:04 -0500 (EST)
> From: Brad Laue <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Licq-main] Licq 1.1 daily QT-GUI + FreeBSD
>
> This problem has existed since 1.0.4 came out, essentially; since qt-gui
> 1.0.4 is in use with the 1.1 dailies, the problem still exists.
>
> licq -p qt-gui hangs as soon as the qt-gui plugin loads (exactly at this
> point) and proceeds to use 100% CPU until killed with a signal 9. Running
> truss+ktrace reveals nothing specifically going wrong. It seems to be
> waiting for something it never gets.
>
> This problem exists on FreeBSD 4.4-RELEASE and 4.4-STABLE as of four days
> ago, using QT 2.3.1, gcc 2.95.3, gcc 3.0.2, and a nightly gcc snapshot.
>
> Any ideas on fixing this?
_______________________________________________
Licq-main mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-main
