DiSEqC configuration menu is not shown

Bug #452894 reported by Donatas Elvikis
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MythTV
Won't Fix
Unknown
Mythbuntu
Fix Released
Low
Unassigned

Bug Description

I have a fresh install of Mythbuntu 9.10 with automatic daily builds enabled and MythTv 0.22 SVN 22460 (not sure about the last digit, since I cant access at the moment, but my last update was yesterday late night)

After selecting card type "DVB DTV capture card (v3.x)" my TerraTec Cinergy S2 PCI HD CI car being recognized I need to configure my DiSEqC. In the newly opened window I see "(Unconnected)" which is the way it should be. However clicking this item only makes my window blink but does not open menu for selecting device type, i.e. Switch, Rotor or LNB, thus no further configuration is possible.

BTW, I could scan all LNB's from command line, szap to channels play them with mplayr, so card is working nicely.

Revision history for this message
Dave Walker (davewalker) wrote :

Whilst this is a bug, you can achieve this by pressing right and enter if I remember correctly. The key is to unselect "(Unconnected)". It can be done, as I did it last week - setting it to LNB. But it isn't functioning as expected.

Changed in mythbuntu:
status: New → Confirmed
Revision history for this message
Simon Harrison (simon-harrison1) wrote :

Yes, I noticed this as well, yesterday. As has already been commented, you need to hit any cursor key, then 'Enter' to select the 'Unconnected' menu item.
This is, in fact a 'feature' of the whole backend-setup menu system. It affects all of the submenu lists, where you need to select a Ccapture card, input connection, video source, etc. to modify.
The selection list appears with the first item highlighted, but if you simply hit 'Enter', nothing happens, the screen just flashes, you need to move down the list with the arrow keys first, even if there is only one menu item.

Revision history for this message
Donatas Elvikis (kyvislt) wrote :

Thanks, this worked.

@Simon Harrison: Actually I tried to observe if this is really true in the whole backend-setup, maybe I missed something, but finally I've got a feeling that this was the only place one has to do the trick.

Revision history for this message
MarcRandolph (mrand) wrote :

Don't hold out high hope for this being fixed in 0.22... but hopefully will be fixed by the time 10.04 rolls around.

Changed in mythbuntu:
importance: Undecided → Low
Changed in mythtv:
status: Unknown → New
Changed in mythtv:
status: New → Won't Fix
Revision history for this message
MarcRandolph (mrand) wrote :

If I understand correctly, this was partly fixed in 0.23. The remainder will be fixed by a (future... hopefully 0.25) complete overhaul of mythtv setup.

Changed in mythbuntu:
status: Confirmed → Fix Released
Revision history for this message
CoolDreamZ (chris-thompson-stormfolio) wrote :

This "feature" has just cost me several hours of head scratching! I can confirm that the issue is still present in 0.25

The user manual on the mythtv wiki states -- If nothing had yet been configured, you will see "(Unconnected)" on top of the screen. Select this to make adjustments -- what is particularly annoying is that there is no obvious visual clue as to whether it is selected or not and just pressing "enter" results in the screen flashing.

I have updated the wiki page.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.