Thanks: 0
Ergebnis 11 bis 18 von 18
Thema: Image veraltet, update
-
17.12.2016, 17:18 #11
- Registriert seit
- 27.11.2016
- Beiträge
- 8
- Thanks (gegeben)
- 0
- Thanks (bekommen)
- 0
- Total Downloaded
- 0
- Total Downloaded
- 0
Hallo,
ich habe trotz der Warnung, dass das Image veraltet ist die Software aktualisiert. Mir wurde versichert, dass es kein Problem ist.
Jetzt bootet die Box nicht mehr.
Was kann ich jetzt tun? Kann ich noch ein neues Image aufspielen? Und wenn ja wie funktioniert das?
Gruß
Mimbari.
-
Advertising
-
17.12.2016, 18:56 #12
- Registriert seit
- 13.04.2013
- Beiträge
- 105
- Thanks (gegeben)
- 77
- Thanks (bekommen)
- 10
- Total Downloaded
- 49,77 MB
- Total Downloaded
- 49,77 MB
Box 1:VU+ Solo 2Box 2:VU+ DUO 4KIch hoffe, Du hast Dir vorher das Image auf einen USB Stick gesichert, oder wenigstens die Einstellungem auf der Disk gesichert.
Ich hatte die Tage auch dieses Problem, habe also bei gelbem Image Status upgedatet. Die Box blieb dann irgendwo hängen.
Habe dann mittels USB Stick mein vorherige Backup-Version zurückgespielt
Der gelbe Status des Images steht jetzt schon eine ganze Weile an.
Warum das so ist, muß der Mod wal was zu sagen.
Ich würde jedenfalls mit dem jetzigen Erfahrungen nicht mehr bei gelb aktualisieren.
-
17.12.2016, 20:34 #13
- Registriert seit
- 24.06.2013
- Ort
- Österreich
- Beiträge
- 5.027
- Thanks (gegeben)
- 837
- Thanks (bekommen)
- 1492
- Total Downloaded
- 15,72 MB
- Total Downloaded
- 15,72 MB
Box 1:Zgemma H9.TwinBox 2:Edision Optimuss OS1+Box 3:Golden Interstar XPEED LX1Box 4:SpycatBox 5:AX HD60Du musst einfach ein neues Image einspielen. Auch wenn der Feed wieder grün zeigt, wirst du sonst wieder das gleiche Problem haben, wenn du ein Update machst.
Hier der Hintergrund.______________________
Hans
TV - Hisense Ulra HD
Eutelsat 13°E und Astra 19,2°E Unicable-Matrix mit Wide-LNB
-
18.12.2016, 00:56 #14
- Registriert seit
- 27.11.2016
- Beiträge
- 8
- Thanks (gegeben)
- 0
- Thanks (bekommen)
- 0
- Total Downloaded
- 0
- Total Downloaded
- 0
Ich hatte das alte Image zum Glück noch auf einem USB-Stick und knnte die Box wieder starten.
Ich habe folgende Imageversion: openatv-5.3-9910lx-20160910
Wenn ich jetzt auf die blaue Taste drücke bekomme ich die Meldung, dass ich ein Softwareproblem habe.
Unten folgt die Log-Datei:
Reicht es, wenn ich ein neues Image aufspiele und die Software akuallisiere, um das Problem zu zu beheben?
<?xml version="1.0" encoding="utf-8"?>
<openATV>
<enigma2>
<crashdate>So Dez 18 01:28:38 2016</crashdate>
<compiledate>Sep 9 2016</compiledate>
<contactemail>forum at www.opena.tv</contactemail>
<!-- Please email this crashlog to above address -->
<skin>MetrixHD/skin.xml</skin>
<sourcedate>2016-09-08</sourcedate>
<version>3.0.0</version>
</enigma2>
<image>
<stbmodel>7220S</stbmodel>
<kernelversion>
<=!=[=C=D=A=T=A=[
Linux 9910lx 4.0.1 #1 SMP Sat Jul 23 03:05:30 CEST 2016 mips GNU/Linux
]=]=>
</kernelversion>
<kernelcmdline>ubi.mtd=rootfs rootfstype=ubifs root=ubi0:rootfs bmem=192M@64M console=ttyS0,115200n8 </kernelcmdline>
<nimsockets>NIM Socket 0:</nimsockets>
<imageversion>
<=!=[=C=D=A=T=A=[
box_type=9910lx
build_type=0
version=5.3
build=0
date=20160809011054
comment=openATV
target=9
creator=openATV
url=http://www.opena.tv
catalog=http://www.opena.tv
]=]=>
</imageversion>
<imageissue>
<=!=[=C=D=A=T=A=[
Welcome to openATV for %h
openatv 5.3 %h
]=]=>
</imageissue>
</image>
<crashlogs>
<enigma2crashlog>
<=!=[=C=D=A=T=A=[
['menu_setup', 'Menu']
01:27:26.817 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:27:26.819 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:27:27.901 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:27:27.903 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:27:27.904 { } Components/ActionMap.py:46 action action -> OkCancelActions cancel
01:27:27.915 { } Screens/Screen.py:151 show [SCREENNAME] MenuSummary
01:27:27.928 { } Screens/Screen.py:151 show [SCREENNAME] ['menu_mainmenu', 'Menu']
01:27:28.202 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:27:28.204 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:27:28.854 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:27:28.857 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:27:28.858 { } Components/ActionMap.py:46 action action -> OkCancelActions cancel
01:27:28.877 { } Screens/Screen.py:151 show [SCREENNAME] InfoBarSummary
01:27:29.155 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:27:29.158 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:27:54.454 [ ] driver/rcinput.cpp:23 handleCode 1 8b 1
01:27:54.457 { } Screens/InfoBarGenerics.py:204 actionA KEY: 139 0 KEY_MENU MENU
01:27:54.459 { } Components/ActionMap.py:46 action action -> InfobarMenuActions mainMenu
01:27:54.490 { } skin.py:1034 readSkin [SKIN] processing screen menu_mainmenu:
01:27:54.801 { } skin.py:1034 readSkin [SKIN] processing screen MenuSummary:
01:27:54.807 { } Screens/Screen.py:151 show [SCREENNAME] MenuSummary
01:27:54.811 { } Screens/Screen.py:151 show [SCREENNAME] ['menu_mainmenu', 'Menu']
01:27:54.911 [ ] driver/rcinput.cpp:23 handleCode 0 8b 1
01:27:54.914 { } Screens/InfoBarGenerics.py:204 actionA KEY: 139 1 KEY_MENU MENU
01:27:56.199 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:27:56.202 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:27:56.500 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:27:56.502 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:27:56.583 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:27:56.586 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:27:56.884 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:27:56.886 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:27:56.899 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:27:56.901 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:27:57.200 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:27:57.202 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:27:58.186 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:27:58.188 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:27:58.487 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:27:58.489 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:27:58.935 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
01:27:58.937 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
01:27:58.939 { } Components/ActionMap.py:46 action action -> OkCancelActions ok
01:27:58.964 { } skin.py:1034 readSkin [SKIN] processing screen menu_setup:
01:27:59.160 { } skin.py:1034 readSkin [SKIN] processing screen MenuSummary:
01:27:59.167 { } Screens/Screen.py:151 show [SCREENNAME] MenuSummary
01:27:59.170 { } Screens/Screen.py:151 show [SCREENNAME] ['menu_setup', 'Menu']
01:27:59.235 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
01:27:59.239 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
01:28:00.412 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:00.415 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:01.006 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:01.008 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:01.020 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:01.023 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:01.595 [ ] driver/rcinput.cpp:23 handleCode 2 6c 1
01:28:01.598 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 2 KEY_DOWN DOWN
01:28:01.896 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:01.898 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:01.933 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:01.936 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:02.234 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:02.237 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:02.248 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:02.251 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:02.549 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:02.551 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:02.564 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:02.566 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:03.163 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:03.165 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:03.292 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:03.295 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:03.593 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:03.596 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:04.411 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
01:28:04.413 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
01:28:04.414 { } Components/ActionMap.py:46 action action -> OkCancelActions ok
01:28:04.429 { } skin.py:1034 readSkin [SKIN] processing screen ParentalControlSetup:
01:28:04.486 { } skin.py:1034 readSkin [SKIN] processing screen SetupSummary:
01:28:04.493 { } Screens/Screen.py:151 show [SCREENNAME] SetupSummary
01:28:04.497 { } Screens/Screen.py:151 show [SCREENNAME] ['ParentalControlSetup', 'Setup']
01:28:04.712 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
01:28:04.715 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
01:28:07.414 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:28:07.417 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:28:07.418 { } Components/ActionMap.py:46 action action -> SetupActions cancel
01:28:07.425 { } Screens/Screen.py:151 show [SCREENNAME] MenuSummary
01:28:07.432 { } Screens/Screen.py:151 show [SCREENNAME] ['menu_setup', 'Menu']
01:28:07.715 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:28:07.717 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:28:08.572 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:08.575 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:08.873 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:08.876 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:09.275 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
01:28:09.277 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
01:28:09.278 { } Components/ActionMap.py:46 action action -> OkCancelActions ok
01:28:09.288 { } Plugins/SystemPlugins/SoftwareManager/plugin.py:166 __init__ building menu entries
01:28:09.294 { } skin.py:1034 readSkin [SKIN] processing screen UpdatePluginMenu:
01:28:09.355 { } skin.py:1034 readSkin [SKIN] processing screen PluginBrowserSummary:
01:28:09.360 { } Screens/Screen.py:151 show [SCREENNAME] PluginBrowserSummary
01:28:09.364 { } Screens/Screen.py:151 show [SCREENNAME] UpdatePluginMenu
01:28:09.575 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
01:28:09.577 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
01:28:12.960 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:12.962 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:12.963 { } Components/ActionMap.py:46 action action -> WizardActions down
01:28:12.963 { W } Components/ActionMap.py:53 action unknown action WizardActions/down! typo in keymap?
01:28:13.497 [ ] driver/rcinput.cpp:23 handleCode 2 6c 1
01:28:13.499 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 2 KEY_DOWN DOWN
01:28:13.500 { } Components/ActionMap.py:46 action action -> WizardActions down
01:28:13.500 { W } Components/ActionMap.py:53 action unknown action WizardActions/down! typo in keymap?
01:28:13.797 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:13.799 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:13.872 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:13.876 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:13.877 { } Components/ActionMap.py:46 action action -> WizardActions down
01:28:13.877 { W } Components/ActionMap.py:53 action unknown action WizardActions/down! typo in keymap?
01:28:14.172 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:14.175 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:16.834 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
01:28:16.837 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
01:28:16.838 { } Components/ActionMap.py:46 action action -> WizardActions ok
01:28:16.846 { } skin.py:1034 readSkin [SKIN] processing screen FlashOnline:
01:28:16.920 { } skin.py:1034 readSkin [SKIN] processing screen SimpleSummary:
01:28:16.925 { } Screens/Screen.py:151 show [SCREENNAME] ['FlashOnline_summary', 'SimpleSummary']
01:28:16.928 { } Screens/Screen.py:151 show [SCREENNAME] FlashOnline
01:28:17.135 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
01:28:17.137 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
01:28:18.515 [ ] driver/rcinput.cpp:23 handleCode 1 18f 1
01:28:18.518 { } Screens/InfoBarGenerics.py:204 actionA KEY: 399 0 KEY_GREEN GREEN
01:28:18.816 [ ] driver/rcinput.cpp:23 handleCode 0 18f 1
01:28:18.818 { } Screens/InfoBarGenerics.py:204 actionA KEY: 399 1 KEY_GREEN GREEN
01:28:18.819 { } Components/ActionMap.py:46 action action -> ColorActions green
01:28:18.820 { } Plugins/SystemPlugins/SoftwareManager/Flash_online.py:53 Freespace [Flash Online] Free space on /media/hdd = 0 kilobytes
01:28:18.828 { } skin.py:1034 readSkin [SKIN] processing screen MessageBox:
01:28:18.867 { } skin.py:1034 readSkin [SKIN] processing screen MessageBox_summary:
01:28:18.873 { } Screens/Screen.py:151 show [SCREENNAME] ['MessageBox_summary', 'SimpleSummary']
01:28:18.877 { } Screens/Screen.py:151 show [SCREENNAME] ['MessageBox']
01:28:22.472 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:28:22.476 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:28:22.477 { } Components/ActionMap.py:46 action action -> MsgBoxActions cancel
01:28:22.481 { } Screens/Screen.py:151 show [SCREENNAME] ['FlashOnline_summary', 'SimpleSummary']
01:28:22.487 { } Screens/Screen.py:151 show [SCREENNAME] PluginBrowserSummary
01:28:22.489 { } Screens/Screen.py:151 show [SCREENNAME] FlashOnline
01:28:22.523 { } Screens/Screen.py:151 show [SCREENNAME] UpdatePluginMenu
01:28:22.773 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:28:22.777 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:28:24.427 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:24.429 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:24.430 { } Components/ActionMap.py:46 action action -> WizardActions down
01:28:24.430 { W } Components/ActionMap.py:53 action unknown action WizardActions/down! typo in keymap?
01:28:24.727 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:24.729 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:26.367 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
01:28:26.370 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
01:28:26.371 { } Components/ActionMap.py:46 action action -> WizardActions down
01:28:26.371 { W } Components/ActionMap.py:53 action unknown action WizardActions/down! typo in keymap?
01:28:26.659 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
01:28:26.661 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
01:28:30.069 [ ] driver/rcinput.cpp:23 handleCode 1 67 1
01:28:30.071 { } Screens/InfoBarGenerics.py:204 actionA KEY: 103 0 KEY_UP UP
01:28:30.072 { } Components/ActionMap.py:46 action action -> WizardActions up
01:28:30.073 { W } Components/ActionMap.py:53 action unknown action WizardActions/up! typo in keymap?
01:28:30.370 [ ] driver/rcinput.cpp:23 handleCode 0 67 1
01:28:30.372 { } Screens/InfoBarGenerics.py:204 actionA KEY: 103 1 KEY_UP UP
01:28:31.046 [ ] driver/rcinput.cpp:23 handleCode 1 67 1
01:28:31.049 { } Screens/InfoBarGenerics.py:204 actionA KEY: 103 0 KEY_UP UP
01:28:31.050 { } Components/ActionMap.py:46 action action -> WizardActions up
01:28:31.050 { W } Components/ActionMap.py:53 action unknown action WizardActions/up! typo in keymap?
01:28:31.347 [ ] driver/rcinput.cpp:23 handleCode 0 67 1
01:28:31.349 { } Screens/InfoBarGenerics.py:204 actionA KEY: 103 1 KEY_UP UP
01:28:31.795 [ ] driver/rcinput.cpp:23 handleCode 1 67 1
01:28:31.798 { } Screens/InfoBarGenerics.py:204 actionA KEY: 103 0 KEY_UP UP
01:28:31.799 { } Components/ActionMap.py:46 action action -> WizardActions up
01:28:31.799 { W } Components/ActionMap.py:53 action unknown action WizardActions/up! typo in keymap?
01:28:32.096 [ ] driver/rcinput.cpp:23 handleCode 0 67 1
01:28:32.098 { } Screens/InfoBarGenerics.py:204 actionA KEY: 103 1 KEY_UP UP
01:28:32.772 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:28:32.775 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:28:32.777 { } Components/ActionMap.py:46 action action -> WizardActions back
01:28:32.782 { } Screens/Screen.py:151 show [SCREENNAME] MenuSummary
01:28:32.790 { } Screens/Screen.py:151 show [SCREENNAME] ['menu_setup', 'Menu']
01:28:33.073 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:28:33.076 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:28:34.821 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:28:34.823 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:28:34.825 { } Components/ActionMap.py:46 action action -> OkCancelActions cancel
01:28:34.835 { } Screens/Screen.py:151 show [SCREENNAME] MenuSummary
01:28:34.847 { } Screens/Screen.py:151 show [SCREENNAME] ['menu_mainmenu', 'Menu']
01:28:35.122 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:28:35.124 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:28:35.265 [ ] driver/rcinput.cpp:23 handleCode 1 ae 1
01:28:35.267 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 0 KEY_EXIT EXIT
01:28:35.268 { } Components/ActionMap.py:46 action action -> OkCancelActions cancel
01:28:35.286 { } Screens/Screen.py:151 show [SCREENNAME] InfoBarSummary
01:28:35.566 [ ] driver/rcinput.cpp:23 handleCode 0 ae 1
01:28:35.568 { } Screens/InfoBarGenerics.py:204 actionA KEY: 174 1 KEY_EXIT EXIT
01:28:37.131 [ ] driver/rcinput.cpp:23 handleCode 1 191 1
01:28:37.133 { } Screens/InfoBarGenerics.py:204 actionA KEY: 401 0 KEY_BLUE BLUE
01:28:37.432 [ ] driver/rcinput.cpp:23 handleCode 0 191 1
01:28:37.435 { } Screens/InfoBarGenerics.py:204 actionA KEY: 401 1 KEY_BLUE BLUE
01:28:37.459 { } Components/ActionMap.py:46 action action -> InfobarExtensions quickmenu
01:28:38.206 { E } Screens/InfoBarGenerics.py:3010 quickmenuStart [INFOBARGENERICS] QuickMenu: error pipshow, starting Quick Menu
01:28:38.946 { D } Traceback (most recent call last):
01:28:38.946 { D } File "/usr/lib/enigma2/python/Components/ActionMap.py", line 48, in action
01:28:38.947 { D } File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 2994, in bluekey_qm
01:28:38.948 { D } File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 3011, in quickmenuStart
01:28:38.948 { D } File "/usr/lib/enigma2/python/Plugins/Extensions/Infopanel/QuickMenu.py", line 78, in <module>
01:28:38.949 { D } EOFError: EOF read where object expected
01:28:38.949 [ E ] python/python.cpp:209 call (PyObject_CallObject(<bound method HelpableActionMap.action of <Components.ActionMap.HelpableActionMap instance at 0x71647b98>>,('InfobarExtensions', 'quickmenu')) failed)
]=]=>
</enigma2crashlog>
</crashlogs>
</openATV>
-
18.12.2016, 08:00 #15
- Registriert seit
- 24.06.2013
- Ort
- Österreich
- Beiträge
- 5.027
- Thanks (gegeben)
- 837
- Thanks (bekommen)
- 1492
- Total Downloaded
- 15,72 MB
- Total Downloaded
- 15,72 MB
Box 1:Zgemma H9.TwinBox 2:Edision Optimuss OS1+Box 3:Golden Interstar XPEED LX1Box 4:SpycatBox 5:AX HD60Wenn du das neueste Image aufspielst brauchst du nicht wieder aktualisieren. Du hast ja dann das neueste Image inklusiver aller Aktualisierungen. Aber grundsätzlich sollten dann auch wieder normale Updates möglich sein.
______________________
Hans
TV - Hisense Ulra HD
Eutelsat 13°E und Astra 19,2°E Unicable-Matrix mit Wide-LNB
-
22.12.2016, 19:23 #16
- Registriert seit
- 01.09.2016
- Beiträge
- 34
- Thanks (gegeben)
- 10
- Thanks (bekommen)
- 3
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Octagon SF8008Box 2:DM 500HDBox 3:DM 500HDGuten Abend @all,
ich bin mir nicht sicher, ob es schon eine Lösung / Antwort bezüglich neuerer Updates gibt. Vor ca. 6 Tagen hatte ich auf eigenes Risiko ein Update "als ungeprüftes Update" durchgeführt. Danach ging, wie bei vielen anderen auch, der Boot-Vorgang der Protek nicht mehr. Ich hatte mir dann ein neues Image von hier gezogen und hatte die Protek neu geflasht. Alles gut gelaufen. Einstellungen konnte ich auch wieder einspielen. Ging razz fazz.
Gestern wollte ich wieder einmal "updaten" und es kam leider wieder die Info "ungeprüftes Update" .... "auf eigenes Risiko durchführen" usw. - gibt es ggf, ein Problem mit den Updates? Oder sollte ich die Box nochmal mit einem ganz aktuellem Image (z.B. von heute) flashen - trotz des Images vor 6 Tagen?
Wäre klasse, wenn mir jemand kurz weiterhelfen könnte.
VG
PressiesGeändert von Pressies (22.12.2016 um 21:22 Uhr)
-
22.12.2016, 20:18 #17giopetGast
Bitte lasst doch mal erstmal das Online Update,macht doch ein Online Flash mit Einstellungen Übernahme und gut ist,wichtig ist natürlich,das ihr vorher eure Einstellungen sichert,falls noch nicht gemacht.
-
22.12.2016, 20:48 #18
- Registriert seit
- 01.09.2016
- Beiträge
- 34
- Thanks (gegeben)
- 10
- Thanks (bekommen)
- 3
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Octagon SF8008Box 2:DM 500HDBox 3:DM 500HDEinstellungen sind zum Glück gesichert. Aber es muss doch einen Grund geben, wieso die Information zwecks des "ungeprüften Updates" gibt. Ging doch die ganze Zeit sehr gut und lief prima
Lesezeichen