Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 84004 - gnome-terminal crashes using NCD x-server
Summary: gnome-terminal crashes using NCD x-server
Status: CLOSED DUPLICATE of bug 80414
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: gnome-terminal
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
Depends On:
Blocks: 79579
TreeView+ depends on / blocked
Reported: 2003-02-10 21:59 UTC by Tim Clymo
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:51:42 UTC

Attachments (Terms of Use)

Description Tim Clymo 2003-02-10 21:59:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
Current gnome-terminal rawhide (2.2.1-2) won't work on an NCD NC980. The NCD is
running the latest (4.0.11) server code.

I get the following error, and g-t crashes:
Xlib:  extension "RENDER" missing on display "".
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 728 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. export DISPLAY=<IP of NCD>
2. gnome-terminal

Actual Results:  Crash

Additional info:

FWIW, here's the output of xdpyinfo against the NCD display

name of display:
version number:    11.0
vendor string:    Network Computing Devices, Inc.
vendor release number:    4
maximum request size:  262140 bytes
motion buffer size:  256
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 4, scanline_pad 32
    depth 8, bits_per_pixel 8, 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 254
focus:  window 0x3c00017, revert to PointerRoot
number of extensions:    11
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1280x1024 pixels (346x277 millimeters)
  resolution:    94x94 dots per inch
  depths (6):    24, 1, 4, 8, 16, 32
  root window id:    0x23
  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 YES, save-unders YES
  largest cursor:    64x64
  current input event mask:    0xfe203f
    KeyPressMask             KeyReleaseMask           ButtonPressMask
    ButtonReleaseMask        EnterWindowMask          LeaveWindowMask
    ButtonMotionMask         StructureNotifyMask      ResizeRedirectMask
    SubstructureNotifyMask   SubstructureRedirectMask FocusChangeMask
    PropertyChangeMask       ColormapChangeMask
  number of visuals:    1
  default visual id:  0x21
    visual id:    0x21
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff, 0xff00, 0xff0000
    significant bits in color specification:    8 bits

Comment 1 Bill Nottingham 2003-02-11 05:52:41 UTC

*** This bug has been marked as a duplicate of 80414 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:51:42 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.