Two presses of PIP button cause crash of zap history is disabled

Issue #277 resolved
Peter Urbanec created an issue

When 20140704 is installed and zap history is disbled, two presses of PIP button cause the following crash:

KEY: 174 make EXIT  
action ->  InfobarShowHideActions hide
KEY: 174 break EXIT
KEY: 375 make SCREEN
KEY: 375 break SCREEN 
action ->  InfobarPiPActions activatePiP
[SCREENNAME]  PictureInPictureZapping
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 48, in action
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 2540, in activePiP
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 2492, in togglePipzap
  File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 2053, in setCurrentServicePath
  File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 1946, in setHistoryPath
TypeError: 'NoneType' object has no attribute '__getitem__'
(PyObject_CallObject(<bound method HelpableActionMap.action of <Components.ActionMap.HelpableActionMap instance at 0x1cc3738>>,('InfobarPiPActions', 'activatePiP')) failed)

Reproduction steps

  • Setup / TV / Zap History
  • Enable zap history = OFF
  • Press PIP button
  • Press PIP button again
  • CRASH

Comments (4)

  1. Peter Urbanec reporter

    This crash only seems to happen when config.plugins.ZapHistoryConfigurator.enable_zap_history=false

  2. Peter Urbanec reporter
    • removed issue_update
    • removed issue_reproducability
    • removed issue_update

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

    • This issue's title has been changed
    • This issue's reproduction steps has been changed
    • This issue's description has been changed
  3. Peter Urbanec reporter
    • removed issue_update

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

    • This issue's title has been changed
  4. Peter Urbanec reporter
    • 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 New 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.
  5. Log in to comment