Kivy Probleme unter Win 10

Hier werden alle anderen GUI-Toolkits sowie Spezial-Toolkits wie Spiele-Engines behandelt.
Antworten
mothome
User
Beiträge: 3
Registriert: Donnerstag 20. Oktober 2016, 13:56

Freitag 8. November 2019, 09:33

Hallo zusammen,

ich habe versucht, wieder einmal etwas mit Kivy zu programmieren. Auch wenn die Ziel-Applikation unter KivyPie laufen soll, wollte ich die Entwicklungsumgebung auf meinem Notebook aufsetzen. Das läßt sich einfach besser mit auf Reisen nehmen. (Versucht doch mal einen Pi mit Akku und Touch im Flieger auszupacken :shock: :lol: )

Mein Problem ist nun, dass ich Kivy nicht zum laufen bekomme. Ich hab schon massiv Tante Google bemüht und alle gefundenen Tipp befolgt. Alle möglichen Packages installiert. Alles ohne Erfolg.
Auch mit dem dependency walker bin ich nicht weiter gekommen.

Hier mal der Kivy-Log

Code: Alles auswählen

[INFO   ] Logger: Record log in my_path\.kivy\logs\kivy_19-11-08_5.txt
[INFO   ] deps: Successfully imported "kivy_deps.gstreamer" 0.1.17
[INFO   ] deps: Successfully imported "kivy_deps.angle" 0.1.9
[INFO   ] deps: Successfully imported "kivy_deps.glew" 0.1.12
[INFO   ] deps: Successfully imported "kivy_deps.sdl2" 0.1.22
[INFO   ] Kivy: v1.11.1
[INFO   ] Kivy: Installed at "my_path\LocalCache\local-packages\Python37\site-packages\kivy\__init__.py"
[INFO   ] Python: v3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 15 2019, 01:31:54) [MSC v.1916 64 bit (AMD64)]
[INFO   ] Python: Interpreter at "my_path\python.exe"
[INFO   ] Factory: 184 symbols loaded
[DEBUG  ] Cache: register <kv.lang> with limit=None, timeout=None
[DEBUG  ] Cache: register <kv.image> with limit=None, timeout=60
[DEBUG  ] Cache: register <kv.atlas> with limit=None, timeout=None
[INFO   ] image: Running dependency walker "my_path\depends.exe" on "my_path\LocalCache\local-packages\Python37\site-packages\kivy\core\image\_img_sdl2.cp37-win_amd64.pyd" to generate troubleshooting log. Please wait for it to complete
[DEBUG  ] image: Dependency walker command is "['my_path\\depends.exe', '/c', '/od:my_path\\kivy_depends_sdl2_log_3f0jnmg0.dwi', 'my_path\LocalCache\\local-packages\\Python37\\site-packages\\kivy\\core\\image\\_img_sdl2.cp37-win_amd64.pyd']"
[INFO   ] image: dependency walker generated "my_path\kivy_depends_sdl2_log_3f0jnmg0.dwi" containing troubleshooting information about provider sdl2 and its failing file "kivy.core.image._img_sdl2 (my_path\LocalCache\local-packages\Python37\site-packages\kivy\core\image\_img_sdl2.cp37-win_amd64.pyd)". You can open the file in dependency walker to view any potential issues and troubleshoot it yourself. To share the file with the Kivy developers and request support, please contact us at our support channels https://kivy.org/doc/master/contact.html (not on github, unless it's truly a bug). Make sure to provide the generated file as well as the *complete* Kivy log being printed here. Keep in mind the generated dependency walker log file contains paths to dlls on your system used by kivy or its dependencies to help troubleshoot them, and these paths may include your name in them. Please view the log file in dependency walker before sharing to ensure you are not sharing sensitive paths
[INFO   ] Image: Providers: img_tex, img_dds, img_gif (img_sdl2, img_pil, img_ffpyplayer ignored)
[DEBUG  ] Cache: register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] Cache: register <kv.shader> with limit=1000, timeout=3600
[DEBUG  ] App: Loading kv <.\showcase.kv>
[INFO   ] window: Running dependency walker "my_path\depends.exe" on "my_path\LocalCache\local-packages\Python37\site-packages\kivy\core\window\_window_sdl2.cp37-win_amd64.pyd" to generate troubleshooting log. Please wait for it to complete
[DEBUG  ] window: Dependency walker command is "['my_path\\depends.exe', '/c', '/od:my_path\\kivy_depends_sdl2_log_tb6nlzz_.dwi', 'my_path\\local-packages\\Python37\\site-packages\\kivy\\core\\window\\_window_sdl2.cp37-win_amd64.pyd']"
[INFO   ] window: dependency walker generated "my_path\kivy_depends_sdl2_log_tb6nlzz_.dwi" containing troubleshooting information about provider sdl2 and its failing file "kivy.core.window._window_sdl2 (my_path\LocalCache\local-packages\Python37\site-packages\kivy\core\window\_window_sdl2.cp37-win_amd64.pyd)". You can open the file in dependency walker to view any potential issues and troubleshoot it yourself. To share the file with the Kivy developers and request support, please contact us at our support channels https://kivy.org/doc/master/contact.html (not on github, unless it's truly a bug). Make sure to provide the generated file as well as the *complete* Kivy log being printed here. Keep in mind the generated dependency walker log file contains paths to dlls on your system used by kivy or its dependencies to help troubleshoot them, and these paths may include your name in them. Please view the log file in dependency walker before sharing to ensure you are not sharing sensitive paths
[DEBUG  ] Window: Ignored <sdl2> (import error)
[CRITICAL] Window: Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.
  File "my_path\LocalCache\local-packages\Python37\site-packages\kivy\core\__init__.py", line 63, in core_select_lib
    fromlist=[modulename], level=0)
  File "my_path\LocalCache\local-packages\Python37\site-packages\kivy\core\window\window_sdl2.py", line 27, in <module>
    from kivy.core.window._window_sdl2 import _WindowSDL2Storage

[CRITICAL] App: Unable to get a Window, abort.
Der dependency walker lieferte einige verschiedene unaufgelößte DLLs. Alles irgendwie Windows-DLLs, die aber scheinbar nicht in Win10 vorhanden sind.
Hier mal ein Auszug:

Code: Alles auswählen

API-MS-WIN-APPMODEL-IDENTITY-L1-2-0.DLL
API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-2.DLL
API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-3.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-1.DLL
API-MS-WIN-APPMODEL-STATE-L1-2-0.DLL
API-MS-WIN-APPMODEL-UNLOCK-L1-1-0.DLL
API-MS-WIN-BASE-UTIL-L1-1-0.DLL
API-MS-WIN-CONTAINERS-CMCLIENT-L1-1-0.DLL
API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL
API-MS-WIN-CORE-APIQUERY-L1-1-1.DLL
API-MS-WIN-CORE-APPCOMPAT-L1-1-0.DLL
API-MS-WIN-CORE-APPCOMPAT-L1-1-1.DLL
API-MS-WIN-CORE-APPINIT-L1-1-0.DLL
API-MS-WIN-CORE-ATOMS-L1-1-0.DLL
API-MS-WIN-CORE-CALENDAR-L1-1-0.DLL
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-COM-L1-1-1.DLL
API-MS-WIN-CORE-COM-L1-1-2.DLL
API-MS-WIN-CORE-COM-L2-1-1.DLL
API-MS-WIN-CORE-COM-MIDLPROXYSTUB-L1-1-0.DLL
API-MS-WIN-CORE-COM-PRIVATE-L1-1-0.DLL
API-MS-WIN-CORE-COM-PRIVATE-L1-1-1.DLL
API-MS-WIN-CORE-COM-PRIVATE-L1-2-0.DLL
API-MS-WIN-CORE-COM-PRIVATE-L1-3-0.DLL
API-MS-WIN-CORE-COMM-L1-1-0.DLL
...
Alles hat aber irgendwie nix mit SDL2 aus der Fehlermaldung zu tun.

Hat irgendwer Ideen? Ich bin inzwischen am Verzweifeln.
__deets__
User
Beiträge: 6614
Registriert: Mittwoch 14. Oktober 2015, 14:29

Freitag 8. November 2019, 09:45

Da steht doch das der dependency walker eine Datei mit mehr Informationen angelegt hat. Was steht denn da drin? Oder ist das der Auszug den du postest? Wenn ja, was ist da den ALLES drin?
mothome
User
Beiträge: 3
Registriert: Donnerstag 20. Oktober 2016, 13:56

Freitag 8. November 2019, 14:29

Der Auszug ist aus der Datei. Das geht weiter mit API-MS-WIN DLLs. Alle weiteren DLLs findet er (Steht auch in dem Log-File vom dependency walker, mit Angaben zur verügbaren Version usw)
Antworten