Bug 585605 - [abrt] crash in glx-utils-7.7-4.fc12: Process /usr/bin/glxgears was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in glx-utils-7.7-4.fc12: Process /usr/bin/glxgears was killed by...
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:54d633f9d770024799751c5785c...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-25 01:40 UTC by RedHat-User
Modified: 2010-08-04 03:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-08-04 03:00:13 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (7.79 KB, text/plain)
2010-04-25 01:40 UTC, RedHat-User
no flags Details

Description RedHat-User 2010-04-25 01:40:00 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: glxgears
component: mesa
executable: /usr/bin/glxgears
global_uuid: 54d633f9d770024799751c5785c895b3d6b20619
package: glx-utils-7.7-4.fc12
rating: 4
reason: Process /usr/bin/glxgears was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

I have an x86_64 CentOS 5 machine running VirtualBox 3.16.  The machine has an ATI Radeon HD 2600XT and I use the proprietary drivers.  Glxgears works fine on it (the host).

I have Fedora 12 (x86_64) installed as a VirturalBox guest.  The VirtualBox guest additions are installed, which should provide 3D acceleration support.  When I execute glxgears in the Fedora 12 guest, it crashes.

How to reproduce
1.  Execute the glxgears command from a konsole.

Comment 1 RedHat-User 2010-04-25 01:40:02 UTC
Created attachment 408906 [details]
File: backtrace

Comment 2 Owen Taylor 2010-07-14 16:44:42 UTC
vboxvideo bug, not Mesa bug

Same as bug 603569, http://www.virtualbox.org/ticket/7061

Comment 3 RedHat-User 2010-08-04 03:00:13 UTC
Closing this ticket since this appears to be an issue with VirtualBox instead of Fedora.  In  Noel Duffy's VirtualBox bug ticket, <http://www.virtualbox.org/ticket/7061>, the user "galalleni" wrote, "Same issue here. It appears that the system is using Mesa's libGL (which is v7.8) instead of the libGL Vbox uses (v7.2) - that's why this error is occurring."

I'm going to look over there to see if there is a way to make VirtualBox use the same Mesa libGL.

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