Lars Wirzenius wrote:

well, it *might* work smoothly indeed, but the fact is that I'm accessing a Sarge sys via a vnc session at 8bit, and all I got is:

2005-02-26 06:59:40.000 GWorkspace[31699] NOTE: Only one display per host fully 
supported.
2005-02-26 06:59:40.000 GWorkspace[31699] WARNING - XGServer is unable to use 
the fast algorithm for writing to an 8-bit display on this host - the most 
likely reason being the StandardColormap RGB_BEST_MAP has not been installed.
2005-02-26 06:59:40.000 GWorkspace[31699] Unrecognized color masks: 
00000007:00000038:000000c0 8
2005-02-26 06:59:40.000 GWorkspace[31699] Please report this along with details 
on your pixel format (ie. the four numbers above). (Or better yet, implement it 
and send me a patch.)

which leaves me with no other choice but use anoter filemanager, hence the
severity.



I suspect this is a bug in gnustep-back and not in gworkspace itself.
Please, could test with another GNUstep apps (via vnc too) ?



I tried it with an 8-bit X server running under qemu. The results were pretty much identical: neither GWorkspace nor Mines (the two GNUstep programs I tried) would run. When I configured it to be a 24-bit screen, Mines would run without problems.

If I understand correctly, this means all or many GNUstep program don't
work at all with an 8-bit display. Personally, I don't think this is a release critical problem, and possibly not even a bug, even though it is obviously quite annoying if that's the only thing you've got. Thus, I
would think the best way would be to assign this bug to the appropriate
GNUstep base package and lowering its severity to normal.




   Hi Lars,

Could try to run these commands ( not sure if you need to do that as user or as root ) on the machine where gworkspace is installed:

. /usr/lib/GNUstep/System/Library/Makefiles/GNUstep.sh (there is space between . an / at the beginning)
defaults write NSGlobalDomain XWindowBufferUseXShm no


   Eric


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to