RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1009064 - [abrt] firefox-17.0.8-1.el6_4 : xcb_glx_query_server_string_string_length : Firefox crashes after tigervnc-server-module is loaded in Xorg
Summary: [abrt] firefox-17.0.8-1.el6_4 : xcb_glx_query_server_string_string_length : F...
Keywords:
Status: CLOSED DUPLICATE of bug 1016032
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: firefox
Version: 6.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Red Hat Gecko Maintainer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1016032
TreeView+ depends on / blocked
 
Reported: 2013-09-17 15:06 UTC by Deepu K S
Modified: 2019-02-15 13:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1016032 (view as bug list)
Environment:
Last Closed: 2013-10-08 16:12:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Full Thread Backtrace (10.15 KB, text/plain)
2013-09-17 15:06 UTC, Deepu K S
no flags Details
Xorg logs (35.49 KB, text/plain)
2013-09-17 15:09 UTC, Deepu K S
no flags Details

Description Deepu K S 2013-09-17 15:06:46 UTC
Created attachment 798858 [details]
Full Thread Backtrace

Description of problem:
/usr/lib64/firefox/firefox was killed by segfault in libxcb-glx.so.0.0.0

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.4
firefox-17.0.8-1.el6_4.x86_64
tigervnc-server-module-1.1.0-5.el6_4.1.x86_64
libxcb-1.8.1-1.el6.x86_64

How reproducible:
Crash happens every time libvnc.so module is loaded in Xorg.

Steps to Reproduce:
1. Install tigervnc-server-module-1.1.0-5.el6_4.1.x86_64 package.
2. Create xorg.conf in /etc/X11/ with loading vnc extension. Below is the contents of xorg.conf file.

Section "Module"
Load "vnc"
EndSection

Section "Screen"
Identifier "Screen 1"
Option "SecurityTypes" "None"
EndSection

3. Logout from session and re-login/ Restart X
4. After Logging in, start firefox. X session crash happens and coming back to login screen.
5. If vnc module is not loaded, everything works as normal.

Actual results:
Firefox gets killed by segfault. And crashes the Xorg session. Crash happening in libxcb-glx.so.0.0.0

Expected results:
Firefox should start as normal. Xorg session should not crash.

Additional info:

The crash is happening at libxcb-1.8.1/src/glx.c +2444 in xcb_glx_query_server_string_string_length. The value passed is 0x0 for getting the string length.
Attached is the backtrace, Xorg.0.log, /var/log/messages .

Comment 1 Deepu K S 2013-09-17 15:09:14 UTC
Created attachment 798859 [details]
Xorg logs

Comment 4 Martin Stransky 2013-10-08 16:12:50 UTC

*** This bug has been marked as a duplicate of bug 1016032 ***


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