On Thu, 7 Mar 2002, John Steele Scott wrote: > One point to add is that if I have a network log window open, when the gui > "freezes up" like that, the information in the network log scrolls up, but no > new information comes in (i.e. only white space scrolls in). Then once the > gui starts responding again, the new network log messages appear where they > should be (i.e. the white space is replaced by characters). This seems to > indicate to me that licq is tickling a bug in one of QT or KDE. I'd guess > it's in KDE, but it should be simple enough to find out . . . if this gets > unbearable enough I'll just recompile it without kde enabled and test that.
I get the same problem without KDE installed. I'm using debian with: libqt3 3.0.1-1 gcc 2.95.4-10 and just a basic fvwm2 window manager without KDE or Gnome. Hope this helps. Thanks, Tom _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
