Bug 101647 - couldn't find RGB GLX visual or fbconfig
Summary: couldn't find RGB GLX visual or fbconfig
Status: RESOLVED MOVED
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.11 (xserver-1.18.4)
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-29 13:09 UTC by Abbott WANG
Modified: 2019-05-23 18:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Blank screen, nothing shows up. (228.63 KB, image/png)
2017-06-29 13:09 UTC, Abbott WANG
Details

Description Abbott WANG 2017-06-29 13:09:38 UTC
Created attachment 132342 [details]
Blank screen, nothing shows up.

MacOS, 10.12.5 (16F73)
XQuartz 2.7.11 (xorg-server 1.18.4)

On localhost, glxgears, glxinfo, xclock work fine. 

Then open iTerm, 
ssh -X -Y to my desktop which runs with Ubuntu Linux, 

xclock&  works, 


[abbott@labcmc ~]$ glxinfo
name of display: localhost:11.0
Error: couldn't find RGB GLX visual or fbconfig
# fails 

[abbott@labcmc ~]$ glxgears
Error: couldn't get an RGB, Double-buffered visual
#fails
gv &
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
gview.exe: xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
# gview.exe is another X11 application I am using. 


I have attached a pic about the bugs. 
Normally, there are atoms showing up in the window, but now, nothing.
Comment 1 GitLab Migration User 2019-05-23 18:32:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/789.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.