Opened 12 years ago

Last modified 10 years ago

#2251 new defect

SILC stops working after network reconnect

Reported by: semb Owned by: elb
Milestone: Component: SILC
Version: 2.0.2 Keywords:
Cc:

Description

On launching Pidgin I can click on a SILC buddy and send IMs to them. If I lose my network connection, and then re-connect, without restarting Pidgin then any IMs I send to a SILC buddy get silently dropped. Also my buddy cannot send messages to me.

Disabling and re-enabling the SILC account fixes things, as well as restarting Pidgin.

I am running on Windows XP.

Change History (8)

comment:1 Changed 12 years ago by seanegan

  • Component changed from libpurple to SILC
  • Owner set to elb

comment:2 follow-up: Changed 12 years ago by datallah

I can recreate this. When this occurs, I'll receive error popups saying "Error during rekey with s.slash0.net: Unexpected error occurred" (which comes directly from the SILC library) every few minutes until I disconnect and reconnect the account.

comment:3 in reply to: ↑ 2 ; follow-up: Changed 11 years ago by nosnilmot

Replying to datallah:

I can recreate this. When this occurs, I'll receive error popups saying "Error during rekey with s.slash0.net: Unexpected error occurred" (which comes directly from the SILC library) every few minutes until I disconnect and reconnect the account.

Do you still get this error using SILC toolkit 1.1.5 ?

I don't see any activity from silc after network down/up at all, and messages I send disappear completely, never showing up in my conversation window. I suspect this might be a SILC toolkit bug.

comment:4 in reply to: ↑ 3 Changed 11 years ago by datallah

Replying to nosnilmot:

Do you still get this error using SILC toolkit 1.1.5 ?

Yes.

I don't see any activity from silc after network down/up at all, and messages I send disappear completely, never showing up in my conversation window. I suspect this might be a SILC toolkit bug.

That sounds likely.

comment:5 Changed 11 years ago by RichieB

This is a duplicate of #1305 (which was illegitimately closed and I reopened as #3424). And yes, I still have this problem on Windows XP using Pidgin 2.3.1.

comment:6 Changed 10 years ago by bernmeister

Any chances this has been resolved? Anyone still experiencing this with Pidgin 2.5.8?

comment:7 Changed 10 years ago by RichieB

I switched to Pidgin on Max OS X, which does not seem to have this issue. I can test on Windows Vista if needed.

comment:8 Changed 10 years ago by bernmeister

Yes, please test on Vista (and/or XP if possible).

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!