xpra icon
Bug tracker and wiki

Opened 3 months ago

Closed 2 months ago

#2011 closed defect (needinfo)

After XPRA Client timed out, `xpra start` does not show a window

Reported by: stdedos Owned by: stdedos
Priority: major Milestone: 2.5
Component: server Version: 2.4.x
Keywords: Cc:

Description

Related: #1997, #2010

I had started a remote session successfully with:
$ xpra start ssh://sntentos@ip --start=gnome-terminal

and the attached Windows machine died of battery.

Now, even though I attach "successfully", I see no GUI.

Attachments (2)

unable-to-see.zip (83.4 KB) - added by stdedos 3 months ago.
trac_2011_new-attempt.zip (164.7 KB) - added by stdedos 2 months ago.

Download all attachments as: .zip

Change History (13)

Changed 3 months ago by stdedos

Attachment: unable-to-see.zip added

comment:1 Changed 3 months ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos

For some reason, your window is showing:

windows.1.state=('_NET_WM_STATE_HIDDEN',)

Can you try connecting from a Linux client, or even the html5 client, to see if the window is shown there?

comment:2 Changed 3 months ago by stdedos

Apologies. Indeed I didn't specify the sequence of events correctly.

Now, even though I attach "successfully", I see no GUI.

Now, even though I attach "successfully", I see no GUI - even if I attach from the Ubuntu 16.04.5 server that is at the "ip".

comment:3 Changed 3 months ago by Antoine Martin

You should be able to get the same effect as the "died of battery" event by unplugging the network cable, abruptly shutting down the virtual machine (assuming this is one) or maybe even by forcibly killing the client process (with kill -9).

None of these attempts make the gnome-terminal window disappear for me.
I will need more precise steps to reproduce.
At the very least, please attach the server log.

comment:4 Changed 3 months ago by stdedos

Server log is in the zip file, as ":9-server.log"

comment:5 Changed 2 months ago by Antoine Martin

Ah, indeed, the server log was hidden in there.

Next time you can reproduce it, please post the steps here.
Please try to run something like:

xdotool search -class gnome-terminal windowactivate
xdotool search -class gnome-terminal windowfocus
xdotool search -class gnome-terminal windowraise

Against the xpra display. Does that help restore the window?

comment:6 Changed 2 months ago by stdedos

Please remove /w attachment. It was a report for #2010

It happened again. Unfortunately, I have no replication instructions :/

I ran the command once, it gave me the empty window. I ran it again, and I collected all the diagnostics through that session :/

I hope the collected diagnostics are helpful

command

"C:\Program Files\Xpra\xpra_cmd" start ssh://user@ip/ --webcam=no --speaker=off --microphone=off --opengl=no --start=gnome-terminal

Note that cliboard sync was on. But it doesn't matter (I hope), because I got it happening 1 times out of 3~5, even with client clipboard off

"C:\Program Files\Xpra\xpra_cmd" start ssh://sntentos@172.16.57.121/ --webcam=no --cliboard=no --speaker=off --microphone=off --opengl=no --start=gnome-terminal
Last edited 2 months ago by stdedos (previous) (diff)

Changed 2 months ago by stdedos

Attachment: trac_2011_new-attempt.zip added

comment:7 in reply to:  5 Changed 2 months ago by stdedos

I thought I was debugging this (see above comment), but then I was thinking: How can I run this "against the xpra display"? The usecase of this one is to start only a terminal (I didn't / haven't thought of starting a terminal to call a GUI). If gnome-terminal has failed, then ... I don't have a terminal (unless of course, I always start xterm --> gnome-terminal)

In some naive attempt (see above), I did from a second DISPLAY (:2):

$ DISPLAY=:1 xdotool search -class gnome-terminal windowactivate
XGetWindowProperty[_NET_WM_DESKTOP] failed (code=1)
$ xdotool search -class gnome-terminal windowactivate
XGetWindowProperty[_NET_WM_DESKTOP] failed (code=1)
$ xdotool search -class gnome-terminal windowfocus
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  42 (X_SetInputFocus)
  Serial number of failed request:  113
  Current serial number in output stream:  115
$ xdotool search -class gnome-terminal windowraise
$ DISPLAY=:1 xdotool search -class gnome-terminal windowraise
$

but the responses didn't sound welcoming

Last edited 2 months ago by Antoine Martin (previous) (diff)

comment:8 Changed 2 months ago by Antoine Martin

How can I run this "against the xpra display"?

DISPLAY=:whatever somecommand

You can find the display with xpra list.

You can also start new commands (ie: an xterm) from the xpra system tray if you enable --start-new-commands=yes.

comment:9 in reply to:  8 Changed 2 months ago by stdedos

Replying to Antoine Martin:

How can I run this "against the xpra display"?

DISPLAY=:whatever somecommand

You can find the display with xpra list.

Before the commands at comment:7, I did

$ DISPLAY=:1 xdotool search -class gnome-terminal
$ xdotool search -class gnome-terminal

However, the "numbers" returned appeared to be the same for both commands (I don't have them right now, but they were "big" numbers, starting with the same 16... 14...). Shouldn't they be different, like e.g. a PID is?

Last edited 2 months ago by Antoine Martin (previous) (diff)

comment:10 Changed 2 months ago by Antoine Martin

Please read the manual to understand the concept of X11 display numbers.

If you don't want to have to figure out which display your session uses, specify the display on the command line.
Preferably starting it via a terminal session directly on the server.

comment:11 Changed 2 months ago by Antoine Martin

Component: androidserver
Resolution: needinfo
Status: newclosed
Note: See TracTickets for help on using tickets.