Xephyr / Xorg enabling backing store feature

Question

Hi,
i used SunRay kiosk mode extention from
http://blogs.sun.com/danielc/entry/meta_kiosk_how_to_run
successful. I want to display a X11 application to dtu(s) using meta kiosk. The meta kiosk script uses Xephyr to display X11 application to dedicated dtu.
Please see meta kiosk session script:
# The next set are not true kiosks in the typical sense and cannot or do not
# conform to the standard use of variables.
run-X11-session () {
DISPLAYNUM=0
if [ -x /usr/X11/bin/Xephyr ]
then
# We are on Solaris X86, Xephyr should be vailable
while [ $DISPLAYNUM -ne 256 ]
do
DISPLAYNUM=`expr $DISPLAYNUM + 1`
--->>> /usr/X11/bin/Xephyr :$DISPLAYNUM -once -query $1 -fullscreen
if [ $? -ne 1 ]
then
exit
fi
done
else
# We are on SPARC/Xnest should be available
#You may have to execute this on your host...
#chmod 04755 /usr/openwin/bin/Xnest
SCREENGEOMETRY=`/opt/SUNWut/bin/utset | grep "Display Timing 1" | cut -f2 -d":" | cut -f1 -d@`
while [ $DISPLAYNUM -ne 256 ]
do
DISPLAYNUM=`expr $DISPLAYNUM + 1`
/usr/openwin/bin/Xnest -once -geometry $SCREENGEOMETRY -query $1 :$DISPLAYNUM
if [ $? -ne 0 ]
then
exit
fi
done
fi
exit
The X11 application that should be displayed uses "backing store" feature. I tried to activate "backing store" with "+bs" option. I modifed the script:
while [ $DISPLAYNUM -ne 256 ]
do
DISPLAYNUM=`expr $DISPLAYNUM + 1`
--->>> /usr/X11/bin/Xephyr :$DISPLAYNUM +bs -once -query $1 -fullscreen
if [ $? -ne 1 ]
then
exit
fi
done
In a second attempt i used "-wm" option, but the modification was not succesful again. So some X11 application windows are not filled with graphical information.
Xephyr is part of the Xorg software.
The Xorg packages used in Solaris 10 update 5 have version 1.3.0. Last available version is 1.6.0. Nevada build 106 uses 1.5.3 Xorg version. Perhaps I want to try this version to get rid of this error.
Thanks for your help !
Christian

Answer 1

skottish wrote:
Welcome to the forums.
Please don't post general issues in this sub-forum. Moving...
Oops, my bad.
As for my issue(s), I'm not going to bother with the proprietary driver until AMD gets their act together.