Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 198408 - Package rhythmbox lacks IPv6 support
Package rhythmbox lacks IPv6 support
Product: Fedora
Classification: Fedora
Component: rhythmbox (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Depends On:
Blocks: IPv6Blocker
  Show dependency treegraph
Reported: 2006-07-11 06:29 EDT by Peter Vrabec
Modified: 2008-07-03 03:00 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-30 11:05:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Replace IPv4-only code with AF-agnostic approach (3.96 KB, patch)
2006-07-18 01:56 EDT, Jan Pazdziora
no flags Details | Diff

  None (edit)
Description Peter Vrabec 2006-07-11 06:29:10 EDT
This bug was reported automaticaly in connection with IPv6 project.
Our aim is to support IPv6 in all Fedora Core packages so FC6 and RHEL5 will be ready for IPv6.
This package seems to lack IPv6 support as is illustrated in attached log.
Here follows part of scanning log (grep -r F_INET *)/up to 30 lines: 

/rhythmbox-0.9.5/daapsharing/rb-daap-src.c:668:	src->sock_fd = socket (AF_INET, SOCK_STREAM, 0);
/rhythmbox-0.9.5/daapsharing/rb-daap-src.c:676:	server.sin_family = AF_INET;
Comment 1 Jan Pazdziora 2006-07-18 01:56:23 EDT
Created attachment 132584 [details]
Replace IPv4-only code with AF-agnostic approach

The patch changes IPv4-only routines by getaddrinfo.

The patch adds support for IPv6 addresses in URI as recommended by RFC 2732.

Why was there strrchr (hostport, ':'); in _split_uri -- what would have
happened if there was a colon in the path part? Anyway, changed to strchr.

Changed the type of argument port in _split_uri to gchar ** -- we work with
strings only.

The patch was not tested beyond compile.
Comment 2 Bastien Nocera 2007-01-30 11:05:34 EST
The DAAP source only works on local networks, and advertised through mDNS, so I
don't think it makes sense to have IPv6 support there.

Also, those aren't full URIs, but just host/port combinations stored internally
(ie. a DAAP source on the local network could be daap://

Filed upstream at:
Comment 3 Yves-Alexis Perez 2008-07-03 03:00:36 EDT
Hmh, why the fact that it works only on local networks and be advertised through
mDNS would block DAAP to work with IPv6?

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