Beiträge von seagen

  • SkinReloader-Plugin (DreamOS)

    All works fine if i leave the infobar unchecked. Then the skin reloads but with the infobar checked i get this error.

    But don't put to much into this, Since we can establish that the plugin works as it should. It's my mod of the DreamOS image that does not play ball.

    Not that easy to create a plugin that can handle all Cowboys builds also :grinning_face_with_smiling_eyes:



  • SkinReloader-Plugin (DreamOS)

    I run into this issue on the Dreambox UltraHD with Dream-Elite7 longtime ago when using zombi skin with styles.

    There i hade to physical add the colour name into the Dream-Elite skin.xml (default skin) file else the Style crashed in the same way.


    So for Peter pan we where trying to work around this by loading a external xml file for plugins and skin default

    This would prevent the issue that dre is writing about and have worked just fine


    So i did the same. added menutext colour code to the skin.xml of the default skin and then all works fine again.

    Now i only get an error from the infobar reaload.


    AttributeError: 'InfoBar' object has no attribute 'unhandledKeyDialog'

  • SkinReloader-Plugin (DreamOS)

    I am sure it's my novice skills of coding that is the problem :smiling_face:

    I have not that output in the log. the file is loaded on GUI restart


    I did try with the DreamOS skin default and the plugin works just fine :smiling_face:

    So i have to see where my custom code goes wrong.


    So your amazing plugin do actually work since it have found a flaw in my code :smiling_face:


    Tanks Sven

  • SkinReloader-Plugin (DreamOS)

    Nice :smiling_face:


    Yes the box freeze and can't be rebooted from Telnet i see the please wait in the lcd screen.

    But from the log file i can see that it's my mod for loading menutext color that is the problem and not your plugin :smiling_face:


    I have a style plugin in my image where you can change the colors menutext in the skin.xml. As you can see i load an external .xml file for this color

    This is not playing ball with your plugin for obviouse reasons.


    Code
    May 24 11:28:41 dreambox enigma2 [3320]: File "SkinReloader.py", line 427, in SkinReloader.SkinReload.reloadSkin
May 24 11:28:41 dreambox enigma2 [3320]: File "/usr/lib/enigma2/python/skin.py", line 742, in loadSkinData
May 24 11:28:41 dreambox enigma2 [3320]: loadSingleSkinData (desktop, dom_skin, path)
May 24 11:28:41 dreambox enigma2 [3320]: File "/usr/lib/enigma2/python/skin.py", line 530, in loadSingleSkinData
May 24 11:28:41 dreambox enigma2 [3320]: colorNames [name] = parseColor (color)
May 24 11:28:41 dreambox enigma2 [3320]: File "/usr/lib/enigma2/python/skin.py", line 247, in parseColor
May 24 11:28:41 dreambox enigma2 [3320]: raise SkinError ("color '% s' must be #aarrggbb or valid named color"% (str))

  • SkinReloader-Plugin (DreamOS)

    Bumping life back into this thread :smiling_face:


    I tested this plugin on my Dreambox Two UltraHD but i ran into a greenscreen straight away.


    Here is some crash info


  • Skin Holo FHD bug

    Well then they should be removed from the DP feed if they are no longer maintained.

    Me personal think that's a petty since your skin are so well made.


    But i do get that time is not endless :smiling_face:


    Take care :smiling_face:

  • Skin Holo FHD bug

    Hi


    Just want to report a bug i the Holo FHD skin by zombi that can be installed from the DP feed.

    The AudioSelection screen needs to be updated.


    There is an error in the eListboxPythonMultiContent. So when you open the screen the audion tracks report a string error and if you press yellow button for subs menu

    Then you get the green screen.


    I fixed it my self by change the code from. This was just a quick fix for me personal. Code needs tweaking by zombi to have the proper look of the whole skin.



    To this


  • Krogoth branch not possible to build anymore

    Well issue is in the python-ioctl as we reported there was an issue with setuptools and setuptools-scm


    After lots of reading and some help from the darkside we manage to figure out that python-ioctl was trying to install setuptools/setuptools-scm but the package is already installed and the files are owned by that package.

    This caused the build crash. So if you re write the git file for python-ioctl then you can pretty much build in any linux distro of your choice.


    I even manage to build an image with the Windows 10 Ubuntu 18.04 lts addon/app but there you need to install the same recommended extra files as for pyro and the dpkg utils.

    Debian 9 strech only need your first 2 fixes and the tweak in the git file and then you can build without the need for any extra installation.


    Again thanks for your help i would never been able and figure this out without you advices :smiling_face:

  • Krogoth branch not possible to build anymore

    Well after some heavy read up and help from the dark side i figure it out and now can build krogoth image on all Linux distros with VMWare and or Windows 10 (Ubuntu 18.04 lts) :smiling_face:


    I have successfully built on Debian 9/10 Ubuntu 16.04/18.04/20.04

    And Windows 10 Ubuntu 18.04 LTS app


    No need for any complicated docker image

    Image that build fastes on my computer was Debian 9 stretch


    Thanks to dre for keeping me motivated and for always helping us less skilled but learning users

  • „Dream­box Seven Ultra HD“ in der Preview

    Zitat von dbox1

    what you are describing is the Sky Q Box.
    And as far as I know, you could never officially watch German Pay TV with the Dreambox. (maybe the alpha was tolerated?)


    Yes the Q box works in a similar way as the OnePlace. And this is the future way of watching TV.

    If it's all going to be Android or a hybrid solution is long over my head :winking_face: But at least with Dreambox we somewhat are already there.


    Thanks to developers we have access to streaming services and IPTV with Catchup/Weekly Archives but for the moment it is all spread out and depended of thirdparty developers.

    If this where accumulated into an image in a proper way like Android based STB's i would be surten that Dreambox have many many years at the tip of the sword.


    This was close to happen with the DreamTV android project where I can install my Allt-I-Box or TeliaPlay app and watch linear TV and all Streaming Services of my subscription.

  • „Dream­box Seven Ultra HD“ in der Preview

    I do not think that the Seven will be the last Dreambox. On the contrary i think this will be the turning point where the next logic step will be a hybrid Dreambox.

    My Sat box from CanalDigital is a hybrid. I watch all linear TV direct from the satellite but i can also start from the beginning of a show.

    I have Catchup TV in the same box and an Weekly archive to chose from if i have missed something.


    All this provided by my Sat provider in a single box. And if the next step after Dreambox Seven is taken then there is a bright future still for Dreambox and DreamProperty :smiling_face:

  • „Dream­box Seven Ultra HD“ in der Preview

    If we should be very honest the main reason for most users in the past why they chose Dreambox was because of illegal use :winking_face:

    You could buy 1 subscription and share that with others.

    Yes lots of people also did buy the Dreambox as a hobby to learn and develop but the main customer did not do this.

    And that is still not the case.


    If customer demands change like drea is describing and i do agree with him. Well then like it or not if you still want to be on the marked then you have to adapt.

    Or else customers will chose other solutions.


    So it want be Streaming or linear tv who might be the reason for Dreambox and other STB's future. It will be the way vendors adapt to the new market and the new customers,

    Dreambox Seven will probably be a very good STB but it will not sell to others then the very few hobby developers and lucky us in Scandinavia who still can watch linear PayTV legal :winking_face:

  • Krogoth branch not possible to build anymore

    :grinning_face_with_smiling_eyes::grinning_face_with_smiling_eyes::grinning_face_with_smiling_eyes::grinning_face_with_smiling_eyes::grinning_face_with_smiling_eyes::grinning_face_with_smiling_eyes::grinning_face_with_smiling_eyes: seriously so we must now swear allegiance to python3 to be able and build an old Dreambox Image :grinning_squinting_face::grinning_squinting_face::grinning_squinting_face::grinning_squinting_face::grinning_squinting_face::grinning_squinting_face:


    But again the only one even taking time to try and digg up some information is dre

    I really must say that you always go the extra mile :thumbs_up: where the developers and DP is on some kind vacation :winking_face:


    Well let's get down on the knee and start swearing and see if this works :smiling_face_with_sunglasses:


    Again thanks dre for always going the extra mile for less skilled persons like me :smiling_face:

  • Krogoth branch not possible to build anymore

    So got passed the errors in my post above. Reason I run out of memory.


    I am using VMWare 16 pro. Ubuntu 18.04 assigned a 500gb disk

    2 Processors with 4 cores and started with 2Gb memory.


    To get pass the crash I increase the memory to 4Gb and got pass that error until again the same issue with another compile task.

    Now i increase the memory to 6Gb and got pass this error also,


    But of cause nothing works as it should and this damn setup tools crapp is here again.


    I build the Pyro like nothing with no issues and less memory and cpu assignment and direct from the git without any need for Docker

    I hope that maybe Ghost or some of the other devs can shade some light on this. Reichi


    dre have been very help full but since he have never encounter this setup tools error then i assume someone else have check this out


    Here is the log


  • Krogoth branch not possible to build anymore

    Hi


    I have battle this oe 2.5 krogoth image build. And I must say that this is so complicated.

    Just to do a simple image build.


    I am in no way an expert but i can build about any image there is for all Enigma2 systems except the damn krogoth :winking_face:

    I hade no chance at all until i did setup a VM ware Ubuntu 18.04 just as m0rphU

    Yes i even stole your username to be sure i copy your setup as described in your post. RE: Baut jemand mit Ubuntu 18.04?

    I Installed docker.io and all the suggested files for docker.


    Copy all of m0rphU telnet commands and so far so good everything whent fine just as in his post.

    But there it stops. after a good 600 tasks run the most irritating red crapp showed up and everything crashed.


    I have attached the crashlog but i assume as always there are a number of pre requested packages that should have been installed to avoid this.

    It would be very nice if someone could post a list of pre requested package that needs to be installed :smiling_face:

  • EPG favorites

    Your provider use https address for the epg source and there is no https support in the epg import plugin if not "Grumpy" has added this to the gutemines feeds plugin?

    Or you can download the only EPG Import plugin with ssl support from another forum. This is the reason why it works on your OpenSource image because the EPG Import plugin for all OE-A builds have https (ssl) support.


    So either do as he suggest the hard and complicated way,

    Or get the correct plugin and be done with it :winking_face:



    Yellow manual download

    DreamOS Expert "Grumpy" :thumbs_up: