Jump to content


Photo

OpenPLI 3.0 crashes when select sat finder


  • Please log in to reply
5 replies to this topic

#1 ias2

  • Member
  • 8 posts

0
Neutral

Posted 5 September 2013 - 12:38

Hi to all,

 

  after upgrading my extrend et9200 with OpenPLI 3.0 on it some days ago, I experience crashes (with log file in /media/hdd) when I go on "sat finder" under setup->service searching menu.
Attached, the log file produced at crash... some suggestions?

Attached Files



Re: OpenPLI 3.0 crashes when select sat finder #2 WanWizard

  • PLi® Core member
  • 70,377 posts

+1,807
Excellent

Posted 5 September 2013 - 12:50

With the standard PLi-HD skin, or did you install something else?

 

warning, skin is missing element header in <class 'Plugins.SystemPlugins.Satfinder.plugin.Satfinder'>
opening frontend 0
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 66, in action
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 46, in action
  File "/usr/lib/enigma2/python/Screens/Menu.py", line 56, in okbuttonClick
  File "/usr/lib/enigma2/python/Screens/Menu.py", line 24, in __call__
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/Satfinder/plugin.py", line 307, in SatfinderMain
    session.open(Satfinder, nimList[0])
  File "/usr/lib/enigma2/python/mytest.py", line 306, in open
    self.execBegin()
  File "/usr/lib/enigma2/python/mytest.py", line 208, in execBegin
    c.show()
  File "/usr/lib/enigma2/python/Screens/Screen.py", line 155, in show
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/Satfinder/plugin.py", line 72, in __onShow
    self.retune(None)
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/Satfinder/plugin.py", line 129, in retune
    satpos = int(self.tuning_sat.value)
ValueError: invalid literal for int() with base 10: ''
(PyObject_CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0x1503828>>,('OkCancelActions', 'ok')) failed)
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
]]> 

Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLI 3.0 crashes when select sat finder #3 ias2

  • Member
  • 8 posts

0
Neutral

Posted 5 September 2013 - 13:00

I've tried the PLi-HD and the standard skin. It crashes with both of them...



Re: OpenPLI 3.0 crashes when select sat finder #4 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 5 September 2013 - 19:30

I've tried the PLi-HD and the standard skin. It crashes with both of them...

As far as I understand PLi-HD is the standard skin for OpenPLi?

So what is this standard skin that you used except PLi-HD?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: OpenPLI 3.0 crashes when select sat finder #5 ias2

  • Member
  • 8 posts

0
Neutral

Posted 5 September 2013 - 21:05

Well, "default skin" rather than "standard skin", sorry. Attached you can find images of both skins. Anyway, after reconfiguring the tuner and a couple of reboots, the sat finder works fine now... I think that the problem arise when I call the sat finder with the tuner configuration messed up...

Attached Files



Re: OpenPLI 3.0 crashes when select sat finder #6 littlesat

  • PLi® Core member
  • 57,117 posts

+698
Excellent

Posted 5 September 2013 - 21:51

File "/usr/lib/enigma2/python/Plugins/SystemPlugins/Satfinder/plugin.py", line 129, in retunesatpos = int(self.tuning_sat.value)

ValueError: invalid literal for int() with base 10: ''

 

 

The config value self.tuning_sat.value is an empty string here...so this one cannot be converted to an integer.

It could be considered to add a check there in satfinder that avoids this GSOD.

But first it is more imported to find what triggers this config value being an empty string.


Edited by littlesat, 5 September 2013 - 21:52.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W



3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users