Crash: Failed to open BO for returned DRI2 buffer #250

New Issue

2015-07-14T10:16:28+02:00

matthiasmendler commented

2015-07-14 10:16:28 +02:00

(Migrated from github.com)

Hi, I love this terminal. But since I use three monitors, I get following error. I can't really reproduce it, just have to wait, at one point the terminal crashes.

Failed to open BO for returned DRI2 buffer (3200x1800, dri2 back buffer, named 137).
This is likely a bug in the X Server that will lead to a crash soon.
Speicherzugriffsfehler (Speicherabzug geschrieben)

I found out, that this could be a driver error. But I cannot reproduce any of the other scenerios, where it'd lead to a crash. It happened to others by using mplayer/mpv in opengl mode. That never crashes for me. Nor do any opengl games.

Since it happened after connecting three screens, and I have one high resolution screen at 3200x1800, I tried to remove the screens, but it also happens with a single 1920x1080 screen:

Failed to open BO for returned DRI2 buffer (1920x1200, dri2 back buffer, named 93).
This is likely a bug in the X Server that will lead to a crash soon.
Speicherzugriffsfehler (Speicherabzug geschrieben)

From glxinfo:

OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2)

I also have a nVidia in this computer, but running cool-retro-term with optirun, it doesn't start, doesn't give any errors.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hi, I love this terminal. But since I use three monitors, I get following error. I can't really reproduce it, just have to wait, at one point the terminal crashes. ``` Failed to open BO for returned DRI2 buffer (3200x1800, dri2 back buffer, named 137). This is likely a bug in the X Server that will lead to a crash soon. Speicherzugriffsfehler (Speicherabzug geschrieben) ``` I found out, that this could be a driver error. But I cannot reproduce any of the other scenerios, where it'd lead to a crash. It happened to others by using mplayer/mpv in opengl mode. That never crashes for me. Nor do any opengl games. Since it happened after connecting three screens, and I have one high resolution screen at 3200x1800, I tried to remove the screens, but it also happens with a single 1920x1080 screen: ``` Failed to open BO for returned DRI2 buffer (1920x1200, dri2 back buffer, named 93). This is likely a bug in the X Server that will lead to a crash soon. Speicherzugriffsfehler (Speicherabzug geschrieben) ``` From glxinfo: ``` OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) ``` I also have a nVidia in this computer, but running cool-retro-term with optirun, it doesn't start, doesn't give any errors. ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/24305440-crash-failed-to-open-bo-for-returned-dri2-buffer?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>

matthiasmendler commented

2015-07-14 13:12:03 +02:00

(Migrated from github.com)

So, of course shortly after posting this, I found the culprit: the xorg driver from intel that I had from xorg edgers (Ubuntu PPA with newer drivers). After removing them it worked again. But this probably means, that coming drivers will break cool retro term...

It must have been an update within the last week, since before, it worked with those drivers.

So, of course shortly after posting this, I found the culprit: the xorg driver from intel that I had from xorg edgers (Ubuntu PPA with newer drivers). After removing them it worked again. But this probably means, that coming drivers will break cool retro term... It must have been an update within the last week, since before, it worked with those drivers.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#250