You are here: Home » Topic » Rhythmbox occasionally drops connection

Rhythmbox occasionally drops connection

This topic contains 1 reply, has 1 voice, and was last updated by  jcornwall 8 years, 9 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #2663

    jcornwall
    Participant

    Here’s a curious one. Since updating my desktop (the DAAP client) from Ubuntu Hardy to Ubuntu Intrepid (beta) Rhythmbox has very occasionally been dropping connections. This is once or twice a day at most, often playing for hours without problems.

    It’s most likely a bug in the newer version of Rhythmbox but have a look at this packet trace I captured. ‘deimos’ is the client and ‘phobos’ is the Firefly server:

    ...
    10:35:19.007204 IP deimos.35285 > phobos.daap: . ack 1849780 win 35
    10:35:19.007432 IP phobos.daap > deimos.35285: . 1849780:1851228(1448) ack 348 win 54

    10:35:19.007434 IP phobos.daap > deimos.35285: . 1851228:1852676(1448) ack 348 win 54

    10:35:19.007435 IP phobos.daap > deimos.35285: . 1852676:1854124(1448) ack 348 win 54

    10:35:19.007437 IP phobos.daap > deimos.35285: . 1854124:1854260(136) ack 348 win 54

    10:35:19.050704 arp who-has phobos tell deimos
    10:35:19.050928 arp reply phobos is-at 00:e0:81:2d:bb:12 (oui Unknown)
    10:35:19.050944 IP deimos.35285 > phobos.daap: . ack 1854260 win 0

    10:35:19.176757 IP phobos.mdns > 224.0.0.251.mdns: 0*- [0q] 5/0/0 PTR[|domain]
    10:35:19.187601 IP deimos.35285 > phobos.daap: R 348:348(0) ack 1854260 win 453

    10:35:19.196604 IP deimos.33614 > phobos.daap: P 81978390:81978622(232) ack 95631897 win 593

    10:35:19.197418 IP phobos.daap > deimos.33614: P 1:33(32) ack 232 win 196

    10:35:19.197448 IP deimos.33614 > phobos.daap: . ack 33 win 593

    10:35:19.197625 IP phobos.daap > deimos.33614: FP 33:422(389) ack 232 win 196

    10:35:19.197877 IP deimos.33614 > phobos.daap: F 232:232(0) ack 423 win 593

    10:35:19.198095 IP phobos.daap > deimos.33614: . ack 233 win 196

    Out of the entire log that is the only multicast packet from Firefly. The client instantly resets the connection upon seeing it. The Firefly server still appears in Rhythmbox’s discovery list but is not selected; selecting it allows me to continue playing music until the next occasional disconnection.

    I don’t think this is firewall related: nothing has changed since my old working configuration and the multicast packets definitely get through. I’ll have a dig through Rhythmbox’s Avahi code to see if anything significant has changed.

    #17775

    jcornwall
    Participant

    A debug log from Rhythmbox during a drop:

    (23:20:59) [0x11fe500] [mdns_service_removed] rb-daap-plugin.c:466: DAAP source 'Media Server' went away
    (23:20:59) [0x11fe500] [remove_source] rb-daap-plugin.c:480: Removing DAAP source: Media Server
    (23:20:59) [0x11fe500] [rb_daap_source_disconnect] rb-daap-source.c:665: Disconnecting source

    ...

    (23:00:30) [0x11fe500] [mdns_service_added] rb-daap-plugin.c:433: New service: Media Server name=Media Server host=82.70.152.18 port=3689 password=0
    (23:00:30) [0x11fe500] [rhythmdb_tree_entry_type_registered] rhythmdb-tree.c:2676: no entries of newly registered type daap:Media Server:Media Server:82.70.152.18 loaded from db

    I can’t see any recent changes to Rhythmbox’s DAAP plugin that would change its behaviour.

    Its claim that Firefly unregistered from multicast DNS appears to agree with the packet trace. Why might Firefly unregister at random times and reregister almost instantaneously?

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.