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 after pressing green button to see scheduled timers

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
1
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Attachments
Results 1 to 6 of 6

Thread: crash log after pressing green button to see scheduled timers

  1. #1
    baz2011uk's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Oct 2015
    Posts
    117
    Thanks
    21
    Thanked 17 Times in 12 Posts

    crash log after pressing green button to see scheduled timers

    had this the other day but been busy till now to upload the error log

    after pressing green button to see scheduled timers it crashed to a black screen followed up with a restart working fine after

    see attached log green button crash.txt

  2. #2
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    Exactly the same for me tonight et10k, 4.2.006. First crash this year.

    Box had booted from deep standby at about 18:25, had recorded 2 programmes, and was in the middle of a 3rd when it crashed.

    It should have been recording in standby, but wasn't for some reason. (Seems to happen more often now than it used to.)

    Pressing green is usually the first thing I do when accessing the box.

    The only thing I've done recently (last night) was to try out iSkin, but went straight back to ViX-Night-HD.

  3. #3
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,362
    Thanks
    6,443
    Thanked 9,160 Times in 6,235 Posts
    That fatal signal issue comes up in a few logs
    Code:
    <  3222.472> [eInputDeviceInit] 0 18f 1
    <  3222.473> [InfoBarGenerics] KEY: 399 GREEN
    <  3222.502> [ActionMap] InfobarSubserviceSelectionActions GreenPressed
    <  3222.552> [Skin] processing screen TimerEditList:
    <  3222.622> [Skin] processing screen TimerEditListSummary:
    <  3222.842> PC: 00501d94
    <  3222.842>     00000000 00000001 00000249 00000001
    <  3222.842>     011a3078 011a4d68 2f399968 76b89738
    <  3222.842>     00000067 00000053 2038353a 202e2e2e
    <  3222.842>     303a3232 36282036 696d2038 00660000
    <  3222.842>     7fe6dd2c 011a4d68 7fe6dca0 00000004
    <  3222.842>     00000000 0000008e 007507a4 71b01d90
    <  3222.842>     00664b24 76a85000 00000000 00000000
    <  3222.842>     76baae10 7fe6dc08 00000002 00561f50
    <  3222.859> Backtrace:
    <  3222.859> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x45DDD4]
    <  3222.860> /usr/bin/enigma2(n/a) [0x501D96]
    <  3222.860> /usr/bin/enigma2(_Z14SwigFromPythonR4ePtrI7gPixmapEP7_object) [0x561F50]
    <  3222.860> /usr/bin/enigma2(_ZN26eListboxPythonMultiContent5paintER8gPainterR12eWindowStyleRK6ePointi) [0x504FC0]
    <  3222.860> /usr/bin/enigma2(_ZN8eListbox5eventEiPvS0_) [0x501B48]
    <  3222.861> /usr/bin/enigma2(_ZN7eWidget7doPaintER8gPainterRK7gRegioni) [0x50B918]
    <  3222.861> /usr/bin/enigma2(_ZN7eWidget7doPaintER8gPainterRK7gRegioni) [0x50B8A4]
    <  3222.861> /usr/bin/enigma2(_ZN7eWidget7doPaintER8gPainterRK7gRegioni) [0x50B8A4]
    <  3222.861> /usr/bin/enigma2(_ZN14eWidgetDesktop10paintLayerEP7eWidgeti) [0x50D3E8]
    <  3222.861> /usr/bin/enigma2(_ZN14eWidgetDesktop5paintEv) [0x50D89C]
    <  3222.862> /usr/bin/enigma2(_ZN6eTimer8activateEv) [0x4629C8]
    <  3222.862> /usr/bin/enigma2(_ZN9eMainloop15processOneEventEjPP7_object9ePyObject) [0x463344]
    <  3222.862> /usr/bin/enigma2(_ZN9eMainloop7iterateEjPP7_object9ePyObject) [0x463484]
    <  3222.862> -------FATAL SIGNAL (11)

  4. #4
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    Happened again tonight, but this time I can repeat the crash.... Green for timers followed by info.

    This is the 2nd crash after an enigma restart after the first one.

  5. #5
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,419
    Thanks
    997
    Thanked 2,894 Times in 2,247 Posts
    Which skin? Ignore its in the log
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
    ------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  6. #6

    Title
    Senior Member
    Join Date
    Mar 2015
    Posts
    1,184
    Thanks
    31
    Thanked 371 Times in 239 Posts
    Hi Ccs,

    The cause of the "< 6994.334> KeyError: 'longfulldate'" crash has been identified, verified, corrected and tested. Pull Request #105 has been created to correct the error.

    My apologies for the error and the inconvenience.

    Regards,
    Ian.

  7. The Following 3 Users Say Thank You to IanSav For This Useful Post:

    abu baniaz (15-01-17),ccs (15-01-17),Rob van der Does (15-01-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.