channel browse failure if one backend that contains unique ones is down

[yianniv]

I created a custom channel group. Some of the channels (11, 12, 13, 14) can only be viewed when a SB is on (DVB-T). Channels 1-8 + 15... are available from the master backend.

If the SB is down (I mean the backend program, the pc is always on) and I use the arrow keys to "climb up" the channel list starting from e.g. 2, the frontend is stuck on the 8 channel (the last available on the MB). The keyboard is unresponsive until I kill the frontend or until I start the SB and the two backends communicate.

I can reproduce it all the time by stopping the SB.

All PCs have the 22519 trunk version.

MythTV Version : 22519 MythTV Branch : trunk Network Protocol : 50 Library API : 0.22.20091016-1 QT Version : 4.5.2 Options compiled in:

linux release using_oss using_alsa using_arts using_jack using_backend using_directfb using_dvb using_frontend using_hdpvr using_iptv using_ivtv using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg

[yianniv]

I forgot to mention that the problem doesn't happen if I have the "all channels" group selected.

[Peter Bennett]

If I understand correctly, this happens only if:

• You have a slave backend with a tuner.
• There are some channels that are only available to the slave backend.
• You have a custom channel group with some channels that are only available to the slave.
• You have the master backend up but the slave backend down.
• You try to use Live TV to watch one of those channels only available to the slave.

It seems an unusual setup, perhaps only affects one user. I will mark this as "Won't fix"