-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi...
Ok, this is the second time this has happened, so I'm reporting it as,
well, maybe a bug, maybe a flaw or oversight. I'm not even sure what's
causing this.
I run my Licq continuously. Normally it stays connected continuously.
This morning I got up to find KDE (2.2.1) attempting to display a
never-ending stream of Licq "Error" boxes, as Licq was apparently
making many of these boxes every second. (Seems kind of
counterproductive, if you ask me. :) I do not know what the error was,
as I was unable to see these boxes. (GUI was unresponsive, all of its
time being taken up with these error dialogs, so I switched to a
console and used "killall".)
Now here's such diagnostic info as I can gather, without having a
backtrace, core, or anything like that. (It didn't crash, I killed it.)
Licq & KDE-gui are version 1.1.0/SSL, compiled 18 Feb 2002. FYI, when
I hit "Statistics" just now, it said last reset was Jan 1, 2001 or
something -- I know it was Jan, 2001 but not sure of the day. Second
time I pulled up Stats, it says I reset them 3 minutes ago, but I did
not -- I hit "OK", not "Reset". Is this behavior as intended?
Licq was started Mar 25, 23:42, according to licq.pid. I killed it
about 06:16 today (April 22). log.errors is 183MB in size!
(Previously, this file filled up my /home partition; this time, there
is 573M left.) I do not have any ulimit file-size restrictions on this
user's account. Last 20 lines of log.errors:
06:07:38: 0x85172a8 Command: 2 SubCommand: 0 Sequence: 33683
SubSequence: 33601: Uin: 0
06:07:38: 0x41696bd0 Command: 2 SubCommand: 0 Sequence: 34940
SubSequence: 34858: Uin: 0
06:07:38: 0x4168dd60 Command: 2 SubCommand: 0 Sequence: 35224
SubSequence: 35142: Uin: 0
06:07:38: 0x4166a7a8 Command: 2 SubCommand: 0 Sequence: 35263
SubSequence: 35181: Uin: 0
06:07:38: 0x416b8090 Command: 2 SubCommand: 0 Sequence: 35743
SubSequence: 35661: Uin: 0
06:07:38: 0x41666990 Command: 2 SubCommand: 0 Sequence: 36411
SubSequence: 36329: Uin: 0
06:07:38: 0x416cedd0 Command: 2 SubCommand: 0 Sequence: 36438
SubSequence: 36356: Uin: 0
06:07:38: 0x416078f8 Command: 2 SubCommand: 0 Sequence: 36642
SubSequence: 36560: Uin: 0
06:07:38: 0x41691708 Command: 2 SubCommand: 0 Sequence: 36661
SubSequence: 36579: Uin: 0
06:07:38: 0x416bd5c8 Command: 2 SubCommand: 0 Sequence: 37382
SubSequence: 37300: Uin: 0
06:07:38: 0x416af380 Command: 2 SubCommand: 0 Sequence: 37544
SubSequence: 37462: Uin: 0
06:07:38: 0x4168bcb8 Command: 2 SubCommand: 0 Sequence: 37549
SubSequence: 37467: Uin: 0
06:07:38: 0x41648b30 Command: 2 SubCommand: 0 Sequence: 37771
SubSequence: 37689: Uin: 0
06:07:38: 0x41631d58 Command: 2 SubCommand: 0 Sequence: 37774
SubSequence: 37692: Uin: 0
06:07:38: 0x416ff5a8 Command: 2 SubCommand: 0 Sequence: 37984
SubSequence: 37902: Uin: 0
06:07:38: 0x4164b8a0 Command: 2 SubCommand: 0 Sequence: 39085
SubSequence: 39003: Uin: 0
06:07:38: 0x8590eb8 Command: 2 SubCommand: 0 Sequence: 39326
SubSequence: 39244: Uin: 0
06:07:38: 0x418359b0 Command: 2 SubCommand: 0 Sequence: 9410
SubSequence: 39260: Uin: 0
06:07:38: 0x416cf448 Command: 2 SubCommand: 0 Sequence: 9532
SubSequence: 39382: Uin: 0
06:07:38: 0x41986350 Command: 2 SubCommand: 0 Sequence: 3489
SubSequence: 39789: Uin: 0
As an experiment, I made log.errors read-only and started Licq; it
printed an error to the console about not being able to write to this
file, but otherwise behaved normally. I *thought* I had set Licq only
to log errors and warnings -- in fact I had, but I notice these
settings are not saved when Licq does "Save settings" or exits; the
only way to get them to "stick" is to set them via command line when
starting Licq. (I find this counter-intuitive, since they may be
toggled via the System menu -- I tend to assume that things I can
change by menu, like "Show offline users", will remain set.)
I'm not sure what other info can be of use here, nor am I able to
reproduce this problem except by letting Licq run for several weeks!
(The weird behavior, naturally, happens while I'm asleep or otherwise
absent.) In case it will be useful to someone, I have bzipped the
error log (25M after compression!) and attached it to this message.
Ahh-- no, just kidding, but I'll be glad to send it to a developer if
requested. :)
I have not built a more recent version on the grounds of, "If it ain't
broke, don't fix it." Is this broke? Would a more recent version fix
it? Aside from failing mysteriously every month or two, Licq has
worked very well since version 1.1.0 and I'm *still* very happy with it!
- --
// Carl Hudkins :: ICQ 5723399 :: PGP 50238D9E
//
// "When two hydrogen atoms love each other very much,
// they bond with an oxygen atom..." --Trance Gemini, Andromeda
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8w/OllLp/6lAjjZ4RAvFkAKDJeVQFj6MU53AAapSAXIWz4V+TYwCdGTFf
M+6IY2APSIoFBDajlgqz6pM=
=VCLr
-----END PGP SIGNATURE-----
_______________________________________________
Licq-main mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-main
