Rainer Dorsch schrieb:
Am Montag, 3. September 2007 12:19 schrieb Stephan Witt:
Rainer Dorsch schrieb:
Am Freitag, 31. August 2007 19:50 schrieb Pavel Sanda:
I run lyx remove on the SLES9 machine and connect from a Debian etch
machine with SSH.
ssh -X or ssh -Y ?
I have also lyx 1.4.3 on the SLES9 machine, this one runs in the same
session flawless.
lyx 1.4.3 is linked against QT3.
Do you know which X setting is affected and how I could check that (or
a term to google for)?
i would search for Depth in your xorg.conf.
Hmmm...I do not yet understand the concept.
On the SLES which runs LyX, there is no XServer. Thus there is no color
depth on the machine which runs LyX.
On the client, which is a Debian etch machine and which runs the XServer,
I get
Section "Screen"
Identifier "Screen0"
Device "Card0"
# Device "radeon driver"
Monitor "Monitor0"
DefaultDepth 24
i.e. a color depth of 24. That seems to be reasonable, any locally
compiled version of LyX does not show and bad colors.
Do I have to tell LyX on the SLES machine that the XServer it is
displayed on the etch machine supports 24 bits color depth? How would I
do that?
No, you don't have to tell LyX about that. The Xlib code is aware of the
properties of the Xservers (Screen) it is connected to.
You may check that with the following command:
% ssh -XC [EMAIL PROTECTED] xdpyinfo
or
% ssh -XC [EMAIL PROTECTED] /usr/X11/bin/xdpyinfo
The output tells you about the default visual and it's depth.
But I would guess that's not the problem.
I am not an expert reading these data, I did not see something suspicious, do
you?
No, it's all well, the X-server (your client machine) and the
Xconnection is able to display true color (24 bit depth). Your problem
is not the X-server.
See the comments in your output below.
It is IMHO a Qt-ABI-incompatibility. Maybe, you can "force" your lyx
binary which is compiled and linked against Qt 4.2.1 to use the correct
(?) shared library at runtime?
I suspect something is fishy with your libQtCore.so.4 =>
/afs/bb/data/d3197/galaxy2/zLinux/qt-4.2.1//lib/libQtCore.so.4
line in ldd output...
Are you sure it is compatible with libQtGui.so.4 =>
/afs/qt-4.2.1/lib/libQtGui.so.4 ?
Stephan
$ ssh -XC [EMAIL PROTECTED] xdpyinfo #user and sles-machine replaced
name of display: localhost:43.0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 70101000
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0x3000005, revert to PointerRoot
number of extensions: 32
ATIFGLEXTENSION
ATIFGLRXDRI
ATITVOUT
BIG-REQUESTS
DAMAGE
DOUBLE-BUFFER
DPMS
Extended-Visual-Information
GLX
MIT-SCREEN-SAVER
MIT-SHM
MIT-SUNDRY-NONSTANDARD
RANDR
RENDER
SECURITY
SGI-GLX
SHAPE
SYNC
TOG-CUP
X-Resource
XC-APPGROUP
XC-MISC
XFIXES
XFree86-Bigfont
XFree86-DRI
XFree86-Misc
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number: 0
That's the screen LyX should use: screen #0
number of screens: 1
screen #0:
dimensions: 1600x1200 pixels (410x310 millimeters)
resolution: 99x98 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x3d
depth of root window: 24 planes
number of colormaps: minimum 1, maximum 1
default colormap: 0x20
default number of colormap cells: 256
preallocated pixels: black 0, white 16777215
options: backing-store NO, save-unders NO
largest cursor: 64x64
current input event mask: 0xfa4031
KeyPressMask EnterWindowMask LeaveWindowMask
KeymapStateMask StructureNotifyMask SubstructureNotifyMask
SubstructureRedirectMask FocusChangeMask PropertyChangeMask
ColormapChangeMask
number of visuals: 8
default visual id: 0x23
That's the visual LyX is using: 0x23
And this visual has true color capabilities.
The LyX application may request the display of every pixmap up to 2^24
different colors.
visual:
visual id: 0x23
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x24
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x25
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x26
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x27
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x28
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x29
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x2a
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
