CH+ and RIGHT do not work correctly in Terrestrial LCN bouquet

Issue #110 resolved
prl created an issue

CH+ and RIGHT only work for the first press of either immediately after selecting the Terrestrial LCN bouquet. After successfully changing service once with CH+ or RIGHT in LiveTV pressing either of them again has no effect.

It only seems to be the Terrestrial LCN bouquet that has this problem. FAV, ALL, select service is OK, and so are the Last Scanned and Favourites (TV) bouquets. Of course services have to be added to Favourites (TV) before this can be tested.

Reproduction steps

FAV>Terrestrial LCN, OK, highlight service, OK to select and return to LiveTV. Pressing either CH+ or RIGHT works. If you press either of them a second time, nothing happens.

Tested on userbouquet.terrestrial_lcn.tv with it exactly as scanned.

Comments (10)

  1. prl reporter

    Removing all the "padding" entries that look like:

    #SERVICE 1:832:d:0:0:0:0:0:0:0:

    from /etc/enigma2/userbouquet.terrestrial_lcn.tv works around this problem.

    Removing these entries also changes the service numbering so that they no longer look like the service LCNs (they number sequentially from 1).

    Bug 110 is also worked around by removing these dummy SERVICE entries from /etc/enigma2/userbouquet.terrestrial_lcn.tv

  2. prl reporter
    • removed issue_status
    • removed issue_update

    The issue was updated with the following change(s):

    • This issue's description has been changed
    • The status has been updated, from New to Confirmed.
  3. prl reporter
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Confirmed to New.
  4. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from New to Delegated.
  5. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Delegated to Testing.
  6. prl reporter

    A file was uploaded. reference to attachment 20140318_prl_Canberra_settings.zip (/etc/enigma2 from a scan of Canberra Black Mountain) This comment was attached:

    Scan and other settings from a scan of Canberra Black Mountain (upgrade firmware, scan in setup wizard, Restart GUI).

    I hope that using these settings will help the developers replicate the problem.

  7. prl reporter
    • removed issue_status

    Still the same for me in 20140316 and 20140317. I have attached a copy of the contents of my /etc/enigma2 folder. I hope this makes finding the problem easier for the Beyonwiz engineers.

    The issue was updated with the following change(s):

    • The status has been updated, from Testing to Not Fixed.
  8. prl reporter

    A file was uploaded. reference to attachment enigma2-20140407.tgz (/etc/enigma2 contents for 20140407) This comment was attached:

    This bug is still present for me in Canberra for firmware 20140407. Attaching the contents of /etc/enigma2 as requested by peteru

  9. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Not Fixed to Testing.
  10. Peter Urbanec
    • removed issue_resolution
    • removed issue_percent
    • removed issue_close
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Testing to Closed.
    • This issue has been closed
    • This issue's progression has been updated to 100 percent completed.
    • The resolution has been updated, from Not determined to Fixed.
  11. Log in to comment