[Licq-main] problems with sending over server (CVS)
Hi 2 All! I complied the latest CVS-version on my SuSE-Linux computer (not behind a firewall) and I noticed (as with older licq 1.1.0 CVS-Snapshots too), that after an unpredictable time no messages - sent over server - won't arrive any recipient anymore. That appears to everybody, no matter what icq he has. If I disconnect and than connect to the icq-server again, all messages will arrive fine for a while... but only for a while. That could be 10 minutes or an hour. Then I have to disconnect and connect again. If everybody had icq 2002 or licq 1.1.0 on his client, it would be no problem, because these clients are able to handle direct connections between firewalls. But to someone who has icq2001 behind a firewall for example I MUST send indirect over the server (I know the reason is the new protocol). And it is very nerving to ask peoples always, if he gets my messages you know?. Is there anybody with the same problem? - Is it a bug from licq? - Or must I install ipv6 on my linux computer (i noticed, that licq generates ipv6 packets)? Generally I think it's not a problem with licq.. rather with AOL ;) The question is, what can I do against it? THX a lot for helping!!! Bye, Andi ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] More suggested features
Mathias Bondeson wrote: ICQ SMS capability: It should be possible to send and receive SMS messages from LICQ. This has been implemented in several other clients, so it shouldn't be so hard to implement in LICQ either. If ya can go ahead, devels are working on all non-implemented features Selective invisible listing: It should be possible to see invisible users in the list, also when you are not on their visible lists. As far as this can be done, it's allready done. It would also be nice if there were a different symbol for users which are invisible and do not have visible-listed and those who have visible-listed the LICQ user. Is there a diffence by being in invisible or invisible? :)) One Display-field different from the Alias-field in the Userinfo: It would be nice to be able to refresh the userinfo without changing the labeling of the contact in the contact list. And as it would be nice to have an Alias field and to be able to update that, the best solution would be to have a separate Display field, as in ICQ. Idea, i'll send this to devel list in a sec, i guess their reply: First complete the 2001b protocol implementation. submit this to the sourceforge feature request page... Expanded userinfo: It would be nice to be able to view all userinfo, including personal interests and so on, from LICQ. Phone info: It would be nice to be able to receive phone info from those ICQ users which have me on their ICQ lists. ICQ Phone: It would be nice to have the ICQ Phone functionality in LICQ. Don't know how easy this is to implement, though. Working on it, lot of work to be done :) Greets, Arjen H ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] problems with sending over server (CVS)
On Thursday 14 March 2002 08:00 am, [EMAIL PROTECTED] wrote: I complied the latest CVS-version on my SuSE-Linux computer (not behind a firewall) and I noticed (as with older licq 1.1.0 CVS-Snapshots too), that after an unpredictable time no messages - sent over server - won't arrive any recipient anymore. That appears to everybody, no matter what icq he has. If I disconnect and than connect to the icq-server again, all messages will arrive fine for a while... but only for a while. That could be 10 minutes or an hour. Then I have to disconnect and connect again. If everybody had icq 2002 or licq 1.1.0 on his client, it would be no problem, because these clients are able to handle direct connections between firewalls. But to someone who has icq2001 behind a firewall for example I MUST send indirect over the server (I know the reason is the new protocol). And it is very nerving to ask peoples always, if he gets my messages you know?. I have not had any problems with sending messages through the server at all. Perhaps you can show a packet where it works, and then the next packet where it doesn't work? Is there anybody with the same problem? - Is it a bug from licq? - Or must I install ipv6 on my linux computer (i noticed, that licq generates ipv6 packets)? Generally I think it's not a problem with licq.. rather with AOL ;) The question is, what can I do against it? licq doesn't generate ipv6 packets at all. It only generates a packet with the aim protocol and lets the kernel put the headers on it. Jon ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
RE: [Licq-main] problems with sending over server (CVS)
I've been getting the same behaviour from licq for the last little while (also using CVS compiled version from a few weeks ago). It seems that none of my messages will ever go through after a little while... I am behind a firewall (at work), but no policies have changed in a long time, and it used to work. sounds like mirabilis messing with the protocol again. --mike ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] More suggested features
Here is another feature that could be nice: a switch to make LICQ play when a message arrives... but not play again until there is no ICQ activity and then wait 2-3 minutes more. What do you think? Gunnar ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
[Licq-main] licq segm fault (cvs, today)
Hi all I've seen this come by before, just thought I'd add my own experiences to help fix this problem I get licq from cvs using update -D today, whenever I try. Since about 4th of March, I'm getting segmentation faults when starting the resulting binaries. This is what I see: licq: no process killed 20:08:20: [WRN] Licq: Ignoring stale lockfile (pid 6205) 20:08:20: [INI] Owner configuration. 20:08:20: [INI] User configuration. 20:08:20: [INI] Loading 86 users. 20:08:20: [INI] Loading saved auto-responses. 20:08:20: [INI] Loading utilities. 20:08:20: [TCP] Local TCP server started on port 32834. 20:08:20: [INI] Opening fifo. 20:08:20: [INI] Spawning daemon threads. 20:08:20: [INI] Starting plugin Qt GUI (version 1.1.0). 20:08:20: [INI] Attempting to load en Qt-GUI translation. 20:08:20: [INI] Qt GUI configuration. QFont::setRawMode(): Invalid XLFD: 6x13 QFont::setRawMode(): Invalid XLFD: 6x13 20:08:20: [INI] Geometry configuration (1019, 19) (128 x 711) 20:08:21: [INI] Applying pli skin. Licq Segmentation Violation Detected. Backtrace: /local/src/licq-cvs/licq/src/licq(licq_handle_sigsegv+0x84) [0x8097d24] /lib/libpthread.so.0 [0x401273ab] /lib/libc.so.6 [0x401e47c8] /usr/local/lib/licq/licq_qt-gui.so(__13CUserViewItemP7ICQUserP13CUserViewItem+0xb9) [0x40377839] /usr/local/lib/licq/licq_qt-gui.so(updateUserWin__11CMainWindow+0x384) [0x4034d7c4] /usr/local/lib/licq/licq_qt-gui.so(setCurrentGroup__11CMainWindowi+0x1b5) [0x4034e335] /usr/local/lib/licq/licq_qt-gui.so(updateGroups__11CMainWindow+0x868) [0x4034eba8] /usr/local/lib/licq/licq_qt-gui.so(__11CMainWindowP10CICQDaemonP14CSignalManagerP12CQtLogWindowbPCcT5P7QWidget+0x190f) [0x4034ab8f] /usr/local/lib/licq/licq_qt-gui.so(Run__8CLicqGuiP10CICQDaemon+0xc9) [0x40348229] /usr/local/lib/licq/licq_qt-gui.so(LP_Main+0x49) [0x40346069] /usr/local/lib/licq/licq_qt-gui.so(LP_Main_tep+0x1d) [0x40345d6d] /lib/libpthread.so.0 [0x401249c7] /lib/libc.so.6(__clone+0x3a) [0x402a576a] Attempting to generate core file. this is on a mandrake 8.1 system which is kept reasonably up to date and it has the KDE 2.2.2 packages on them from the kde site. I can provide more detailed information if someone wants it... I'll go back to a version that can actually start up ;-) Simon ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] problems with sending over server (CVS)
On Wed, 13 Mar 2002 13:21:45 -0500 James [EMAIL PROTECTED] wrote: Michael Wojcikiewicz wrote: I've been getting the same behaviour from licq for the last little while (also using CVS compiled version from a few weeks ago). It seems that none of my messages will ever go through after a little while... I am behind a firewall (at work), but no policies have changed in a long time, and it used to work. sounds like mirabilis messing with the protocol again. --mike Hello, I remember writing about having this problem maybe 3 weeks ago. but I think I was dismissed like an old crazy lady..LOL.. But anyway I too can send mesg. for a little while then after disconnect and riconnect, it will start , again, it is a viciuos circle.. it used to work fine and all of the sudden ...??? who knowes what happened.. I use SuSE Linux 7.3 and licq version 1.1.0/SSl QT GUI plugin version 1.04... This problem has been reported on the GnomeICU list several times. I believe they found the problem to be that they were ignoring a message from the ICQ server concerning messages being sent too fast. Perhaps this is the case here too? ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] More suggested features
From: DeXteR [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Mathias Bondeson [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Licq-main] More suggested features Date: Wed, 13 Mar 2002 17:07:12 +0100 Mathias Bondeson wrote: snip Selective invisible listing: It should be possible to see invisible users in the list, also when you are not on their visible lists. As far as this can be done, it's allready done. I posted a question about this very same feature about a month ago, and was told that it cannot be implemented because it is a behaviour determined by the ICQ server, and not the client. Can someone please clarify if this feature can be implemented by the client and is it implemented in Licq ? Sincerely, Yosi _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
