Roon browser display continually dropping then re-attaching on Linux Mint Mate + Raspbian

Core Machine (Operating system/System info/Roon build number)

Latest version roon server on Linux mint latest version

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Everything wired, fritz box 7530 as Internet modem/router, with 8 way netgear switch. Roon server and roon Bridge plugged into switch

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Roon Bridge on Linux mint, Firefox browser as display. Audio out via USB, zero impact to sound

Description Of Issue

I have Firefox browser on a pc running roon Bridge attached to the same audio zone. The display continually cycles between attached and disconnected. Every 8 seconds roughly, it connects, shows display, disconnects after 8 seconds, reconnects and repeats.
Watching the pop up in roon remote I can see the display swap between start and stop display. It displays OK, button on remote says stop display, then a blip, display goes black and remote says start display. Continuously cycling.
Now I did change router yesterday which could be the cause? In preparation for a broadband supplier change next week, this is the fritz box from the new supplier connected to the old supplier details until Wednesday. Nothing else I recall changing.

I’ve just transferred the active zone to a raspberry pi with attached 7" display in the other room and it’s perfect! Switched it back and display/dropped/display/dropped continues. So I guess it’s something with this pc. But the music is perfect just the display. This pc and the raspberry both running roon Bridge build 169. Same browser on both, doesn’t matter if Firefox or vivaldi. Display is local ip address : 9100/display/

snippet from the logs

07/21 19:51:19 Info: [roonapi] [apiclient 192.168.1.14:44548] connected (websocket)
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] GOT com.roonlabs.registry:1/info
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] COMPLETE Success {"core_id":"b2909c7c-d00b-4785-9581-f8f9486f517b","display_name":"robert-nas","display_version":"1.6 (build 416) stable"}
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] GOT com.roonlabs.registry:1/register {"extension_id":"com.roonlabs.display_zone","display_name":"Roon API Display Zone","display_version":"1.0.0","publisher":"Roon Labs, LLC","email":"contact@roonlabs.com","required_services":["com.roonlabs.transport:2","com.roonlabs.image:1"],"optional_services":[],"provided_services":["com.roonlabs.zonedisplay:1","com.roonlabs.pairing:1","com.roonlabs.ping:1"],"token":"ac749bcd-2457-4ec5-9257-30adf7a53e77"}
07/21 19:51:19 Warn: [roonapi/registry] booting client with duplicate token ac749bcd-2457-4ec5-9257-30adf7a53e77
07/21 19:51:19 Info: [roonapi] [apiclient 192.168.1.14:44546] disconnected
07/21 19:51:19 Trace: [roonapi/registry] removing [apiclient 192.168.1.14:44546] => [com.roonlabs.display_zone, Roon API Display Zone v1.0.0 by Roon Labs, LLC <contact@roonlabs.com>]
07/21 19:51:19 Info: [transport/zonedisplay] Zone display unregistered: [Roon API Display Zone (Roon Labs, LLC): ac749bcd-2457-4ec5-9257-30adf7a53e77:57ab7411-c7a0-4507-8112-a4ddc4fbd039]
07/21 19:51:19 Trace: [roonapi/registry] [com.roonlabs.display_zone, Roon API Display Zone v1.0.0 by Roon Labs, LLC <contact@roonlabs.com>] was re-enabled based on token
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] CONTINUE Registered {"core_id":"b2909c7c-d00b-4785-9581-f8f9486f517b","display_name":"robert-nas","display_version":"1.6 (build 416) stable","token":"ac749bcd-2457-4ec5-9257-30adf7a53e77","provided_services":["com.roonlabs.transport:2","com.roonlabs.image:1"],"http_port":9100}
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] REQUEST com.roonlabs.zonedisplay:1/subscribe_displays {"subscription_key":"345"}
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] REQUEST com.roonlabs.pairing:1/subscribe_pairing {"subscription_key":"346"}
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] GOT com.roonlabs.transport:2/subscribe_zones {"subscription_key":0}
07/21 19:51:19 Trace: [roonapi] [apiclient 192.168.1.14:44548] CONTINUE Subscribed {"zones":[{"zone_id":"160193166e7e554e14910f600ac665e0d6a9","display_name":"htpc","outputs":[{"output_id":"170193166e7e554e14910f600ac665e0d6a9","zone_id":"160193166e7e554e14910f600ac665e0d6a9","can_group_with_output_ids":["1701cc47c34051fa2accdd42a173f18484dd","170193166e7e554e14910f600ac665e0d6a9","17015dcdfcc3a6d39d9b579012bbbbb0e135"],"display_name":"htpc","source_controls":[{"control_key":"1","display_name":"HDA NVidia MI

another log snippet

[{"zone_id":"1601cc47c34051fa2accdd42a173f18484dd","queue_time_remaining":127,"seek_position":169}]}
07/21 19:51:59 Trace: [roonapi] [apiclient 192.168.1.14:44554] CONTINUE Changed {"zones_seek_changed":[{"zone_id":"1601cc47c34051fa2accdd42a173f18484dd","queue_time_remaining":127,"seek_position":169}]}
07/21 19:52:00 Trace: [roonapi] [apiclient 192.168.1.19:44770] CONTINUE Changed {"zones_seek_changed":[{"zone_id":"1601cc47c34051fa2accdd42a173f18484dd","queue_time_remaining":126,"seek_position":170}]}
07/21 19:52:00 Trace: [roonapi] [apiclient 192.168.1.14:44554] CONTINUE Changed {"zones_seek_changed":[{"zone_id":"1601cc47c34051fa2accdd42a173f18484dd","queue_time_remaining":126,"seek_position":170}]}
07/21 19:52:01 Info: [roonapi] [apiclient 192.168.1.14:44556] connected (websocket)
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] GOT com.roonlabs.registry:1/info
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] COMPLETE Success {"core_id":"b2909c7c-d00b-4785-9581-f8f9486f517b","display_name":"robert-nas","display_version":"1.6 (build 416) stable"}
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] GOT com.roonlabs.registry:1/register {"extension_id":"com.roonlabs.display_zone","display_name":"Roon API Display Zone","display_version":"1.0.0","publisher":"Roon Labs, LLC","email":"contact@roonlabs.com","required_services":["com.roonlabs.transport:2","com.roonlabs.image:1"],"optional_services":[],"provided_services":["com.roonlabs.zonedisplay:1","com.roonlabs.pairing:1","com.roonlabs.ping:1"],"token":"ac749bcd-2457-4ec5-9257-30adf7a53e77"}
07/21 19:52:01 Warn: [roonapi/registry] booting client with duplicate token ac749bcd-2457-4ec5-9257-30adf7a53e77
07/21 19:52:01 Info: [roonapi] [apiclient 192.168.1.14:44554] disconnected
07/21 19:52:01 Trace: [roonapi/registry] removing [apiclient 192.168.1.14:44554] => [com.roonlabs.display_zone, Roon API Display Zone v1.0.0 by Roon Labs, LLC <contact@roonlabs.com>]
07/21 19:52:01 Info: [transport/zonedisplay] Zone display unregistered: [Roon API Display Zone (Roon Labs, LLC): ac749bcd-2457-4ec5-9257-30adf7a53e77:57ab7411-c7a0-4507-8112-a4ddc4fbd039]
07/21 19:52:01 Trace: [roonapi/registry] [com.roonlabs.display_zone, Roon API Display Zone v1.0.0 by Roon Labs, LLC <contact@roonlabs.com>] was re-enabled based on token
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] CONTINUE Registered {"core_id":"b2909c7c-d00b-4785-9581-f8f9486f517b","display_name":"robert-nas","display_version":"1.6 (build 416) stable","token":"ac749bcd-2457-4ec5-9257-30adf7a53e77","provided_services":["com.roonlabs.transport:2","com.roonlabs.image:1"],"http_port":9100}
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] REQUEST com.roonlabs.zonedisplay:1/subscribe_displays {"subscription_key":"353"}
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] REQUEST com.roonlabs.pairing:1/subscribe_pairing {"subscription_key":"354"}
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] GOT com.roonlabs.transport:2/subscribe_zones {"subscription_key":0}
07/21 19:52:01 Trace: [roonapi] [apiclient 192.168.1.14:44556] CONTINUE Subscribed {"zones":[{"zone_id":"160193166e7e554e14910f600ac665e0d6a9","display_name":"htpc","outputs":[{"output_id":"170193166e7e554e14910f600ac665e0d6a9","zone_id":"160193166e7e554e14910f600ac665e0d6a9","can_group_with_output_ids":["1701cc47c34051fa2accdd42a173f18484dd","170193166e7e554e14910f600ac665e0d6a9","17015dcdfcc3a6d39d9b579012bbbbb0e135"],"display_name":"htpc","source_controls":[{"control_key":"1","display_name":"HDA NVidia MI

Hi @Robert_Holloway,

Can you please confirm if the same behavior occurs when you access the browser from the RoonServer install? What about if you try using a different web browser on the RoonBridge, such as Chrome, does it display the same behavior?

If this issue only started after the router change, Fritzbox is on our Networking Best Practices as a router with known configuration settings to apply. Do you by any chance have “Software Packet Acceleration” turned on and is the behavior the same if you disable this feature?

Hi, can’t find software packet acceleration setting anywhere in fritz os.
Installed chromium browser on the roon Bridge and it works perfectly.
Very strange as both Firefox and vivaldi browsers worked before. Firefox works on the roon server itself and vivaldi on my raspberry pi roon Bridge.
All I can assume is there’s something about the roon Bridge pc itself (which is Linux mint mate edition) maybe something in mate itself that makes the difference. (the roon server is Linux mint cinnamon)
I have another pc I can experiment with (also a room bridge running Linux mint mate) to see if the Firefox / vivaldi / chromium also work differently.
Anyway solved by using chromium… Should have thought to try!

1 Like

Hi @Robert_Holloway,

Thanks for the update here and glad to hear that things are working out with Chromium. Not sure why it would be just Firefox affected by this issue, perhaps it’s worth double checking the multicast settings and making sure that it is properly configured? Either way, I have moved this post over to the Linux subcategory and if you make any new discoveries please do feel free to let the community know (in case others run into similar behavior). Thanks!

Just tried Firefox on another pc with Linux mint mate… Works perfectly.
Something peculiar with this specific computer and there are so many variables at play it’s going to be hard to track down. I don’t think it’s anything network related (at least as far as the router/switch are concerned) as I can send the display to other computers around the house, but when it comes back to this one it stops working; unless using chromium and then it’s OK. Could be security settings on each browser as they are all slightly different.

Hi @Robert_Holloway,

Hmm, this is peculiar if the same browser works on the same platform yet on another machine. What is the version of Firefox that you are using on both machines? Do they have the same version numbers? Same addons/plugins? What if you try running it as incognito on Firefox on the machine that did not previously work, does that change anything? Also, can you send me the full log set from the machine that it does not work on via Dropbox / Google Drive / Send.firefox.com?

Hi, managed to break it on my raspberry pi that was working perfectly. How? closed and reopened the browser. Now it cycles on/off/on/off just like the other PC. This is vivaldi browser. Will try chromium …

Ok works on chromium. The raspberry pi normally just sits there and works, I never touch it so it’s been up for days. 77 days according to htop command. Suspect the browser was running all that time too. Now I’ve closed and reopened, it’s picked up the “bug” that doesnt seem to impact Chromium.

Hi, have sent you the full set of log files. The ones that might be of interest are from today 25July, see log_02 and log_03. Scan for “vivaldi on linux” and “chrome on linux” (actually chromium). What I’ve noticed is “booting client with duplicate token” which seems to me to be when the display connection gets dropped. 10 seconds later, the display reconnects and is booted again. With the older file, before i stopped and restarted vivaldi, you dont get that. After the restart of vivaldi, the booting starts. and doesnt occur with Chromium. Hope that helps.

Hi @Robert_Holloway,

Thank you for sending those log files over. I have requested the technical team take a closer look to see if there is anything strange regarding the “booting client with duplicate token” trace you observed. I will be sure to reach out to you once I have any further information.

Hi @Robert_Holloway,

I brought your case to the attention of the QA team and we will need to discuss with the devs as to what exactly the duplicate token indicates as they would be better suited to answer this question. We also require some more information as to file the proper case notes, can you please let me know which build/flavor of Firefox you are using on the install with this issue? Are there any additional addons or configuration options you have set in Firefox that are not the default values?

Hi @Robert_Holloway,

I wanted to check in with you here as we have discussed this issue with the devs recently. The duplicate token traces that you noticed occur when the Core already has an active connection via the API and closes the other one. I would like to request some points of clarification here:

  1. Are you logged into the affected Firefox browsers with a Firefox account?

  2. Do you sync your Firefox data between the two machines via Firefox Sync?

  3. If you do sync your data in this way, is there any change if you reinstall Firefox, do not log in via a Firefox account and try to reproduce the issue?

  4. What endpoints are you using in your setup? When this issue occurred, were you using one specific zone to display to both Roon displays?

  5. Which version of Firefox are you using? Do you have any addons installed?

Hmmm. Now broken on chromium and working on Firefox. Need more experimenting like rebooting etc to get stable behaviour

Reboot made no difference. However I opened an “incognito” tab on chromium and that works, the “cognito” tab opened at the same time is broken. I’m not aware I’m logged in as a browser user on any of these, however I assume there must be some attribute of a clean incognito tab - or rather the lack of attribute, some cookie or whatever - that isn’t tripping up roon.

I’ve now disabled some of the “remember me”, save cookies etc type settings in chromium, relaunched and its working.

Hi @Robert_Holloway,

Thanks for the update. Just to make sure I understand you here:

Are you saying you were not logged in to any of the browsers when this issue occurred? Do you have any kind of sync happening between the different machines you use for your Roon display?

No I’m not aware there’s any syncing going on. However as noted, with some config options disabled in chromium, it appears to be working. Note the pi is running chromium at the same time, though I didn’t try sending the display there to see the effect. Opening an incognito tab worked then I thought to disable some options and non incognito (ie ordinary tab) started to work. So without knowing 100% the cause, as these browsers tend to remember things, like last visited tab etc, given the result yesterday in my experimenting, that was the underlying cause of the issue. Ie I suspect using an incognito tab in chromium or Firefox should always work.

Hi @Robert_Holloway,

Thanks for the followup. Since you have activated incognito mode, this would effectively bypass any addons you may have installed.

It sounds like one of your addons or config options was causing the issue and without knowing what exactly you disabled and how this interacts with the browser’s cookies, it will be difficult for us to isolate the issue.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.