Bug 48922

Summary:	IRC stops working when switching from wireless to LAN
Product:	Telepathy	Reporter:	shaneonabike <shanebill>
Component:	idle	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	IRC Log file

Description shaneonabike 2012-04-19 07:38:58 UTC

Created attachment 60313 [details]
IRC Log file

[I realize this might be strange but it happens a lot and not with other
accounts like Jabber, etc]

In Ubuntu 11.x

* Connect to IRC on Wifi
* Plug in LAN later on and IRC stops working

Would there be any way to detect a change in the connect and re-connect the IRC
channel. It's not clear to me why this stops working but it happens on a
regular basis.

It also happens the other way around :/

I removed the connection at 10:20 so after that it looks like there is a
msg_queue timeout being received. I wonder if it receives that if it couldn't
just force a new connect.

The only way I have ever been able to re-invoke this is to put myself offline
and then bring myself back online for IRC to properly reconnect.

(Originally reported here: https://bugzilla.gnome.org/show_bug.cgi?id=674262 - they told me to report it here).

Comment 1 shaneonabike 2012-04-19 07:40:29 UTC

Whoops I neglected to add that this is happening specifically when I am using Empathy 3.2.0.1. Sorry for not putting that in my original post.

Comment 2 GitLab Migration User 2019-12-03 20:09:45 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-idle/issues/37.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.