-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttributeError: 'DisplayOpenGL' object has no attribute 'context' #255
Comments
Hi, is the problem related to this discussion #195 i.e. needing to setup the driver to work with bullseye? |
I guess, you should try this: |
Yesterday I tried to do a clean build on Pi3B with Buster using the instructions at TheDigitalPictureFrame. I am getting similar messages as reported here and elsewhere. The OS is 2021-05-07-raspios-buster-arm64 cat /etc/os-release Here is the output from the picframe install:sudo python3 -m pip install -U pip picframe -i . The messages are different depending on if executing pic frame from a remote ssh or from a native terminal window on the pi.From ssh From Native Terminal |
On a whim I tried Helgeerbe's 3B/Bullseye configuration from issue 195 with my Buster install (per the 3B installation instructions). In other words I just ran raspi-config to change to full KMS and changed use_glx to True. This solved the startup problems from a native terminal window and the images cycle as expected. But: enabling a mouse for input does not work, picframe 'hangs' when starting. Note - this is a Logitech wireless mouse (I no longer have any wired mice😉) However, enabling a keyboard does work If I start picframe from a remote ssh window with input_type: mouse I get the following: |
My working config for a fresh install of PicFrame 2024.5.31 on a 3B using Wolfgang's instructions required two things. First was using full KMS in raspi-config per issue 195, while use_glx in the yaml file stayed false. This allowed picframe to start without error from a Pi desktop terminal session. To run from a remote terminal I must set use_glx True. This does not seem to affect execution from the Pi desktop terminal. The second thing fixed the mouse peripheral issue. the file 'pointer.png' was somehow missing from the pi3d icons folder located at ~/.local/lib/python3.7/site-packages/pi3d/util/icons. I found this file at the pi3d GitHub site and copied it to my pi. Now picframe starts without error and the mouse works. Performance seems significantly slower so following suggestions in issue #100 I adjusted fps and got a reasonable level of performance back. It seems like something under the hood has changed and affected performance on the Pi3B. |
If you like, you can try the Bookworm way: https://www.thedigitalpictureframe.com/how-to-build-the-best-raspberry-pi-digital-picture-frame-with-bookworm-and-pi3d-picframe-2024-edition/ |
I hadn’t realized there was a better starting point now with bookworm, Thanks for pointing this out. Itt works pretty well. I had to use sudo when I issued the journalctl command to vacuum the logs. That may be because I built the system with my name as user instead of ‘pi’ but it all worked.
The pointer.png file is still missing in the icons folder so picframe hangs when you start it with the mouse enabled. I managed to copy pointer.png to the correct place and the mouse works but I did notice that all the icons that used to be png files are now gif files. In any event it still enabled the mouse and use of the menus.
Would all of this still work with the full desktop version of Bookworm?
Many thanks,
Dan
… On Jun 5, 2024, at 1:53 PM, Wolfgang Männel ***@***.***> wrote:
If you like, you can try the Bookworm way: https://www.thedigitalpictureframe.com/how-to-build-the-best-raspberry-pi-digital-picture-frame-with-bookworm-and-pi3d-picframe-2024-edition/
—
Reply to this email directly, view it on GitHub <#255 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6TDYVRPT4GWK4ZSGF4TALZF5NC5AVCNFSM5RME5PAKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJVGA3TIMRRGU3A>.
You are receiving this because you commented.
|
I have setup pic frame on a fresh raspberry pi4, with an Display on the HDMI Port:
First launch from the Terminal gets me the following Errors:
What's going wrong here?
best regards
The text was updated successfully, but these errors were encountered: