FBO Initialization failed: Incomplete attachment

[Frank Gould]

I am trying to find a solution to the problem reported in the subject of this post.  I am using KivyPie image to test a simple app that I've attached.  When this error message appears, the image does not appear on the screen but is blank or black screen.  The two Slide jpg files attached are what I use to test.  There are also glGetError 0x502 that appear in the console messages and would like to get those resolved as well.  I have had similar results running this app on the NOOBS distribution.  I appreciate any suggestions.

[Cristóbal Contreras Rubio]

Normally KivyPie does not have folder /home/pi, it has /home/sysop.
Check if your images are in /home/sysop/.masterpics/pix instead of /home/pi/.masterpics/pix

[Frank Gould]

Thank you Cristobal for your response. Yes, the copy I attached was local and not on the test RPi that had been updated with the correct folder. Pictures from the folder you suggested did display on the screen EXCEPT when the subject line error messages appear.

[Cristóbal Contreras Rubio]

I get lost in your code, could you attach the trace of the entire error?

[Frank Gould]

My apologies for any confusion. I copied that code off the web and tailored it for my test.  I've attached a new version that pulls pictures from the /home/sysop/pix folder and removed the Temp label feature.  If you will create that pix folder and put the two jpg files I originally attached to this post, you should be able to run this attached version of screenmanager.py.

I have also included the log from this app execution called KivyPie-screenmanagertest-log.txt.  Scroll down and you'll find the glGetError 0x505 after many glGetError 0x502 errors.  If I use my regular slideshow pictures that are not so simple, the app eventually locks up after many glGetError 0x505 errors, most likely because the GPU runs out of memory.  I have to power cycle reboot to get the app to run again.

Thank you for your patience with this issue and any suggestions are greatly appreciated.

[Cristóbal Contreras Rubio]

The problem is with OpenGL, you've got this error

glGetError 0x502

I've googled this and I've founded this open issue of Kivy, maybe the solution is you should increase the gpu memory of Raspberry Pi.
I would recommend:
- Use Python 3 (best performance, less security errors, ...)
- Simplify the ScreenManager
kv = """
<KivySlideshow>:
    id: scrmgr
    size_hint: 1,1

<PhotoScreen>:
    Image:
        source: root.imsource
""
...
class PhotoScreen(Screen):
    manager = scrmgr
...
class KivySlideshow(ScreenManager):
...

[Cristóbal Contreras Rubio]

Ahh, I almost forget to recommend you that your solution is maybe not "optimal".
In your case, I will load all screens/photos once in the screenmanager, and then, for the transition, you should use a Kivy Clock Trigger

[Frank Gould]

I’m not asking for a code review or work around solution.  This test app and my product app run on Windows and Android with no FBO Initialization failures.  Someone needs to fix this Kivy bug that is only happening on Raspberry Pi.  I have also tested it in VM Mint Linux and it does not fail or exhibit the same glGetErrors.

I’m also trying to build a QEMU on Windows that will allow me to share this with other developers who do not have a RPi.

Please let me know if you can help get this bug fixed.

--
You received this message because you are subscribed to a topic in the Google Groups "KivyPie" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kivypie/OcnffiUSD1M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kivypie+u...@googlegroups.com.
To post to this group, send email to kiv...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kivypie/a73cbcb7-b0c2-4820-8a6c-f145892089a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.