44075 – Problem with libart backend and gnustep

Bug 44075 - Problem with libart backend and gnustep

Summary: Problem with libart backend and gnustep

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Gentoo Gnustep project

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-03-08 14:37 UTC by Cedric Godin
Modified:	2004-09-24 09:40 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Cedric Godin 2004-03-08 14:37:25 UTC

when "openapping" Gorm remotely, I receive a bunch of errors and all appears white at screen. Here are the error messages :

2004-03-08 23:23:09.878 Gorm[30747] X-Windows error - BadPixmap (invalid Pixmap parameter)
          on display: nout:1.0
                type: 0
       serial number: 924
        request code: 2
2004-03-08 23:23:09.933 Gorm[30747] X-Windows error - BadShmSeg (invalid shared segment parameter)
          on display: nout:1.0
                type: 0
       serial number: 931
        request code: 148

(both the server and the client have gnustep launched).


Reproducible: Always
Steps to Reproduce:
1.emerge gnustep-*
2.emerge app-gnustep/gorm
3.openapp Gorm (remotely)



Expected Results:  
see Gorm (or any gnustep app).

I tried this via a remote X connection, via ssh conenction, same results.

Comment 1 Armando Di Cianno (RETIRED) gentoo-dev

2004-09-24 09:40:28 UTC

First, there are new packages available.
Secondly, the libart_lgpl based backend is not intended for remote X usage.  The xlib backend is intended to still support X remoting.  So, using the new packages, you can "emerge -pv gnustep-back-xlib" and run the support script "/usr/GNUstep/System/Tools/Gentoo/config-gnustep-back-xlib.sh" to change to use of this backend.