FrankK

I have Jamulus server running on a Raspberry Pi 3B+ that has been working fine for months. It was upgraded to v3.5.5 a few weeks ago, and continued to work just fine. As of about a week ago, everyone trying to connect to the server gets the infamous "TRYING TO CONNECT" message when they try to connect to my server. I have a monitor connected to the Pi, and the server shows that every connect attempt is successful — each person that tries is listed as connected — but we just see the "TRYING TO CONNECT"...

I have Jamulus server running on a Raspberry Pi 3B+ that has been working fine for months. It was upgraded to v3.5.5 a few weeks ago, and continued to work just fine. As of about a week ago, everyone trying to connect to the server gets the infamous "TRYING TO CONNECT" message when they try to connect to my server. I have a monitor connected to the Pi, and the server shows that every connect attempt is successful — each person that tries is listed as connected — but we just see the "TRYING TO CONNECT"...

I have Jamulus server running on a Raspberry Pi 3B+ that has been working fine for months. It was upgraded to v3.5.5 a few weeks ago, and continued to work just fine. As of about a week ago, everyone trying to connect to the server gets the infamous "TRYING TO CONNECT" message when they try to connect to my server. I have a monitor connected to the Pi, and the server shows that every connect attempt is successful — each person that tries is listed as connected — but we just see the "TRYING TO CONNECT"...

I have Jamulus server running on a Raspberry Pi 3B+ that has been working fine for months. It was upgraded to v3.5.5 a few weeks ago, and continued to work just fine. As of about a week ago, everyone trying to connect to the server gets the infamous "TRYING TO CONNECT" message when they try to connect to my server. I have a monitor connected to the Pi, and the server shows that every connect attempt is successful — each person that tries is listed as connected — but we just see the "TRYING TO CONNECT"...

OK, never mind... after seeing a comment on another thread where someone had to restart their computer after installing 3.5.5, I slapped myself in the forehead; that should have been the first thing I tried! And sure enough, it worked. (sigh)

I'm seeing similar problems. My server is on 3.5.4, and I have two clients: one on either 3.5.2 or 3.5.3 (how do I tell what version it is?) and one upgraded today to 3.5.5. The older client works fine with the server, but the 3.5.5 client does not send or receive any audio to/from the server. The 3.5.5 client connects just fine and I get no errors, but there is simply no audio in or out. Has anyone else seen this? Is there a solution that I'm missing?

I'm seeing similar problems. My server is on 3.5.4, and I have two clients: one on either 3.5.2 or 3.5.3 (how do I tell what version it is?) and one upgraded today to 3.5.5. The 3.5.3 client works fine with the server, but the 3.5.5 client does not send or receive any audio to/from the server. The 3.5.5 client connects just fine and I get no errors, but there is simply no audio in or out. Has anyone else seen this? Is there a solution that I'm missing?

I've successfully installed and run 3.5.4 server on a Raspberry Pi 3B+, and it appears to be working fine. But I get a warning when I start the server that reads, "libEGL warning: DRI2: failed to authenticate". I'm sure it's related to qt5ct, but I'm not sure what's going on. Is anyone familiar with this warning? UPDATE: I should have mentioned that I see this warning when I start the server with "./Jamulus -s -R /home/jam".