[136] in im locker bugs
licq broken on 9.3 linux
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Tue Aug 10 18:49:39 2004
To: bug-im@mit.edu
From: Ken Raeburn <raeburn@MIT.EDU>
Date: Tue, 10 Aug 2004 18:49:26 -0400
"olc answers" tells people to use "athrun im licq", but on a 9.3.8
Athena Linux box:
% athrun im licq
attach: /afs/sipb.mit.edu/project/im attached to /mit/im for filesystem im
attach: /afs/athena.mit.edu/contrib/crypto attached to /mit/crypto for filesystem crypto
/afs/sipb.mit.edu/project/im/bin/licq.real: error while loading shared libraries: libssl.so.0.9.6: cannot open shared object file: No such file or directory
It probably just needs a "i386_rhel3" link in the crypto locker,
though all that software looks old enough (2001-2002) that it could
probably stand to be updated.
On Solaris, logged in over ssh from a non-Athena system, it seems to
start mostly okay:
% athrun im licq
attach: /afs/sipb.mit.edu/project/im attached to /mit/im for filesystem im
attach: /afs/athena.mit.edu/contrib/crypto attached to /mit/crypto for filesystem crypto
18:29:05: [WRN] Unable to create fifo:
Invalid argument.
but creates a window saying
Before you can start using LICQ you need to register a use...
You can either register an existing UIN on create a new acc...
Both messages run off the right side of the window (I didn't set the
window size), and the Prev/Next/Cancel buttons look like they hang
down a little past the bottom edge of the window, though the text is
fully visible (but wouldn't be if it had any descenders).
Manually resizing the window does bring everything fully into view.
It spews some messages about assertion failures:
Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkLabel'
Gtk-CRITICAL **: file gtklabel.c: line 260 (gtk_label_set_text): assertion `GTK_IS_LABEL (label)' failed.
Gtk-CRITICAL **: file gtkwidget.c: line 3310 (gtk_widget_set_sensitive): assertion `widget != NULL' failed.
I got five sets of these messages while I ran licq for a short time.
I didn't go through with the registration, I was just curious how
current the instructions and software were.
Ken
