-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 07 July 2002 03:30 pm, Ilya Konstantinov wrote:
> Can anyone please run licq through valgrind to find that memory
> corruption instead of making workarounds?
Perhaps it may be with this... but it is coming from qt libraries:
==8813== Threa
Hello
I am running Mandrake 8.2 with KDE 3.102
After installing LICQ 1.1.0
I get this on start up
[dave@PCBOOK dave]$ licq
19:28:27: [WRN] Licq: Ignoring stale lockfile (pid 30149)
19:28:27: [ERR] Unable to load plugin (qt-gui ) :
/usr/lib/licq/licq_qt-gui.so: undefined symbol: _ZN7QWidget5even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The latest CVS now has a more complete Server Side List implementation. If
you are currently using Server Side List, you will need to do the following
steps if you wish to export your current list (groups and users in those
groups) to the server:
On Sunday 07 July 2002 12:11, Stefan Seifert wrote:
> gfdsa wrote:
> >On Saturday 06 July 2002 13:53, Stefan Seifert wrote:
> >>gfdsa wrote:
> Oh sorry, was my mistake. I should start to sleep from time to time...
> It should be KDE_MALLOC=0 licq
> not KMALLOC
>
> Hope this works better
>
>
>
st
On Sun, Jul 07, 2002 at 11:11:50AM +0200, Stefan Seifert wrote:
> Oh sorry, was my mistake. I should start to sleep from time to time...
> It should be KDE_MALLOC=0 licq
> not KMALLOC
Can anyone please run licq through valgrind to find that memory
corruption instead of making workarounds?
(Yes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I have combined all reliability patches (patch0-3) recently posted to
> this list by Tim and Juan rediffed against the lastest CVS. I wonder
> when will those patches be committed to the CVS?
meantime use it in your local tree, keeping it update is
Hi all,
I have combined all reliability patches (patch0-3) recently posted to this
list by Tim and Juan rediffed against the lastest CVS. I wonder when will
those patches be committed to the CVS?
--- include/licq_buffer.h Mon May 06 01:51:26 2002 Revision: 1.6
+++ include/licq_buffer.h Thu Ju
gfdsa wrote:
>On Saturday 06 July 2002 13:53, Stefan Seifert wrote:
>
>
>>gfdsa wrote:
>>
>>
>>>Hi.
>>>
>>>Does anyone can give me a clue?
>>>It will be very appreciated
>>>
>>>
>>>
>
>
>
>>I had the same problem. In the Bugtracker on Sourceforge.net I found the
>>hint to start licq
On Saturday 06 July 2002 14:32, Ilya Konstantinov wrote:
> On Sat, Jul 06, 2002 at 12:53:36PM +0200, Stefan Seifert wrote:
> > gfdsa wrote:
> > >Hi.
> > >
> For me, XIM-related crashes started appearing only when I upgraded to
> Qt 3.0.4 and KDE 3.0.2. Since they don't appear in a Qt-only licq, I
