Bug#270976: xlibs: doesn't understand IRIX xinerama X servers

2004-12-21 Thread Matt Reynolds
Thought I should point out that SGI have logged a bug against their 
Xinerama X server and fixed this incompatibility with 6.5.27 onwards.


Basically Xsgi with xinerama enabled is telling the client that it has a 
single screen (logically enough), and then proceeding to pass xscreen 
dimensions for the two (or more) physical screens that make up the 
logical screen. Hence the overflow of bytes. It's only since Xfree 
started checking for unused bytes in this setup message that the problem 
was noticed.


Apologies for pushing this out as a debian/xfree problem when it was 
really ours... :(


As a more general comment, Xsgi's xinerama extension complies to a 
different version of Xorg's standard than the one that most vendors have 
implemented. It's a bit of a minefield. I've noticed many gnu/linux 
packages that don't quite work right with Xsgi.. *sigh*


Feel free to close this one down.



Bug#270976: xlibs: doesn't understand IRIX xinerama X servers

2004-10-15 Thread Branden Robinson
On Tue, Oct 12, 2004 at 08:14:20PM +0100, Matt Reynolds wrote:
> Oh yeah, there's a lot more stuff in the xpdyinfo output (well only from
> the IRIX side - the debian client can't complete the setup stages of the
> connection, so it doesn't output anything more than I showed). I
> didn't want to flood the bug report straight away with the full output,
> the IRIX X server has a LOT of visual IDs. I've enclosed the output.

Thanks!

> I can attempt to collect a snoop trace of the debian client talking to the
> X server tomorrow if it'll help.

Sure, that would be great.

> The weirdest thing about all this? I can't find that line in the source
> code of the xlibs package, yet "strings libX11.so | grep parse" returns
> the exact string..!

xlibs doesn't contain any shared libraries anymore -- please see its
package description.

What you want is libx11-6.

$ grep -3n 'Did not parse entire' xc/lib/X11/*.c
xc/lib/X11/OpenDis.c-567-
xc/lib/X11/OpenDis.c-568-   if(usedbytes != setuplength){
xc/lib/X11/OpenDis.c-569-   /* Sanity check, shouldn't happen. */
xc/lib/X11/OpenDis.c:570:   fprintf(stderr, "Xlib: Did not parse entire 
setup message: "
xc/lib/X11/OpenDis.c-571-   "parsed: %ld, message: 
%ld\n",
xc/lib/X11/OpenDis.c-572-   usedbytes, setuplength);
xc/lib/X11/OpenDis.c-573-   OutOfMemory(dpy, setup);

-- 
G. Branden Robinson|My first priority in any attack is
Debian GNU/Linux   |to solve the problem -- not issue a
[EMAIL PROTECTED] |press release.
http://people.debian.org/~branden/ |-- Steve McInerney


signature.asc
Description: Digital signature


Bug#270976: xlibs: doesn't understand IRIX xinerama X servers

2004-10-12 Thread Matt Reynolds
Hi,

On Tue, 12 Oct 2004, Branden Robinson wrote:

> retitle 270976 libx11-6: doesn't understand setup messages from 
> XINERAMA-enabled IRIX X servers
> reassign 270976 libx11-6
> tag 270976 + upstream moreinfo
> thanks
>
> On Fri, Sep 10, 2004 at 11:46:03AM +0100, Matt Reynolds wrote:
> > Package: xlibs
> > Version: 4.3.0.dfsg.1-7
>
> I am sorry it has taken a while for us to reply to your bug report.
>
> When you run xdpyinfo as above, is that really all the information you get
> back?  There should be much more.
>
> I am wondering what extension name is advertised by the IRIX X server when
> XINERAMA is enabled, and xdpyinfo should tell us.
>

Oh yeah, there's a lot more stuff in the xpdyinfo output (well only from
the IRIX side - the debian client can't complete the setup stages of the
connection, so it doesn't output anything more than I showed). I
didn't want to flood the bug report straight away with the full output,
the IRIX X server has a LOT of visual IDs. I've enclosed the output.

I can attempt to collect a snoop trace of the debian client talking to the
X server tomorrow if it'll help. The weirdest thing about all this? I
can't find that line in the source code of the xlibs package, yet "strings
libX11.so | grep parse" returns the exact string..!

Matt.name of display::0.0
version number:11.0
vendor string:Silicon Graphics
vendor release number:6600
maximum request size:  262140 bytes
motion buffer size:  0
bitmap unit, bit order, padding:32, MSBFirst, 32
image byte order:MSBFirst
number of supported pixmap formats:6
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 12, bits_per_pixel 16, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
keycode range:minimum 15, maximum 149
focus:  window 0x4400027, revert to Parent
number of extensions:32
DCShare
DEC-XTRAP
DOUBLE-BUFFER
DPMS
ESA
Extended-Visual-Information
GLX
LBX
MIT-SHM
MIT-SUNDRY-NONSTANDARD
Multi-Buffering
READDISPLAY
RECORD
ReadDisplay
SCREEN-SAVER
SGI-CONTROLPASSING
SGI-NewMultibuffering
SGI-SCREEN-CAPTURE
SGI-SUNDRY-NONSTANDARD
SGI-VIDEO-CONTROL
SGI-XINERAMA
SGIFullScreenStereo
SHAPE
SYNC
TOG-CUP
XC-APPGROUP
XC-MISC
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number:0
number of screens:1

screen #0:
  dimensions:2560x1024 pixels (728x291 millimeters)
  resolution:89x89 dots per inch
  depths (5):1, 8, 12, 15, 24
  root window id:0x4e
  depth of root window:24 planes
  number of colormaps:minimum 1, maximum 23
  default colormap:0x20
  default number of colormap cells:256
  preallocated pixels:black 0, white 16777215
  options:backing-store YES, save-unders YES
  largest cursor:32x32
  current input event mask:0x5a20bd
KeyPressMask ButtonPressMask  ButtonReleaseMask
EnterWindowMask  LeaveWindowMask  PointerMotionHintMask
ButtonMotionMask StructureNotifyMask  SubstructureNotifyMask   
SubstructureRedirectMask PropertyChangeMask   
  number of visuals:28
  default visual id:  0x33
  visual:
visual id:0x20
class:PseudoColor
depth:8 planes
available colormap entries:256
red, green, blue masks:0x0, 0x0, 0x0
significant bits in color specification:8 bits
  visual:
visual id:0x21
class:PseudoColor
depth:8 planes
available colormap entries:256
red, green, blue masks:0x0, 0x0, 0x0
significant bits in color specification:8 bits
  visual:
visual id:0x22
class:StaticColor
depth:8 planes
available colormap entries:256
red, green, blue masks:0x7, 0x38, 0xc0
significant bits in color specification:8 bits
  visual:
visual id:0x23
class:PseudoColor
depth:8 planes
available colormap entries:256
red, green, blue masks:0x0, 0x0, 0x0
significant bits in color specification:8 bits
  visual:
visual id:0x24
class:PseudoColor
depth:8 planes
available colormap entries:256
red, green, blue masks:0x0, 0x0, 0x0
significant bits in color specification:8 bits
  visual:
visual id:0x25
class:PseudoColor
depth:12 planes
available colormap entries:4096
red, green, blue masks:0x0, 0x0, 0x0
significant bits in color specification:8 bits
  visual:
visual id:0x26
class:PseudoColor
depth:12 planes
available colormap entries:4096
red, green, blue masks:0x0, 0x0, 0x0
significant bits in color specification:8 bits
  visual:
visual id: 

Bug#270976: xlibs: doesn't understand IRIX xinerama X servers

2004-10-12 Thread Branden Robinson
retitle 270976 libx11-6: doesn't understand setup messages from 
XINERAMA-enabled IRIX X servers
reassign 270976 libx11-6
tag 270976 + upstream moreinfo
thanks

On Fri, Sep 10, 2004 at 11:46:03AM +0100, Matt Reynolds wrote:
> Package: xlibs
> Version: 4.3.0.dfsg.1-7
> Severity: important
> 
> > xclock
> Xlib: Did not parse entire setup message: parsed: 848, message: 1600
> Error: Can't open display: scully:0.0
> 
> My primary display is a dual-head RIIRIX Octane running Xinerama.
> 
> xdpyinfo reports:
> number of screens:1
> 
> screen #0:
>   dimensions:2560x1024 pixels (728x291 millimeters)
> resolution:89x89 dots per inch
> 
> but each time I try to display an X app from nmy debian machine to the 
> 
> irix machine, I get the following:
> 
> Xlib: Did not parse entire setup message: parsed: 848, message: 1600
> xdpyinfo:  unable to open display "scully:0.0".
> 
> The exact same machine running without xinerama works fine with remotely
> displayed apps from the same debain machine.. Every other Unix machine
> and linux distribution I've tried will display to the xinerama-enabled
> IRIX machine with no problems. I can't see why it's failing here (other
> than the fact that IRIX uses a slightly different xinerama extension to
> many of the other implementations out there, on the basis that Xorg
> never formalised it!).
> 
> Point is even if the xinerama information returned from the server isn't
> completely understood by the X client, it should still setup a connection
> and attempt to open a window..
> 
> I'm more than willing to run debug if it'll help...
> 
> (I tried installing the unstable xlibs too - no change)

I am sorry it has taken a while for us to reply to your bug report.

When you run xdpyinfo as above, is that really all the information you get
back?  There should be much more.

I am wondering what extension name is advertised by the IRIX X server when
XINERAMA is enabled, and xdpyinfo should tell us.

-- 
G. Branden Robinson|   Psychology is really biology.
Debian GNU/Linux   |   Biology is really chemistry.
[EMAIL PROTECTED] |   Chemistry is really physics.
http://people.debian.org/~branden/ |   Physics is really math.


signature.asc
Description: Digital signature


Processed: Re: Bug#270976: xlibs: doesn't understand IRIX xinerama X servers

2004-10-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> retitle 270976 libx11-6: doesn't understand setup messages from 
> XINERAMA-enabled IRIX X servers
Bug#270976: Doesn't understand IRIX xinerama X servers
Changed Bug title.

> reassign 270976 libx11-6
Bug#270976: libx11-6: doesn't understand setup messages from XINERAMA-enabled 
IRIX X servers
Bug reassigned from package `xserver-xfree86' to `libx11-6'.

> tag 270976 + upstream moreinfo
Bug#270976: libx11-6: doesn't understand setup messages from XINERAMA-enabled 
IRIX X servers
There were no tags set.
Tags added: upstream, moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#270976: xlibs: doesn't understand IRIX xinerama X servers

2004-09-10 Thread Matt Reynolds

Package: xlibs
Version: 4.3.0.dfsg.1-7
Severity: important

> xclock
Xlib: Did not parse entire setup message: parsed: 848, message: 1600
Error: Can't open display: scully:0.0

My primary display is a dual-head RIIRIX Octane running Xinerama.

xdpyinfo reports:
number of screens:1

screen #0:
  dimensions:2560x1024 pixels (728x291 millimeters)
resolution:89x89 dots per inch

but each time I try to display an X app from nmy debian machine to the 


irix machine, I get the following:

Xlib: Did not parse entire setup message: parsed: 848, message: 1600
xdpyinfo:  unable to open display "scully:0.0".

The exact same machine running without xinerama works fine with remotely
displayed apps from the same debain machine.. Every other Unix machine
and linux distribution I've tried will display to the xinerama-enabled
IRIX machine with no problems. I can't see why it's failing here (other
than the fact that IRIX uses a slightly different xinerama extension to
many of the other implementations out there, on the basis that Xorg
never formalised it!).

Point is even if the xinerama information returned from the server isn't
completely understood by the X client, it should still setup a connection
and attempt to open a window..

I'm more than willing to run debug if it'll help...

(I tried installing the unstable xlibs too - no change)

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-386
Locale: LANG=en_GB, LC_CTYPE=en_GB

Versions of packages xlibs depends on:
ii  libice64.3.0.dfsg.1-6 Inter-Client Exchange library
ii  libsm6 4.3.0.dfsg.1-6 X Window System Session Management
ii  libx11-6   4.3.0.dfsg.1-6 X Window System protocol client li
ii  libxext6   4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii  libxft14.3.0.dfsg.1-6 FreeType-based font drawing librar
ii  libxi6 4.3.0.dfsg.1-6 X Window System Input extension li
ii  libxmu64.3.0.dfsg.1-6 X Window System miscellaneous util
ii  libxmuu1   4.3.0.dfsg.1-6 lightweight X Window System miscel
ii  libxp6 4.3.0.dfsg.1-6 X Window System printing extension
ii  libxpm44.3.0.dfsg.1-6 X pixmap library
ii  libxrandr2 4.3.0.dfsg.1-6 X Window System Resize, Rotate and
ii  libxt6 4.3.0.dfsg.1-6 X Toolkit Intrinsics
ii  libxtrap6  4.3.0.dfsg.1-6 X Window System protocol-trapping
ii  libxtst6   4.3.0.dfsg.1-6 X Window System event recording an
ii  xlibs-data 4.3.0.dfsg.1-6 X Window System client data

-- no debconf information


--
/* Matthew Reynolds  | Secondline IRIX and Linux   *
 * SGI EMEA Customer Support | tel: 087060 SGISGI (744744) *
 * fax: +44 (0)118 925 7823  | web: http://www.sgi.com/*
 *  I write my .sig in emacs. ^x^s^x^c.*/

NB: Information in this message is SGI confidential. It is
intended solely for the person(s) to whom it is addressed and
may not be copied, used, disclosed or distributed to others
without SGI consent. If you are not the intended recipient
please notify me by email or telephone, delete the message
from your system immediately and destroy any printed copies.
So nerr.

** - note that if you send me an executable file attachment,
I won't get it. That means pif|com|exe|bat|scr|vbs and zip!!
This policy has very rarely been proved wrong!!!  - **