Bug 883155 - empathy/telepathy won't connect to IRC when on lame IPv6 connectivity
empathy/telepathy won't connect to IRC when on lame IPv6 connectivity
Product: Fedora
Classification: Fedora
Component: telepathy-idle (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks: dualstack
  Show dependency treegraph
Reported: 2012-12-03 17:17 EST by Pavel Šimerda (pavlix)
Modified: 2015-07-15 10:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 15:10:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description Pavel Šimerda (pavlix) 2012-12-03 17:17:05 EST
When IPv6 connectivity fails in the provider network, Empathy will not connect to IPv6-enabled IRC networks like freenode. I suspect the problem *might* be in not
trying to connect to other that the first address returned by getaddrinfo().

See the following document:

Comment 1 Pavel Šimerda (pavlix) 2012-12-03 17:17:53 EST
The expected behaviour is to use the still working IPv4 connectivity to connect to the IPv4 address.
Comment 2 Pavel Šimerda (pavlix) 2012-12-03 17:23:08 EST
I finally connected (after some time), that means the reproducability won't be 100%. The problem is that IPv6 is getting *dropped* here, so the most basic way to
reach the other host via IPv4 is to let the IPv6 time out.
Comment 3 Fedora End Of Life 2013-07-03 15:59:16 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2013-07-31 15:10:34 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 5 Pavel Šimerda (pavlix) 2013-08-01 06:02:27 EDT
Needs retest but never received any answer.
Comment 6 Jan Kurik 2015-07-15 10:55:32 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:

Note You need to log in before you can comment on or make changes to this bug.