Tvheadend

syslog:
Aug 13 21:54:17 core2 tvheadend¹⁰¹⁴: htsp: Got connection from 192.168.2.101
Aug 13 21:54:17 core2 tvheadend¹⁰¹⁴: htsp: 192.168.2.101: Welcomed client software: XBMC Media Center (HTSPv12)
Aug 13 21:54:22 core2 tvheadend¹⁰¹⁴: htsp: 192.168.2.101 [ XBMC Media Center ]: Disconnected
Aug 13 21:54:22 core2 tvheadend¹⁰¹⁴: htsp: Got connection from 192.168.2.101
Aug 13 21:54:22 core2 tvheadend¹⁰¹⁴: htsp: 192.168.2.101: Welcomed client software: XBMC Media Center (HTSPv12)
Aug 13 21:54:24 core2 tvheadend¹⁰¹⁴: htsp: 192.168.2.101 [ XBMC Media Center ]: Disconnected

It is the same for me since last build.
I was used to disable all the authentications using the '--noacl' parameters but, maybe an old bug, for some interactions/streaming it was necessary to use the "jolly rule" of the first post in this report. Note, I didn't even have the super user file in my ~/.hts/tvheadend/ folder.
Now:
- if I keep the '--noacl' parameter but disable the jolly rule, I can't login in the web interface;
- if I keep both: * I can login on the web-interface but I can't stream using vlc with an url like http://server:9981/play/stream/channel/9e6eefe1df4d5fea2e58128e23e3988d as in the past * I can't use TVHClient (with or without password): the app says 'access denied'; * I can't use XBMC (username specified, password empty): it looks to login but empty channel list and no functionalities.

There are regressions but I expect that using the '--noacl' parameter all the actions/logins should work even if there are no username/password specified in urls/applications

for me it is the same,
nothing works
any client ios, android, xbmc and vlc nothing is streaming

Could you try v3.9-1287-gd327932 ?

Better with v3.9-1288-gcb5c5d1 .

It segfaults for me, but I can't provide further details now: I'm on smartphone away from home with VPN. Later a log.

It seems to work with 3.9.1289~g1eddf45 on both linux client as android TVHGuid. Thanks.

on debain it works
i still wait for the synology package :)

I can't reproduce the segfaults now, but the authentication works well. Thanks.