Ticket #19 (closed defect: Duplicate)

Opened 7 years ago

Last modified 22 months ago

Persistent unread messages at startup

Reported by: alexisb Owned by:
Priority: normal Milestone:
Component: message Version: 1.0.*
Keywords: Cc:

Description

When I start Licq, I have some already read messages that are still marked as unread (also for system messages). I have to re-read each of them each time I start licq (latest stable) which is quite boring... I got a pretty defensive firewall on my computer, perhap's it is related (but all went fine before).

-- Alexis

Change History

Changed 7 years ago by nobody

Logged In: NO

I'm experiencing the same problem. It only started a few days ago. A friend is also experiencing the same. Maybe it's a change to ICQ network protocols not sending proper ACKs? It only seems to happen to messages that were sent to me offline.

Changed 7 years ago by nobody

Logged In: NO

same problem here, it's also happen on my windows box with me running miranda icq also... I really hate to ruin a machine by putting mirabilis icq on it to flush the messages out :(

Changed 7 years ago by oosterlo

Logged In: YES user_id=163587

I also had this problem. But after I logged into my icq account once with the regular Windows client, the messages finally disappeared..

Changed 7 years ago by nobody

Logged In: NO

Me and my friend also have the same problem. Other my friend (in the same office, behind the same firewall haven't noticed it). We all have the same server, the same firewall and the same ICQ server (and offcourse the same licq version (1.0.3/SSL)). The only difference is that we are using KDE and the other guy uses Enlightment, but I can not imagine it might depend on it. I would also say (as the other "nobody") that ICQ specification has changed. :-( But I sometimes was also succesfull in solving the problem by using of other client (kicq)...

Changed 7 years ago by dbr

  • status changed from assigned to closed

Logged In: YES user_id=36808

Closed, as this bug is a duplicate of bug #413771

Note: See TracTickets for help on using tickets.