Bug 88691

Summary: Cannot open postscript documents - backing pixmap problem
Product: [Retired] Red Hat Linux Reporter: Need Real Name <chhabra>
Component: gvAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: high    
Version: 9CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: http://groups.google.com/groups?q=group:comp.os.linux.misc+author:Madhusudan+author:Singh&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=b754fg%24bb4kr%241%40ID-159130.news.dfncis.de&rnum=1
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-13 17:48:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2003-04-11 22:13:17 UTC
Description of problem:

Whenever I try to open a postscript document gv, I get the following error :

Warning: Could not allocate backing pixmap in main window.

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  73 (X_GetImage)
  Serial number of failed request:  29
  Current serial number in output stream:  29

Error: PostScript interpreter failed in main window.

I am using Gnome.

When I use ggv, it returns with another error message indicating that the
document cannot be opened.

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

gv-3.5.8-22
ggv-1.99.97-2

How reproducible:

Every time the above action is attempted

Steps to Reproduce:
1. gv filename.ps
2. ggv > Open > filename.ps
3.
    
Actual results:

An infoPopup window opens up with the error text, while gv shows a blank page.

Expected results:

gv ought to show the document properly.

Additional info:

None that I can think of.

Comment 1 Need Real Name 2003-04-13 17:48:56 UTC
The problem lay with misconfiguration of the X server which assumed an extremely
high value of resolution (xdpyinfo | grep "resolution"). Fixed it in
/etc/X11/XF86Config.