Danke pclin für deine Gutheit und Weisheit!
Es tut immer gut zu lesen, wie man nach der Hand schlägt, die einem gefüttert hat!
a) war auf der Box nichts von Gemini
b) Ich bin jetzt auch ganz froh, dass Du bei kodi-18 nicht dabei bist.
Danke pclin für deine Gutheit und Weisheit!
Es tut immer gut zu lesen, wie man nach der Hand schlägt, die einem gefüttert hat!
a) war auf der Box nichts von Gemini
b) Ich bin jetzt auch ganz froh, dass Du bei kodi-18 nicht dabei bist.
Mit dem Menu hat es wohl auch nix zu tun, weil es beim Ausführen über das pluginmenu auch passiert.
ist wohl nur so, weil kodi mit dem EGL läuft? Geminiterm (fb Grafik) geht ganz normal.
Aber nach kodi beenden geht ab dem neuen rel wohl das:
...
def __runFinished(self,retval):
print "[XBMCMediaCenter] - __runFinished"
eDBoxLCD.getInstance().unlock()
eDBoxLCD.getInstance().update()
fbClass.getInstance().unlock()
...
nicht mehr??
Ich hänge das plugin hier mal an, kodi habt Ihr ja im oe.
Bitte schaut mal warum kodi mit dem neuen e2 rel die GUI/Display der Box weghängt.
Danke
Ist aber nicht nur hier so wenn man kodi startet.
Ist bei jedem.
Ich hier hab ja kodi-18. Aber das geht auch mit kodi-17 so. Man beendet kodi, das TV Bild kommt wieder man kann noch mit <<, >> umschalten, aber die e2 GUI wird nicht mehr sichtbar und das Display hängt auch. Geht erst so ab dem neuen Enigma2 rel.
Ich habe gerade den Gegentest mit einer anderen binär Anwendung (geminiterminal) gemacht aus dem Bluepanel (Menu) und da geht es ganz normal.
Das ganze ist komischer Weise nur bei kodi??
k.a. warum
Aber der Fehler läßt sich leider sofort reproduzieren.
Ich habe jetzt eventuell was anders in Verdacht. Es hat sich doch was im Menu geändert (Radio oben in dem neuem Rel.) und mein plugin macht da einen Eintrag und startet von da.
Ich hack mal noch ein bisschen nach.
Danke schon mal für die Antwort.
auf der dm7080 geht der eConsoleAppContainer() auch nicht mehr.
http://www.i-have-a-dreambox.c…ostid=2221546#post2221546
ich habe das auch bemerkt auf der dm920 im aktuellen enigma2
root@dm7080:~# kodi
kodi-dreambox: ../git/src/v3d.c:667: bcmDisplayBufferDestroy: Assertion `mem->magic == DMEGL_PIXMAP_MAGIC' failed.
/usr/bin/kodi: line 223: 1089 Aborted (core dumped) ${KODI_BINARY} $SAVED_ARGS
Crash report available at /root/kodi_crashlog-20181028_203706.log
Alles anzeigen
20:37:05.005 T:1929302016 NOTICE: CDreamboxUtils::GetNativeResolution mode: 1080p
20:37:05.005 T:1929302016 NOTICE: CDreamboxUtils::SetFramebufferResolution width: 1920 height: 1080
20:37:05.008 T:1929302016 NOTICE: CDreamboxUtils::GetNativeResolution mode: 1080p
20:37:05.009 T:1929302016 NOTICE: Found resolution 640 x 480 with 640 x 480i @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 720 x 576 with 720 x 576i @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080i @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1280 x 720 with 1280 x 720 @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 640 x 480 with 640 x 480 @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080i @ 50.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 24.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 25.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 30.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 50.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1280 x 720 with 1280 x 720 @ 24.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 1280 x 720 with 1280 x 720 @ 50.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 720 x 576 with 720 x 576 @ 60.000000 Hz
20:37:05.009 T:1929302016 NOTICE: Found resolution 640 x 480 with 640 x 480 @ 60.000000 Hz
20:37:05.010 T:1929302016 NOTICE: Found resolution 800 x 600 with 800 x 600 @ 60.000000 Hz
20:37:05.010 T:1929302016 NOTICE: Found resolution 1024 x 768 with 1024 x 768 @ 60.000000 Hz
20:37:05.010 T:1929302016 NOTICE: Found resolution 1366 x 768 with 1366 x 768 @ 60.000000 Hz
20:37:05.010 T:1929302016 NOTICE: Found (1920x1080@60.000000) at 19, setting to RES_DESKTOP at 16
20:37:05.022 T:1929302016 NOTICE: EGL_VERSION = 1.4
20:37:05.023 T:1929302016 NOTICE: EGL_VENDOR = Broadcom
20:37:05.023 T:1929302016 NOTICE: EGL_EXTENSIONS = EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_vg_parent_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_lock_surface EGL_KHR_fence_sync EGL_BRCM_image_update_control
20:37:05.023 T:1929302016 NOTICE: EGL_CLIENT_EXTENSIONS = NULL
20:37:05.023 T:1929302016 NOTICE: Checking resolution 16
20:37:05.027 T:1929302016 NOTICE: GL_VENDOR = Broadcom
20:37:05.027 T:1929302016 NOTICE: GL_RENDERER = VideoCore IV HW (V3D-435)
20:37:05.027 T:1929302016 NOTICE: GL_VERSION = OpenGL ES 2.0
20:37:05.027 T:1929302016 NOTICE: GL_SHADING_LANGUAGE_VERSION = OpenGL ES GLSL ES 1.00
20:37:05.027 T:1929302016 NOTICE: GL_EXTENSIONS = GL_OES_compressed_ETC1_RGB8_texture GL_OES_compressed_paletted_texture GL_OES_texture_npot GL_OES_depth24 GL_OES_vertex_half_float GL_OES_EGL_image GL_EXT_discard_framebuffer GL_OES_rgb8_rgba8 GL_OES_depth32 GL_APPLE_rgb_422 GL_OES_packed_depth_stencil GL_EXT_debug_marker GL_EXT_multisampled_render_to_texture
hier crasht das
kann mir ein developer einen Hinweis geben durch welche gl Funktion das benutzt wird? Ich tappe da im dunkeln.
Auf armhf geht das mit GLES3.
Es fehlt das kernel modul rfkill, wenn man es dazubaut geht schon mal eine
"Microsoft Wedge Mobile Keyboard" BT
root@dm7080:/usr/lib/bluez/test# bluetoothctl
[NEW] Controller 00:15:83:15:A3:10 dm7080 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent KeyboardOnly
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:15:83:15:A3:10 Discovering: yes
[NEW] Device 7C:1E:52:0B:0D:97 7C-1E-52-0B-0D-97
[CHG] Device 7C:1E:52:0B:0D:97 LegacyPairing: no
[CHG] Device 7C:1E:52:0B:0D:97 Name: Microsoft Wedge Mobile Keyboard
[CHG] Device 7C:1E:52:0B:0D:97 Alias: Microsoft Wedge Mobile Keyboard
[CHG] Device 7C:1E:52:0B:0D:97 LegacyPairing: yes
[bluetooth]# pair 7C:1E:52:0B:0D:97
Attempting to pair with 7C:1E:52:0B:0D:97
[CHG] Device 7C:1E:52:0B:0D:97 Connected: yes
[agent] PIN code: 498013
[CHG] Device 7C:1E:52:0B:0D:97 Modalias: usb:v045Ep0790d0403
[CHG] Device 7C:1E:52:0B:0D:97 UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 7C:1E:52:0B:0D:97 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 7C:1E:52:0B:0D:97 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 7C:1E:52:0B:0D:97 Paired: yes
Pairing successful
[CHG] Device 7C:1E:52:0B:0D:97 Connected: no
[bluetooth]# trust 7C:1E:52:0B:0D:97
[CHG] Device 7C:1E:52:0B:0D:97 Trusted: yes
Changing 7C:1E:52:0B:0D:97 trust succeeded
[bluetooth]# connect 7C:1E:52:0B:0D:97
Attempting to connect to 7C:1E:52:0B:0D:97
[CHG] Device 7C:1E:52:0B:0D:97 Connected: yes
Connection successful
[Microsoft Wedge Mobile Keyboard]#
Alles anzeigen
Alles anzeigenDie 520 stirbt eh aus, nachdem nun idiotischerweise alle anfangen nur noch FHD Skins zu bauen
Das macht ja mit den schnellen Boxen schon kein Spaß... von der 52x wollen wir dann mal gar nicht sprechen.
*kopfschüttel*
cya
P.S. Bitte nicht ganz ernst nehmen das ganze... wir werden den Support nicht einstellen oder so für die 520.... aber FHD Skins machen trotzdem keinen Sinn
kann ich nur mitschütteln
root@dm900:/usr/lib/bluez/test# hciconfig hci0 up
root@dm900:/usr/lib/bluez/test# hcitool scan
Scanning ...
00:1F:81:86:86:93 S10
root@dm900:/usr/lib/bluez/test# bluetoothctl
[NEW] Controller 00:02:72:C3:7E:4C dm900 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:02:72:C3:7E:4C Discovering: yes
[NEW] Device 00:1F:81:86:86:93 00-1F-81-86-86-93
[CHG] Device 00:1F:81:86:86:93 LegacyPairing: no
[CHG] Device 00:1F:81:86:86:93 Name: S10
[CHG] Device 00:1F:81:86:86:93 Alias: S10
[CHG] Device 00:1F:81:86:86:93 LegacyPairing: yes
[bluetooth]# pair 00:1F:81:86:86:93
Attempting to pair with 00:1F:81:86:86:93
[CHG] Device 00:1F:81:86:86:93 Connected: yes
[CHG] Device 00:1F:81:86:86:93 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1F:81:86:86:93 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1F:81:86:86:93 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1F:81:86:86:93 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1F:81:86:86:93 Paired: yes
Pairing successful
[CHG] Device 00:1F:81:86:86:93 Connected: no
[bluetooth]# connect 00:1F:81:86:86:93
Attempting to connect to 00:1F:81:86:86:93
Failed to connect: org.bluez.Error.Failed
[bluetooth]# exit
Agent unregistered
[DEL] Controller 00:02:72:C3:7E:4C dm900 [default]
root@dm900:/usr/lib/bluez/test# systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2017-08-10 13:07:37 CEST; 4min 55s ago
Docs: man:bluetoothd(8)
Main PID: 27540 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─27540 /usr/libexec/bluetooth/bluetoothd
Aug 10 13:07:37 dm900 systemd[1]: Starting Bluetooth service...
Aug 10 13:07:37 dm900 bluetoothd[27540]: Bluetooth daemon 5.37
Aug 10 13:07:37 dm900 systemd[1]: Started Bluetooth service.
Aug 10 13:07:37 dm900 bluetoothd[27540]: Starting SDP server
Aug 10 13:07:37 dm900 bluetoothd[27540]: Failed to open RFKILL control device
Aug 10 13:07:37 dm900 bluetoothd[27540]: Bluetooth management interface 1.4 initialized
Aug 10 13:07:37 dm900 bluetoothd[27540]: Failed to obtain handles for "Service Changed" charact
Aug 10 13:11:27 dm900 bluetoothd[27540]: a2dp-sink profile connect failed for 00:1F:81:86:86:93
Alles anzeigen
Was fehlt? Geht dass überhaupt noch?
LG Emanuel
ist nur ein bug, repariert sicher bald wer:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> getInputDevices < ['event4', 'event3', 'event2', 'event1', 'event0']
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> evdev < event4
[iInputDevices] getInputDevices <ERROR: ioctl(EVIOCGNAME): [Errno 22] Invalid argument >
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> evdev < event3
[iInputDevices] getInputDevices <ERROR: ioctl(EVIOCGNAME): [Errno 22] Invalid argument >
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> evdev < event2
[iInputDevices] getInputDevices <ERROR: ioctl(EVIOCGNAME): [Errno 22] Invalid argument >
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> evdev < event1
[iInputDevices] getInputDevices <ERROR: ioctl(EVIOCGNAME): [Errno 22] Invalid argument >
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> evdev < event0
[iInputDevices] getInputDevices <ERROR: ioctl(EVIOCGNAME): [Errno 22] Invalid argument >
Alles anzeigen
Ich hab es jetzt mal angepasst, es rennt scheinbar besser, aber der dm900 meldet immer noch den Fehler:
...
action -> SetupActions ok
[MyScreen] push 0
[MyScreen][MPWorker] task push 1
[MyScreen] push 2
[MyScreen] push 3
[MPWorker] [MyScreen] push 4
task 1 running cpu core: 1
0 running cpu core: 0
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 2 running cpu core: 0
[MyScreen] push 5
[EPGC] cleanup invalid data
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 3 running cpu core: 0
[MyScreen] push 6
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 4 running cpu core: 1
[MyScreen] push 7
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 5 running cpu core: 1
[MyScreen] push 8
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 6 running cpu core: 0
[MyScreen] push 9
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 7 running cpu core: 1
ERROR reading PES (fd=92) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 92(8)
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MPWorker] task 8 running cpu core: 1
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 9 running cpu core: 0
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
action -> SetupActions ok
[MyScreen] push 0
[MPWorker] task 0 running cpu core: 1
[MyScreen] push 1
[MPWorker] task 1 running cpu core: 0
[MyScreen] push 2
[MyScreen] push 3
[MyScreen] push 4
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 2 running cpu core: 0
[MyScreen] push 5
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 3 running cpu core: 1
[MyScreen] push 6
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 4 running cpu core: 0
[MyScreen] push 7
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 5 running cpu core: 1
[MyScreen] push 8
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 6 running cpu core: 0
[MyScreen] push 9
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 7 running cpu core: 1
action -> SetupActions ok
[MyScreen] push 0
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 8 running cpu core: 0
[MyScreen] push 1
main thread is non-idle! display spinner!
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MPWorker] task 9 running cpu core: 1
[MyScreen] push 2
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MPWorker] task 0 running cpu core: 0
[MyScreen] push 3
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
[MPWorker] task 1 running cpu core: 1
[MyScreen] push 4
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 2 running cpu core: 0
[MyScreen] push 5
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 3 running cpu core: [MyScreen] push 6
1
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 4 running cpu core: 1
[MyScreen] push 7
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 5 running cpu core: 0
[MyScreen] push 8
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 6 running cpu core: 1
[MyScreen] push 9
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 7 running cpu core: 1
action -> SetupActions ok
[MyScreen] push 0
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 8 running cpu core: 0
[MyScreen] push 1
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MPWorker] task 9 running cpu core: 1
[MyScreen] push 2
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MPWorker] task 0 running cpu core: 0
[MyScreen] push 3
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 1 running cpu core: 0
[MyScreen] push 4
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
[MPWorker] task 2 running cpu core: 1
[MyScreen] push 5
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 3 running cpu core: 0
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 4 running cpu core: 1
[MyScreen] push 6
[MyScreen] push 7
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 5 running cpu core: 0
[MyScreen] push 8
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 6 running cpu core: 1
[MyScreen] push 9
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 7 running cpu core: 0
ERROR reading PES (fd=92) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 92(8)
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 8 running cpu core: 1
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MPWorker] task 9 running cpu core: 0
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
[EPGC] cleanupOutdated
...
Alles anzeigen
Danke schon mal
Ich hab mich mal an einem Testplugin für Multitasking probiert, keine Ahnung ob das so richtig ist. *duq*
Mir ist dabei nur aufgefallen, dass der dm900 kernel beim 2. Aufruf der Funktion fast immer einen
Filedevice Error meldet.
Die laufende e2 Sitzung im Shell kann ich dann auch nur mit 2 mal ^C abbrechen - siehe log, Testplugin im Anhang.
MP-Test log dm900:
...
action -> SetupActions ok
[MyScreen] push 0
[MyScreen] push 1
[MyScreen] push 2
[MPWorker] task 0 running cpu core: 1
[MPWorker] task 1 running cpu core: 0
[MyScreen] push 3
[MyScreen] push 4
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 2 running cpu core: 1
[MyScreen] push 5
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 3 running cpu core: 1
[MyScreen] push 6
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 4 running cpu core: 0
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 5 running cpu core: 1
[MyScreen] push 7
[MyScreen] push 8
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 6 running cpu core: 0
[MyScreen] push 9
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 7 running cpu core: 1
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 8 running cpu core: 0
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MPWorker] task 9 running cpu core: 1
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
action -> SetupActions ok
[MyScreen] push 0
[MyScreen] push[MPWorker] task 0 running cpu core: 1
1
[MyScreen] push 2
[MyScreen] push 3
[MPWorker] task 1 running cpu core: 0
[MyScreen] push 4
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 2 running cpu core: 1
[MyScreen] push 5
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 3 running cpu core: 0
[MyScreen] push 6
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 4 running cpu core: 0
[MyScreen] push 7
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 5 running cpu core: 0
[MyScreen] push 8
[EPGC] schedule finished(1483408043)
[EPGC] stop caching events(1483408043)
[EPGC] next update in 60 min
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 6 running cpu core: 1
[MyScreen] push 9
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 7 running cpu core: 0
ERROR reading PES (fd=93) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 93(8)
ERROR reading PES (fd=95) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 95(8)
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 8 running cpu core: 1
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MPWorker] task 9 running cpu core: 1
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
...
Alles anzeigen
MP-Test log dm7080:
...
[MyScreen] push 0
[MyScreen][MPWorker] task 0 running cpu core: 3
push 1
[MPWorker] task 1 running cpu core: 1
[MyScreen] push 2
[MPWorker] task 2 running cpu core: 0
[MyScreen] push 3
[MyScreen][MPWorker] task 3 running cpu core: 2
push 4
[MyScreen] push 5
[MyScreen] push 6
[MyScreen] push 7
[MyScreen] push 8
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 4 running cpu core: 3
[MyScreen] push 9
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 5 running cpu core: 1
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 6 running cpu core: 2
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MPWorker] task 7 running cpu core: 3
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 8 running cpu core: 2
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 9 running cpu core: 1
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
nr_read 19209 nr_write 74
sum 19283 prev_sum 19283
hdd IDLE!
[IDLE] 579.630295038 60 True
action -> SetupActions ok
[MyScreen] push 0
[MyScreen] [MPWorker] task push 1
[MyScreen]0 running cpu core: 0
[MPWorker] push 2
[MyScreen] task 1[MPWorker] task push 2 running cpu core:3
[MyScreen]running cpu core: 3 2[MPWorker] task
3 running cpu core: 1
push 4
[MyScreen] push 5
[MyScreen] push 6
[MyScreen] push 7
[MyScreen] push 8
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 4 running cpu core: 2
[MyScreen] push 9
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 5 running cpu core: 0
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 6 running cpu core: 0
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 7 running cpu core: 3
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 8 running cpu core: 1
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MPWorker] task 9 running cpu core: 3
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
action -> SetupActions ok
[MyScreen] push 0
[MyScreen] [MPWorker] push 1task 0 running cpu core: 2
[MyScreen][MPWorker] task 1 running cpu core: 0
push 2
[MPWorker] task 2 running cpu core: 1
[MyScreen] push 3
[MyScreen] [MPWorker] task push 4
[MyScreen] push 5
3 [MyScreen]running cpu core: 3
push 6
[MyScreen] push 7
[MyScreen] push 8
[MyScreen] Hallo Welt! 0
[MPWorker] task 0 finished!
[MPWorker] task 4 running cpu core: 2
[MyScreen] push 9
[MyScreen] Hallo Welt! 2
[MPWorker] task 2 finished!
[MPWorker] task 5 running cpu core: 1
nr_read 19209 nr_write 74
sum 19283 prev_sum 19283
hdd IDLE!
[IDLE] 585.853872061 60 True
[MyScreen] Hallo Welt! 3
[MPWorker] task 3 finished!
[MPWorker] task 6 running cpu core: 3
[MyScreen] Hallo Welt! 1
[MPWorker] task 1 finished!
[MPWorker] task 7 running cpu core: 0
[MyScreen] Hallo Welt! 6
[MPWorker] task 6 finished!
[MPWorker] task 8 running cpu core: 3
[MyScreen] Hallo Welt! 5
[MPWorker] task 5 finished!
[MPWorker] task 9 running cpu core: 1
[MyScreen] Hallo Welt! 4
[MPWorker] task 4 finished!
[MyScreen] Hallo Welt! 7
[MPWorker] task 7 finished!
[MyScreen] Hallo Welt! 9
[MPWorker] task 9 finished!
[MyScreen] Hallo Welt! 8
[MPWorker] task 8 finished!
It's now Di 03 Jan 2017 02:29:31 CET
...
Alles anzeigen
entsteht z.B. : dm900
Referenzbeispiel im Anhang
...
create buffer for widget 820 x 570
action -> WizardActions ok
[Hallo World] start
Looking for embedded skin
create buffer for widget 960 x 690
FBIO_ACCEL (Invalid argument)
ACCEL BLIT FAILED!!
src surface addr 3dd92000, bypp 4, pixelformat 8888061f, valid 1, size 170:250
srcArea: 0 166 15 0
dstArea: 30 464 30 2
blit: -> 30.125 340:510 -> 30.125 340:510, flags=6
clip rect: 30 464 30 2
FBIO_ACCEL (Invalid argument)
ACCEL BLIT FAILED!!
src surface addr 3dd92000, bypp 4, pixelformat 8888061f, valid 1, size 170:250
srcArea: 160 166 10 0
dstArea: 350 464 20 2
blit: -> 30.125 340:510 -> 30.125 340:510, flags=6
clip rect: 350 464 20 2
[EPGC] nownext finished(1483276317)
...
Alles anzeigen
also ich habe auch mal das skin im Bildbetrachter auf ca. 100x100 angepasst, da komm ich gar nicht so weit
hdd was accessed since previous check!
[IDLE] 0 600 False
[ePicLoad] Unsupported file format
[ePicLoad] Unsupported file format
action -> DirectionActions down
[ePicLoad] Unsupported file format
action -> DirectionActions downUp
unknown action DirectionActions/downUp! typo in keymap?
action -> DirectionActions down
before: 1
[ePicLoad] get Thumbnail... /media/network/dm7080/pixmap/Ilda-Editor1.png
[ePicLoad] Cache File found
[ePicLoad] finished decoding /media/network/dm7080/pixmap/Ilda-Editor1.png.
before: 1
[ePicLoad] get Thumbnail... /media/network/dm7080/pixmap/Ilda-Editor2.png
[ePicLoad] Cache File found
[ePicLoad] finished decoding /media/network/dm7080/pixmap/Ilda-Editor2.png.
before: 1
[ePicLoad] get Thumbnail... /media/network/dm7080/pixmap/Ilda-Editor4.png
[ePicLoad] Cache File found
[ePicLoad] finished decoding /media/network/dm7080/pixmap/Ilda-Editor4.png.
before: 1
[ePicLoad] get Thumbnail... /media/network/dm7080/pixmap/Ilda-Editor5.png
[ePicLoad] Cache File found
EGL Error: 12301 (Invalid surface)
Python stack trace:
/usr/lib/enigma2/python/Plugins/Extensions/PicturePlayer/plugin.py(451): showPicFATAL: dereferenced ePtr<Cfilepara> NIL... abort!!
/usr/lib/enigma2/python/enigma.py(7376): __call__
/usr/lib/enigma2/python/e2reactor.py(191): mainLoop
/usr/lib/python2.7/site-packages/twisted/internet/base.py(1190): run
/usr/lib/enigma2/python/mytest.py(177): runReactor
/usr/lib/enigma2/python/mytest.py(586): runScreenTest
/usr/lib/enigma2/python/mytest.py(1): <module>
mainloop seems busy... crash from this thread
Segmentation fault
0xccc28(sp=0x8964e808) <eFatal(char const*, ...)+108>
0xb1bac(sp=0x8964ec30) <_init+17116>
0x1fa284(sp=0x8964ec40) <ePicLoad::gotMessage(ePicLoad::Message const&)+784>
0x1fcde4(sp=0x8964ec80) <loadPic(ePtr<gPixmap>&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int, int, int, int, int, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+2420>
0xc8600(sp=0x8964ece0) <eSocketNotifier::activate(int)+240>
0xca14c(sp=0x8964ed10) <eMainloop_native::processOneEvent(int)+2664>
0xca270(sp=0x8964ed80) <eMainloop_native::runLoop()+44>
0xe0c2c(sp=0x8964ed88) <eThread::wrapper(void*)+64>
0xb3dc10c0(sp=0x8964ed98) <__pthread_get_minstack+6076>
Alles anzeigen
glaub aber, dass liegt an dem Plugin (unsicherer Seitenwechsel)
ePicLoad skalierte kein PNG (1920x1080) in die Listeneintrag-Pixmap (100x100),
es bleibt unsichtbar.
Der Pointer ist aber nicht None
Meldungen im log:
[ePicLoad] setPara max-X=100 max-Y=100 aspectRatio=11520:11520 cache=0 resize=1 bg=#00000000
...
[ePicLoad] finished decoding /media/network/dm7080/pixmap/w10.png.
...
ignored x down scale 0:0 1920x1080 -> 15:229 100x56 (19.20)
ignored x down scale 0:0 1920x1080 -> 15:331 100x56 (19.20)
ignored x down scale 0:0 1920x1080 -> 15:433 100x56 (19.20)
ignored x down scale 0:0 1920x1080 -> 15:535 100x56 (19.20)
oder sogar einmal:
[ePicLoad] decode picture... /media/network/dm7080/pixmap/w10.png
EGL Error: 12301 (Invalid surface)
[ePicLoad] finished decoding /media/network/dm7080/pixmap/w10.png.
Seltsamer Weise geht eine Auflösung von Listeneintrag-Pixmap (130x100).
In quadratischen Pixmaps geht es nicht mehr.
Ich habe ein mini Referenzbeispiel mit Bild im Anhang, damit kann man das Problem einfach nachstellen.
Ich hab's nicht eingebaut. Ich hab's auf Bitten ausgebaut.
Ich baus jetzt mal so ein wie ich meine