RE: vsw4 problems in lsbsi

"Wichmann, Mats D" <[email protected]>
Newsgroups gmane.linux.lsb.test-suite
Message-ID <A06801158AE07847B27A52C1A074BC1D07FB0633@fmsmsx404.amr.corp.intel.com>
Actually, this one looks identical to one Thorsten posted on June 7 for
"Running on SLES9SP2 (XFree86, heavy patched)". The condsiderable
difference in X software versions between these two suggests to me this
might be a setup thing, indeed.


	I am running into a few problems that seem to be unique to the
lsbsi. They all seem to be related to a problem with the font path
within the lsbsi for Xvfb. Here are the errors I am seeing along with
the excerpt from the journal. 
	
	1. /tset/CH02/clsdsply/Test 19 UNRESOLVED 
	
	400|7 19 1 09:26:25|IC Start 
	200|7 19 09:26:25|TP Start 
	520|7 19 00018589 1 1|CHECK:XCloseDisplay-19  1, line 1462 
	520|7 19 00018589 1 2|CHECK:XCloseDisplay-19  2, line 1469 
	520|7 19 00018589 1 3|REPORT:Unexpected error BadValue 
	520|7 19 00018589 1 4|REPORT:BadValue (integer parameter out of
range for operat 
	ion) 
	520|7 19 00018589 1 5|REPORT:Protocol request was X_SetFontPath 
	520|7 19 00018589 1 6|REPORT:Unexpected Xlib error 
	520|7 19 00018589 1 7|CHECK:XCloseDisplay-19  3, line 1477 
	520|7 19 00018589 1 8|CHECK:XCloseDisplay-19  4, line 1484 
	520|7 19 00018589 1 9|CHECK:XCloseDisplay-19  5, line 1490 
	520|7 19 00018589 1 10|CHECK:XCloseDisplay-19  6, line 1503 
	520|7 19 00018589 1 11|CHECK:XCloseDisplay-19  7, line 1503 
	520|7 19 00018589 1 12|CHECK:XCloseDisplay-19  8, line 1519 
	520|7 19 00018589 1 13|CHECK:XCloseDisplay-19  9, line 1531 
	520|7 19 00018589 1 14|CHECK:XCloseDisplay-19  10, line 1537 
	220|7 19 2 09:26:27|UNRESOLVED 
	410|7 19 1 09:26:27|IC End 
	
	2. /tset/CH06/stfntpth/Test 1 FAIL 
	
	200|241 1 09:34:47|TP Start 
	520|241 1 00018829 1 1|TRACE:Received error type BadValue 
	520|241 1 00018829 1 2|REPORT:Got BadValue, Expecting Success 
	520|241 1 00018829 1 3|CHECK:XSetFontPath-1  1, line 179 
	520|241 1 00018829 1 4|REPORT:Font path component did not match
what was set 
	520|241 1 00018829 1 5|REPORT:  was
'/usr/X11R6/lib/X11/fonts/misc/', expecting 
	'/usr/lib/X11/fonts/100dpi/' 
	520|241 1 00018829 1 6|REPORT:Font path component did not match
what was set 
	520|241 1 00018829 1 7|REPORT:  was
'/opt/lsb/test/vsw4/xtest/fonts', expecting 
	'/usr/lib/X11/fonts/75dpi/' 
	220|241 1 1 09:34:47|FAIL 
	410|241 1 1 09:34:47|IC End 
	
	3. /tset/CH06/stfntpth/Test 2 FAIL 
	
	400|241 2 1 09:34:47|IC Start 
	200|241 2 09:34:47|TP Start 
	520|241 2 00018829 1 1|TRACE:Received error type BadValue 
	520|241 2 00018829 1 2|REPORT:Got BadValue, Expecting Success 
	520|241 2 00018829 1 3|CHECK:XSetFontPath-2  1, line 265 
	520|241 2 00018829 1 4|REPORT:Font path component did not match
what was set 
	520|241 2 00018829 1 5|REPORT:  was
'/usr/X11R6/lib/X11/fonts/misc/', expecting 
	'/usr/lib/X11/fonts/100dpi/' 
	520|241 2 00018829 1 6|REPORT:Font path component did not match
what was set 
	520|241 2 00018829 1 7|REPORT:  was
'/opt/lsb/test/vsw4/xtest/fonts', expecting 
	'/usr/lib/X11/fonts/75dpi/' 
	220|241 2 1 09:34:47|FAIL 
	410|241 2 1 09:34:47|IC End 
	
	It looks like the last two problems are related to 100dpi and
75dpi fonts not being in the font path. Am I not setting some variable
correctly or is this just a problem due to the way the lsbsi is built?
Since the lsbsi is a minimally conforming system, it has very little
font info on it. Mainly it just has the /usr/X11R6/lib/X11/fonts/misc
directory copied from the host system. Are there more directories needed
or maybe some extra configuration steps to get this working correctly in
the lsbsi? Any help on this would be appreciated. 
	
	Regards,
	
	Marvin Heffler
	Linux Standard Base
	IBM Linux Technology Center
	11501 Burnet Road, Zip 905-7A017
	Austin, TX 78758
	(512) 838-0953    T/L 678-0953

_______________________________________________
lsb-test mailing list
[email protected]
http://mail.freestandards.org/mailman/listinfo/lsb-test
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.