Bug 445004 - Segmentation fault in glutInitDisplayMode
Segmentation fault in glutInitDisplayMode
Product: Fedora
Classification: Fedora
Component: PyOpenGL (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Nikolay Vladimirov
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-02 14:01 EDT by Michael Krauss
Modified: 2008-07-26 17:21 EDT (History)
0 users

See Also:
Fixed In Version: 3.0.0-0.6.b4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-26 17:21:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Krauss 2008-05-02 14:01:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5

Description of problem:
When starting a program using glutInitDisplayMode(), no matter what parameters passed, it results in a segmentation fault. This program for example:
or the test_glutinit.py program from the original pyopengl upstream package.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. try to start one of the mentioned programs.

Actual Results:
segmentation fault. No error messages bedside that.

Expected Results:
A beautiful OpenGl rendered window should appear.

Additional info:
Comment 1 Bug Zapper 2008-05-14 06:32:23 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 2 Nikolay Vladimirov 2008-07-18 06:51:21 EDT
I'm not able to reprodce this. 
A new version of PyOpenGl will hit tomorrow's rawhide try with that. Also it
will be in F-9 updates-testing in a few days. 
So, please try the new version and report if the problem is still present or not. 
Comment 3 Nikolay Vladimirov 2008-07-26 17:21:39 EDT

No reply from the reporter. I'm closing this if the problem is still present,
please reopen the bug. 

Note You need to log in before you can comment on or make changes to this bug.