1

I'm developing an application using Python 3 / PyQt5. Everything seems ship-shape until I try to run the GUI (which is partially reliant on a live graph that is backed by pyqtgraph) on my Raspberry Pi 2 Model B (Raspbian Jessie), when it throws the error libEGL warning: DRI2: failed to authenticate. This question has a potential fix, but it's very long and might not be exactly what I need, so I don't want to embark on that reconfig journey unless I absolutely have to. I'm trying to make this software easy to configure on a fresh installation.

Exactly what happens: I execute my application from the terminal (python3 app.py) on the Pi. The application does start, but throws the aforementioned libEGL warning. My application consists of a starting window that has buttons to open the functional portions of my application. This starts fine, but when I try to open my "control panel" with a live plot in it, this new window stops responding. There is no Python error traceback.

Any ideas?

bearoplane
  • 131
  • 1
  • 1
  • 6

2 Answers2

1

As far as I know now, these issues are unrelated. After some serious debugging of code I was reusing for the data acquisition, I noticed that there were some problems with process spawning that was causing the program to hang in the new implementation. I'm taking two separate scripts and trying to integrate them into a well-formatted, well-coded application, so I assume the problems were introduced when I tried to interface the old with the new.

Lesson learned: write better tests. If this pops back up as a real problem, I'll be sure to put it here.

bearoplane
  • 131
  • 1
  • 1
  • 6
0

driconf (cute little configuration utility) on a Raspberry Pi 3B tells me

Screen "0" is not direct rendering capable.

Alan Corey
  • 201
  • 1
  • 6