Bug 1006615

Summary: IPv6 <-> IPv4 mismatch when subscribing to multicast (upstream patch)
Product: [Fedora] Fedora Reporter: Tyson Whitehead <twhitehead>
Component: glib2Assignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:22:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tyson Whitehead 2013-09-10 22:37:53 UTC
Description of problem:

There's a bug in glibc that causes gstreamer to fail when trying to use multicast address.  A patch was created and it was fixed in glibc 2.35.3

https://bug687092.bugzilla-attachments.gnome.org/attachment.cgi?id=231388

It would be great if we could apply this patch to our current glibc.

Version-Release number of selected component (if applicable):

< 2.35.2

How reproducible:

Always

Steps to Reproduce:

1. don't explicitly disable IPv6, and
2. from a terminal run

$ GST_DEBUG=*udpsink*:5 gst-launch-1.0 fakesrc ! udpsink host=239.1.2.3 port=1234

Actual results:

...
(gst-launch-1.0:26827): GLib-GIO-CRITICAL **:
g_socket_multicast_group_operation: assertion `g_inet_address_get_family
(group) == socket->priv->family' failed
...
Could not join multicast group: unknown reason
ERROR: pipeline doesn't want to preroll.
...

Expected results:

The pipeline should run.

Additional info:

More details can be found under the associated gstreamer and glibc bug reports

https://bugzilla.gnome.org/show_bug.cgi?id=687090
https://bugzilla.gnome.org/show_bug.cgi?id=687092

Comment 1 Tyson Whitehead 2013-09-10 22:43:02 UTC
Note that I said glibc in the comments when I really meant glib2.

Also note that this only effects F18 as F19 and above are glib2 >= 2.35.2.

Comment 2 Fedora End Of Life 2013-12-21 14:34:11 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 3 Fedora End Of Life 2014-02-05 22:22:34 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.