negative uin (uin# overflow?)

[nobody]

I'm running linux 2.4.10; licq version 1.0.3 (last stable); X server version 4.1.0 on enlightenment. I have Slackware 8.0. I use the qt-gui interface for licq. In my contact list, recently, I see an negative uin#. It show me as an overflowed (?) (signed) long int... (Basic) doubt is a new bug? The licq don't do many things with this entry...

[wstephenson]

Logged In: YES user_id=257393

I've just seen this too, from a newly created account, kernel 2.4.7 on SuSE 7.2 & KDE 2.2.1.

[nobody]

Logged In: NO

yeah I get that too on accouncts with a UIN higher than, 100,000,000. You can add the UIN and send to it but when receiving messages it shows as the overflow number.

[nobody]

Logged In: NO

opps I should be a little more descriptive, I am using 1.0.3 with the console plug in. I can add the long UIN to my list it is a problem only when receiving messages from the long UIN, I guess it must be a mistyped class or something, maybe the class in returning back long instead of double long?? Dunno, I had a quick look at the source but couldn't see anything.

[nobody]

Logged In: NO

there is a hack in code icqd-udp.cpp to fix backward UIN's in version 99b. However this screws up the big UIN, on receive ONLY for other version. I haven't tested it with 99b at the other end of a connection. but this fixes the problem for UIN's over 100,000,000 -- Comment out the following lines, make and re-install. restart Licq, and your away.

(NOTE: I'm not a contributor, so I can't patch the actual source, and it it's totally tested, but worked for me YMMV.)

//if (nUin > 0x07FFFFFF) // { // nUin = ((nUin & 0x000000FF) << 24) + ((nUin & 0x0000FF00) << 8) + // ((nUin & 0x00FF0000) >> 8) + ((nUin & 0xFF000000) >> 24); //# }

Russell Smith

[nobody]

Logged In: NO

Me, too. Debian woody licq-ssl 1.0.3

[nobody]

Logged In: NO

i got the same problem

[nobody]

Logged In: NO

We have the same problem - a user with a number greater than 100,000,000 is sending from icq2001b(win98) to licq(redhat7.2)

the message gets to the user with licq but cannot send back to user at other end because the uin is incorrect because of the overflow

so until this error is corrected millions of people will not be able to

communicate back and forth

(the number of people using ICQis now over 148 million) hence about 1/3 of the people cannot communicate till this is solved

[daywalker]

Logged In: YES user_id=1342

UPGRADE LICQ CVS!!!!! read http://www.rhrk.uni-kl.de/~dmuell/licq/