Bug 9181

Summary:	The default visual and visual list of Xvfb in 7.2 has changed from what it was in 7.1
Product:	xorg	Reporter:	Deron Johnson <deron.johnson>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED FIXED	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	highest	CC:	astrand
Version:	7.2 (2007.02)
Hardware:	x86 (IA32)
OS:	Solaris
Whiteboard:
i915 platform:		i915 features:

Description Deron Johnson 2006-11-27 15:57:07 UTC

When I start Xvfb with a 24-bit depth, the visuals are different than what  you
get with Xvfb 7.1.
In addition, whereas Xvfb 7.1 has a TrueColor default visual, Xvfb 7.2 (in the
server-1.2-branch)
has a DirectColor default visual. This causes problems for Looking Glass. Was
this change
intentional or is it a bug? The reason why this is occuring is because the
symbol XFree86Server is not defined
while compiling fbcmap.c (this symbol is defined during the server compile in
7.1 but not in 7.2).

Comment 1 Daniel Stone 2007-02-27 01:34:52 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 2 Jesse Adkins 2010-11-20 11:43:21 UTC

(In reply to comment #0)
> When I start Xvfb with a 24-bit depth, the visuals are different than what  you
> get with Xvfb 7.1.
> In addition, whereas Xvfb 7.1 has a TrueColor default visual, Xvfb 7.2 (in the
> server-1.2-branch)
> has a DirectColor default visual. This causes problems for Looking Glass. Was
> this change
> intentional or is it a bug?
Wouldn't this be a bug in Looking Glass not being able to set the visual it wants or rejecting unusable ones?

> The reason why this is occuring is because the
> symbol XFree86Server is not defined
> while compiling fbcmap.c (this symbol is defined during the server compile in
> 7.1 but not in 7.2).

fbcmap.c hasn't been included in the build in a while. Even if it was, I killed it when I fixed #5436 ten days ago.

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.