Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.

View Entry Info: Crash log reports wrong model (cosmetic problem)

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
5.0.013
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Results 1 to 7 of 7

Thread: Crash log reports wrong model (cosmetic problem)

  1. #1

    Title
    Senior Member
    Join Date
    Mar 2014
    Posts
    290
    Thanks
    100
    Thanked 73 Times in 59 Posts

    Crash log reports wrong model (cosmetic problem)

    I made the move to NCam 1.5-r0 yesterday and the LX3 crashed a couple of times - nothing major but as a result I noticed that the box type reported in the debug logs is mbultra instead of xpeedlx3 or whatever it should be.

    Crashdate = Sun Apr 23 19:33:18 2017

    Creator = OpenViX
    Version = 5.0
    Build = 013
    Type = release
    Machine = mbultra
    URL = http://www.world-of-satellite.com
    Compiled = Apr 19 2017
    Skin = iSkin-Dark/skin.xml
    Component = enigma2, signal
    Only cosmetic but reporting it here thank-you

  2. #2
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,629
    Thanks
    2,006
    Thanked 4,953 Times in 3,274 Posts
    Do you, or have you ever, owned an mbultra?
    Help keep OpenViX servers online.Please donate!

  3. #3

    Title
    Senior Member
    Join Date
    Mar 2014
    Posts
    290
    Thanks
    100
    Thanked 73 Times in 59 Posts
    Hi Heuvos, no I've never had one of those boxes, although looking at that box I'm guessing it's the same factory so maybe something slipped through in the code?

  4. #4
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,360
    Thanks
    6,442
    Thanked 9,160 Times in 6,235 Posts
    I mentioned this issue a while back. Cropped up a few months ago IIRC

  5. #5
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,360
    Thanks
    6,442
    Thanked 9,160 Times in 6,235 Posts
    Tried to reproduce it, but this time it was OK.

    Crash logs, not debug logs by the way.

  6. The Following User Says Thank You to abu baniaz For This Useful Post:

    aido (25-04-17)

  7. #6

    Title
    Senior Member
    Join Date
    Mar 2014
    Posts
    290
    Thanks
    100
    Thanked 73 Times in 59 Posts
    Exactly right, it's the crash logs not debug logs, I can't edit the thread title though - I'm blaming all the beer over the bank holiday for frazzling my mind

  8. #7
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,790
    Thanks
    237
    Thanked 1,658 Times in 1,306 Posts
    Quote Originally Posted by aido View Post
    Exactly right, it's the crash logs not debug logs, I can't edit the thread title though
    Fixed.....
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  9. The Following User Says Thank You to birdman For This Useful Post:

    aido (25-04-17)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.