Hi, I compiled wine20050419 under slackware 10.1 via tools/wineinstall. After starting a xterm window on a remote X11 terminal (via properly initialized DISPLAY environment variable) I tried to start several wine progs (wcmd, winefile ...) and Windows applications (wine c:\\...) but each time I get X Error of failed request: BadShmSeg (invalid shared segment parameter) Major opcode of failed request: 144 (MIT-SHM) Minor opcode of failed request: 2 (X_ShmDetach) Segment id in failed request: 0x2400017 Serial number of failed request: 2058 Current serial number in output stream: 2090 If I correctly understand this error message the issue is related to the MIT shared memory extension which indeed is only supported by a local running X server (am I correct?). I tried to use available resources (google ..) but found nothing. What I have to do? Thanks for your time and support. Michael --
Hi, On Thu, Apr 21, 2005 at 10:35:54AM +0200, Michael Riedel wrote:
Hi,
I compiled wine20050419 under slackware 10.1 via tools/wineinstall.
After starting a xterm window on a remote X11 terminal (via properly initialized DISPLAY environment variable) I tried to start several wine progs (wcmd, winefile ...) and Windows applications (wine c:\\...) but each time I get
X Error of failed request: BadShmSeg (invalid shared segment parameter) Major opcode of failed request: 144 (MIT-SHM) Minor opcode of failed request: 2 (X_ShmDetach) Segment id in failed request: 0x2400017 Serial number of failed request: 2058 Current serial number in output stream: 2090 Wine remote displaying has been working for ages, so this is certainly a big problem that should be fixed. A CVS regression test might be in order...
Andreas Mohr
Le jeu 21/04/2005 à 05:11, Andreas Mohr a écrit :
Hi,
On Thu, Apr 21, 2005 at 10:35:54AM +0200, Michael Riedel wrote:
Hi,
I compiled wine20050419 under slackware 10.1 via tools/wineinstall.
After starting a xterm window on a remote X11 terminal (via properly initialized DISPLAY environment variable) I tried to start several wine progs (wcmd, winefile ...) and Windows applications (wine c:\\...) but each time I get
X Error of failed request: BadShmSeg (invalid shared segment parameter) Major opcode of failed request: 144 (MIT-SHM) Minor opcode of failed request: 2 (X_ShmDetach) Segment id in failed request: 0x2400017 Serial number of failed request: 2058 Current serial number in output stream: 2090 Wine remote displaying has been working for ages, so this is certainly a big problem that should be fixed.
I can confirm the problem here too (one of my a video cards started acting strange, so I've been back to ssh+x instead of local x for testing the 20050419 rh packages).
A CVS regression test might be in order...
20050310 worked in this respect. At least it's a start point. I won't have time until the weekend to work on that. Vincent
IF this happens when using SSH, something to check is what the actual settings of DISPLAY are: Normally under SSH, DISPLAY will be set to something like: DISPLAY=localhost:10 and SSH will forward TCP port 6010 on the remote machine to the local machine's X server on port 6000. It *could* be that Wine is looking at DISPLAY, seeing "localhost" and saying "AHA! This is localhost - I can use shared memory" - which it cannot. To test this hypothesis, try setting the DISPLAY environment variable to point directly to the computer you are using as the display (and making sure that machine is set to allow the remote machine to use the display), and see if the problem continues. If it does, then my hypothesis is wrong. If it starts working, then that would tend to confirm my hypothesis that Wine is being confused by the "localhost" in the DISPLAY variable.
David D. Hagood wrote:
To test this hypothesis, try setting the DISPLAY environment variable to point directly to the computer you are using as the display (and making sure that machine is set to allow the remote machine to use the display), and see if the problem continues.
If it does, then my hypothesis is wrong. If it starts working, then that would tend to confirm my hypothesis that Wine is being confused by the "localhost" in the DISPLAY variable.
I tried that about a week ago. The problem continues. -- Anssi Hannula
On Thu, Apr 21, 2005 at 06:24:03AM -0500, David D. Hagood wrote:
IF this happens when using SSH, something to check is what the actual settings of DISPLAY are:
Normally under SSH, DISPLAY will be set to something like:
DISPLAY=localhost:10
and SSH will forward TCP port 6010 on the remote machine to the local machine's X server on port 6000.
It *could* be that Wine is looking at DISPLAY, seeing "localhost" and saying "AHA! This is localhost - I can use shared memory" - which it cannot.
To test this hypothesis, try setting the DISPLAY environment variable to point directly to the computer you are using as the display (and making sure that machine is set to allow the remote machine to use the display), and see if the problem continues.
If it does, then my hypothesis is wrong. If it starts working, then that would tend to confirm my hypothesis that Wine is being confused by the "localhost" in the DISPLAY variable.
I have a dual head configurion and I tend to run fullscreen apps with a DISPLAY env variable so that I can read the wine output. I recently started getting this error, so it would appear to happen whenever the DISPLAY env variable is set, no matter if it's remote or not. I had put it down to some xlibs that I upgraded at the same time the error started happening. I haven't tried rolling back all the way to the March release, but I did roll back to 14th CVS, and that doesn't work. I had thought that the 14th had worked for me before the library upgrade, but I am probably mistaken. -- Alex
participants (6)
-
Alex Woods -
Andreas Mohr -
Anssi Hannula -
David D. Hagood -
Michael Riedel -
Vincent Béron