Re: Problem with Xserver and Gnome applications



On 2008-01-24, J.A. Gutierrez <spd@xxxxxxxxxxxxxxxxxxxx> wrote:

Hello

I have noticed a problem while trying to display X clients
running on Linux systems with remote display on IRIX 6.5
X server.

- Server:

IRIX64 6.5.24f
X11 Execution Environment, 6.5.24, based on X11R6.6
Default screen #0:

dimensions: 1280x1024 pixels (396x297 millimeters)
resolution: 82x88 dots per inch
depths (5): 1, 8, 12, 15, 24
root window id: 0x35
depth of root window: 24 planes

- Clients:

Several recent Linux distributions, for example Mandriva 2008.1
lib64gdk_pixbuf2.0_0-2.12.5-2mdv2008.1
gnome-common-2.20.0-2mdv2008.1

$ gedit
The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 72 error_code 2 request_code 139 minor_code 1)

request_code is 139, which being greater than 127, means that the failed
request belongs to an X11 extension. First though is that maybe the Xsgi
server does not support that extension and gedit doesn't check for it
properly? Aparently major opcode of 139 belongs to the TOG-CUP
extension, see if that's listed at xdpyinfo of your SGI X server, or not.

However an unsupported extension opcode would cause a BadRequest, not a
BadValue, error. BadValue means, as the parenthesis indicates, that one
of the arguments passed to the specific extension's request is invalid.
minor_code of 1, means that the request is GetReservedColormapEntries.
The only value given to that request according to TOG-CUP specification
(http://www.x.org/docs/Xext/tog-cup.pdf), is the screen number. It's
highly unlikely that gedit always sends an invalid screen number, and
X.org lets it get away with that, and it's just Xsgi that barfs...
Unless it's an endianess issue, which would be an Xlib bug (xorg's
one)... but that's even more inlikely.
The best course of action is to send a bug report to gedit with all the
above information, and see where that leads to. It could be an Xsgi bug,
so send them an email, if you have a support contract with SGI, and see
if they care in their current sad state :) It's a pretty obscure
extension AFAIK, and a bug might have crept unnoticed.

--
John Tsiombikas (Nuclear / Mindlapse)
http://nuclear.sdf-eu.org/
.



Relevant Pages

  • Re: xserver-xorg-video-geode: Problems with geode Xorg driver
    ... corrupted When I try the EXA AccelMethod the server crashes ... ... X.Org Server Extension, ... Loading extension XFree86-DRI ... clock/interlace/doublescan) GEODE: Not using default mode ...
    (Ubuntu)
  • Re: xserver-xorg-video-geode: Problems with geode Xorg driver
    ... corrupted When I try the EXA AccelMethod the server crashes ... ... X.Org Server Extension, ... Loading extension XFree86-DRI ... clock/interlace/doublescan) GEODE: Not using default mode ...
    (Ubuntu)
  • xserver-xorg-video-geode: Problems with geode Xorg driver
    ... When I try the EXA AccelMethod the server crashes ... ... ABI class: X.Org Server Extension, ... Loading extension XFree86-DRI ...
    (Ubuntu)
  • Re: Cant get OMA going
    ... The extension was already set to "Allow." ... Expand the server name. ... The Windows SharePoint Services ISAPI filter handles all ... > |> Kerberos authentication is disabled Integrated Windows ...
    (microsoft.public.exchange.clients)
  • Re: bug in time() related to DST?
    ... closes that short window of DST transition. ... > an indication of what the bug in my code is. ... > The servers are running Win2000 Server. ... > The call to GetLocalTimewill have the correct time and the time ...
    (microsoft.public.vc.language)