After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764435 - Pre-configured "Gnome" network fails to connect, but custom irc.gimp.org works
Pre-configured "Gnome" network fails to connect, but custom irc.gimp.org works
Status: RESOLVED DUPLICATE of bug 762335
Product: polari
Classification: Applications
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-31 20:41 UTC by Eduardo Silva
Modified: 2016-04-01 13:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Eduardo Silva 2016-03-31 20:41:08 UTC 
I was in two rooms at previously (polari 3.18) custom configured irc.gnome.org.

Removed that server, and proceded to enter a new #gnome channel using the pre-configured "Gnome" network. A small icon appeared besides the network telling it failed to connect.

Re-entered #gnome using custom irc.gimp.org address and it worked.
Comment 1 Florian Müllner 2016-04-01 10:13:56 UTC 
(In reply to Eduardo Silva from comment #0)
> Removed that server, and proceded to enter a new #gnome channel using the
> pre-configured "Gnome" network.

If a network consists of multiple servers, we just pick the first one (at least until we resolve bug 762335). Unfortunately in the case of "GNOME", that's irc.eagle.y.se, which ceased to work (temporarily?).

Andrea, do you know if that server is expected to come back up eventually, or should we adjust the server list?
Comment 2 Andrea Veri 2016-04-01 13:26:58 UTC 
That server has been down for around one day but it should be back up now. (next time we'll make sure to remove it from rotation)
Comment 3 Florian Müllner 2016-04-01 13:34:38 UTC 
In that case I don't think there's anything actionable beyond bug 762335 here, so closing as duplicate.

*** This bug has been marked as a duplicate of bug 762335 ***