On January 5, 2002 6:13 am, Kingsly John wrote: > The problem is with the KDE 2.2.2 rpms (from germany???) .. check the > archives for details of the thread ... something to do with the clipboard > too I believe.
I didn't install from RPM. I'm using Debian testing. However, I have isolated the problem, and I'm not sure if its an licq issue or not, so some assistance from a knowledgeable developer would be appreciated. (I have tinkered with other GUI toolkits, but never Qt or KDE) Running with the HighColor Default KDE style, gdb produces the following backtrace immediately after the SIGSEGV occurs: #0 0x41424a9d in HCStyle::drawKMenuItem () from /usr/lib/hcstyle.so #1 0x40c651e7 in KMenuBar::drawContents () from /usr/lib/libkdeui.so.3 #2 0x4057a385 in QFrame::paintEvent () from /usr/lib/libqt-mt.so.2 #3 0x40550f42 in QWidget::event () from /usr/lib/libqt-mt.so.2 #4 0x404b4b87 in QApplication::notify () from /usr/lib/libqt-mt.so.2 #5 0x40e03da4 in KApplication::notify () from /usr/lib/libkdecore.so.3 #6 0x404847ea in QETWidget::translatePaintEvent () from /usr/lib/libqt-mt.so.2 #7 0x40480383 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.2 #8 0x4047f460 in QApplication::processNextEvent () from /usr/lib/libqt-mt.so.2 #9 0x404b70bf in QApplication::enter_loop () from /usr/lib/libqt-mt.so.2 #10 0x40486a87 in QApplication::exec () from /usr/lib/libqt-mt.so.2 #11 0x40237df0 in CLicqGui::Run (this=0x80cdcc8, _licqDaemon=0x80caad8) at licqgui.cpp:345 #12 0x402361a8 in LP_Main (_licqDaemon=0x80caad8) at licqgui.cpp:155 #13 0x40235ec1 in LP_Main_tep (p=0x80caad8) at /usr/data/cvs/licq/include/licq_plugin.h:119 #14 0x4002feca in pthread_start_thread () from /lib/libpthread.so.0 #15 0x4002ff11 in pthread_start_thread_event () from /lib/libpthread.so.0 However, changing the style used by licq, like this: ./licq -p kde-gui -- --style default causes it to run without a hitch. So is LICQ doing something wrong, or is KDE's Highcolor style buggy? Oh, and there is one other bug - as far as I can tell, licq's GUI plugins don't properly ignore KDE or Qt arguments, and try to parse them as if they were arguments to the plugin. (Though they are also properly interpreted by their intended recipient) -- Nick Pilon _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
