** Changed in: pyopengl (Ubuntu)
Assignee: (unassigned) => Srijan Tiwari (srijantiwari1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/289925
Title:
Segmentation fault on amd64 in glutInitDispl
glutCreateWindow segfaulted here both with the simplest possible PyOpenGL
example and also with the simplest possible example in C. This was with an
Intel 855GM with a 16-bit display on Debian Squeeze. Changing the display to
24-bit made the segfault go away.
--
You received this bug notific
This bug was fixed for the 3.0.1 release by disabling GL error-checking
on GLUT functions. This is another case of (some) newer GL
implementations being extremely anal about calls to GL entry points
before there is a GL context. Basically the glGetError() calls were
seg-faulting because GLUT didn
Exact same situation as #15 here on my EeePC 1001P. Ubuntu 9.10,
OpenGL.__version__ == '3.0.0', Python 2.6.4. I'm not currently using
Glut for my own project, but all the python examples that use it are now
broken, including the GLContext tests.
--
Segmentation fault on amd64 in glutInitDisplayM
#15 Thanks! it works !
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
For me, to fix this problem just replace libgl1-mesa-glx by libgl1-mesa-swx11
(through synaptic)
Hope this help!
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I can confirm this bug still exists with the latest version of PyOpenGL
from their bzr site:
>>> import OpenGL
>>> print OpenGL.__version__
3.0.0b6
>>>
>>> from OpenGL import GLUT
>>> GLUT.glutInitDisplayMode(GLUT.GLUT_RGBA | GLUT.GLUT_DOUBLE)
Segmentation fault
with the following backtrace
Pr
By disabling error checking as above, I do not get a seg fault error
anymore, although I do see the cryptic message
get fences failed: -1
param: 6, val: 0
About pyglet: it seems to work on my machine (MSI Wind, Pyopengl 3.0b5,
Jaunty). I mentioned it above because of an earlier post claiming it
"
I'm fine with a higher priority, but as of yet I have no
reproducibility. As a check, can someone do:
import OpenGL
OpenGL.ERROR_CHECKING = False
in one of their test scripts? That might at least tell me whether it's
really the glGetError call causing the problem or whether that just
happens to
I 100% Agree with this. pyopengl for some of the most popular distros is
completely broken. Thats a showstopper in my book.
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Let me try to recap:
1) Issue does not seem to be related with amd64 (32 bit jaunty manifests it
too).
2) Issue does not seem to be related with OpenGL library per se, since examples
in C/C++ run with no problems, although this could be due to the fact that
compiled examples do not incur in the
Pyglet is ok for my configuration (no segmentation or any other (except
sound, when it used) failures in hello_world or any other example from
source package), but the PyOpenGL lines, described above, still fail.
Ubuntu 9.04
Python 2.6.2
pyglet 1.1.3
Intel Graphics Video Card
--
Segmentation fau
Mike C. Fletcher wrote:
>We could work around it by disabling GLUT error checking entirely, but that
>seems a bit of a nuclear option, as it would >change the API. Instead I'm
>thinking we'll disable error checking *just* for the GLUT functions commonly
>called before >the GLUT context is create
Okay, on my Jaunty AMD64 I cannot replicate the problem even when I
switch to MESA software renderer (it doesn't occur with fglrx driver
either). However, looking through the tracebacks posted, it seems
pretty obvious that some configurations are failing when a call to
glGetError happens before th
It seems like we have something like the following:
* race condition where native drivers are fast enough not to crash (i.e. they
are filling out an internal structure before the call to glutInit)
* use of a GL operation by FreeGLUT that requires a GL context under MESA, but
does not under the
Thanks for the testing. I've found the upstream issue and linked it to this one:
http://sourceforge.net/support/tracker.php?aid=1737282
** Bug watch added: SourceForge.net Tracker #1737282
http://sourceforge.net/support/tracker.php?aid=1737282
** Also affects: pyopengl via
http://sourceforg
Same here. Still seg faults. i386 w/intel graphics.
2009/5/7 Juho Vepsäläinen
> I just tested the package provided by Robert. It still gives segfault.
> It gives the same backtrace as before in
> https://bugs.launchpad.net/debian/+source/pyopengl/+bug/289925/comments/12
> .
>
> I'm using Jaunty
I just tested the package provided by Robert. It still gives segfault.
It gives the same backtrace as before in
https://bugs.launchpad.net/debian/+source/pyopengl/+bug/289925/comments/12
.
I'm using Jaunty i386 with Mobility Radeon 9700 (64MB) here. Note that
it worked just fine in Hardy using fgl
Can you please test with 3.0.0 final in my PPA https://launchpad.net
/~robert-ancell/+archive/ppa. (bug 351284)
** Changed in: pyopengl (Ubuntu)
Importance: Undecided => Low
** Changed in: pyopengl (Ubuntu)
Status: Confirmed => Triaged
--
Segmentation fault on amd64 in glutInitDisplay
Yes, making the code look like this, completely resolves this
segmentation fault problem:
GLUT.glutInit(sys.argv)
GLUT.glutCreateWindow('foobar') # required to be a line before
glutInitDisplay
GLUT.glutInitDisplayMode(GLUT.GLUT_RGBA | GLUT.GLUT_DOUBLE)
(thanks to: http://
I've tried this with an internal Intel video card: it showed the window,
but it there were some artifacts and the window was unable to do
anything (close/maximize/resize) and showed Segmentation Fault when
window is closed with Alt+F4. I've clearly removed all ati fglrx
drivers, made a reboot. and
sudo apt-get install xorg-driver-fglrx
this installation is fixed the problem. So, if it is possible to make a
message about the drivers requirement while installing the module, it
will be perfect
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You
The same on i686 Ubuntu 8.10/Python2.6/PyOpenGL 3.0.0c1
but the cause seems to be another
:~$ python --version
Python 2.6.2
:~$ uname -a
Linux 2.6.27-11-generic #1 SMP Wed Apr 1 20:57:48 UTC 2009 i686
GNU/Linux
:~$ python
Python 2.6.2 (r262:71600, Apr 16 2009, 10:57:41)
[GCC 4.3.2] on linux2
I can report having this problem on my new amd64 Ubuntu Hardy
installation. However, I also have a previous Kubuntu Hardy installation
on the same machine which does not have the problem.
I assumed in my case that it was a driver problem as glxinfo screwed my
display. Having disabled the restricte
Confirm that this causing problem on CentOS as well.
>>] uname -a
Linux ... 2.6.18-92.el5 #1 SMP Tue Jun 10 18:51:06 EDT 2008 x86_64 x86_64
x86_64 GNU/Linux
>>] /sbin/lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation NV41GL [Quadro FX 1400]
(rev a2)
>>] lsb_release -rd
D
I can confirm that it doesn't work on ubuntu 8.10 but I can also confirm
that the problem disappears when the fglrx is switched on.
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
just in case you need something to look forward to: this bug still persists in
Jaunty.
I am using the Radeon driver. This did not occur with fglrx on intrepid.
here is my backtrace:
#0 0xb7c1f196 in glGetError () from /usr/lib/libGL.so.1
#1 0xb7d21057 in ffi_call_SYSV ()
from /usr/lib/python
Same problem over here.
$ uname -a
Linux poony 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics
Controller (rev 02)
$ lsb_release -rd
Description:Ubuntu 8.10
Release:
I have seen this bug on two i386 machines. Both were recently upgraded
from 8.04 to 8.10. One machine has a Radeon card, the other an Intel
on-board.
I have found that if I call glutCreateWindow() before calling
glutInitDisplayMode() the problem goes away most of the time.
Python 2.5.2 (r252:60
** Changed in: pyopengl (Debian)
Status: Unknown => New
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: pyopengl (Ubuntu)
Status: Incomplete => Confirmed
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
fwiw, I only encounter this crash on my MacBook SantaRosa, with the
Intel GMA950 graphics card. I tested it running fine on 8.10 with:
nvidia-glx-177 177.80-0ubuntu2
and
nvidia-glx-173 173.14.12-1-0ubuntu3
on a GeForce 7300go and FX5200 respectively.
All systems appear to have Direct Rendering
>>> glutInitDisplayMode (GLUT_SINGLE | GLUT_RGB)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f487693f6e0 (LWP 2645)]
0x7f48769080f0 in ?? ()
(gdb) bt
#0 0x7f48769080f0 in ?? ()
#1 0x7f4875064aec in ffi_call_unix64 ()
from /usr/lib/python2.5/lib-dyn
Hi,
Can you please run python from gdb:
gdb python
run
and then introduce the python commands.
when segfault happen, run backtrace, and post the result here.
Thanks.
** Changed in: pyopengl (Ubuntu)
Status: New => Incomplete
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://
** Changed in: pyopengl (Ubuntu)
Status: Incomplete => New
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Debian Bug tracker #480657
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480657
** Also affects: pyopengl (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480657
Importance: Unknown
Status: Unknown
--
Segmentation fault on amd64 in glutInitDisp
I'm encountering the same crash on Intrepid i386.
[EMAIL PROTECTED] ~/Downloads (2432)]: dpkg -l python-opengl
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: u
Can you test with the Intrepid version? This is version 3.0.0~b3.
I've been able to run successfully your example, without segfault, on an amd64:
[EMAIL PROTECTED]:~/temp/PyOpenGL-Demo-3.0.0b6/PyOpenGL-Demo$ python
Python 2.5.2 (r252:60911, Oct 5 2008, 19:29:17)
[GCC 4.3.2] on linux2
Type "help"
38 matches
Mail list logo
