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 685183 - Rygel not recognised by Cambridge Audio NP30
Rygel not recognised by Cambridge Audio NP30
Status: RESOLVED FIXED
Product: rygel
Classification: Applications
Component: IOP
0.16.x
Other Linux
: Normal normal
: ---
Assigned To: rygel-maint
rygel-maint
Depends on:
Blocks:
 
 
Reported: 2012-10-01 07:22 UTC by julienlafontaine2006
Modified: 2012-10-01 12:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Dump of the conversation between Rygel and the NP30 (1.30 KB, application/vnd.tcpdump.pcap)
2012-10-01 07:22 UTC, julienlafontaine2006 		Details
Rygel output in debug mode (5.62 KB, application/octet-stream)
2012-10-01 07:23 UTC, julienlafontaine2006 		Details
Dump of the conversation between Rygel and the NP30 (NEW) (5.26 KB, application/vnd.tcpdump.pcap)
2012-10-01 07:45 UTC, julienlafontaine2006 		Details
Rygel output in debug mode (NEW) (5.62 KB, application/octet-stream)
2012-10-01 07:45 UTC, julienlafontaine2006 		Details

Description julienlafontaine2006 2012-10-01 07:22:01 UTC 
Created attachment 225468 [details]
Dump of the conversation between Rygel and the NP30

Rygel does not seem to be compatible with the Cambridge Audio NP30 network music player.

When the NP30 scans for UPnP servers on the network, it does not seems to see Rygel. Other UPnP servers such as UShare are working ok.

Note that Rygel does work with a PS3 connected to the same network.
Comment 1 julienlafontaine2006 2012-10-01 07:23:09 UTC 
Created attachment 225469 [details]
Rygel output in debug mode
Comment 2 julienlafontaine2006 2012-10-01 07:45:05 UTC 
Created attachment 225470 [details]
Dump of the conversation between Rygel and the NP30 (NEW)
Comment 3 julienlafontaine2006 2012-10-01 07:45:47 UTC 
Created attachment 225471 [details]
Rygel output in debug mode (NEW)
Comment 4 Jens Georg 2012-10-01 07:52:45 UTC 
That is weird, that means receiva firmware regressed. My reciva-based device works fine.

Did you try to update the device?
Comment 5 julienlafontaine2006 2012-10-01 11:42:39 UTC 
Yes, I have been running the latest version of the firmware (v266-b-354-a-002) for a couple of months now.
Comment 6 Jens Georg 2012-10-01 11:53:42 UTC 
Can you uncomment the "force-downgrade-for" line from $HOME/.config/rygel.conf and append ";Reciva" to it, restart rygel and see if that fixes it?
Comment 7 julienlafontaine2006 2012-10-01 12:19:01 UTC 
It fixed it! Thanks so much!