Bug is back on 10.10, the test case in the first post leads to a
segfault.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/318043
Title:
glGetError causes a segmentation fault
Bug seems to be gone in Lucid Lynx.
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
___
Mailing list:
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
** Tags added: intrepid
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
___
Mailing list:
but the latest stable mesa 3d version does.
Specifically which version are you referring to here?
Can you please test whether this problem is solved in the version of mesa
included in xorg-edgers?
https://edge.launchpad.net/~xorg-edgers/+archive/ppa
** Changed in: mesa (Ubuntu)
The Packages I referred to did not have dri acceleration, so this is
still a bug. The Karmic version still does not work, but the latest
stable mesa 3d version does.
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you
After considering this a little more, aren't all calls to opengl not
valid until a context is made current?
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
1) Without a context, calls should just return an error, not segfault. (And
glGetError should be used to get the type of the error...)
2) glGetError crashes the same way if used with a valid context. It would just
make the test case longer.
--
glGetError causes a segmentation fault
Hmmm, mine doesn't crash with a valid context set as current, do you
want to give an example?
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
Alright I took a hint from Dima and tried the hardy libGL.so.1. It
worked perfectly. Then i tried the other versions. I tried the jaunty,
jaunty, and karmic, ALL OF THEM WORKED! I'm not really sure what that
means but it fixed the problem for me. I got them from here
Yeap running ubuntu jaunty
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/27287278/lspci_vvnn
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/27287289/Xorg.0.log
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
** Changed in: mesa (Ubuntu)
Status: Incomplete = New
--
glGetError causes a segmentation fault
https://bugs.launchpad.net/bugs/318043
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
13 matches
Mail list logo
