xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Version 1 and Version 2 of Ticket #352


Ignore:
Timestamp:
06/06/13 07:13:40 (8 years ago)
Author:
Antoine Martin
Comment:

Cannot reproduce.


This is what I see when I use "xpra stop" to stop the session (this solution is preferred to SIGINT):

New connection received: SocketConnection(/home/antoine/.xpra/desktop-10)
connection closed after 0 packets received (0 bytes) and 0 packets sent (0 bytes)
Connection lost
Handshake complete; enabling connection
Python/GObject Linux client version 0.10.0 connected from 'desktop'
windows/pixels forwarding is disabled for this client
max client resolution is 0x0 (from []), current server resolution is 2560x1600
Shutting down in response to request
Disconnecting existing client Protocol(SocketConnection(/home/antoine/.xpra/desktop-10)), reason is: shutting down
connection closed after 2 packets received (577 bytes) and 2 packets sent (1101 bytes)
xpra client disconnected.
Connection lost
Connection lost
New connection received: SocketConnection(/home/antoine/.xpra/desktop-10)
connection closed after 0 packets received (0 bytes) and 0 packets sent (0 bytes)
Connection lost
xpra is terminating.
closing tcp socket 0.0.0.0:10000
removing socket /home/antoine/.xpra/desktop-10
killing xvfb with pid 9346
Server terminated successfully (0). Closing log file.

TIL:

removing socket /home/antoine/.xpra/desktop-10

And now with killall -SIGINT xpra:

got signal SIGINT, exiting
xpra is terminating.
closing tcp socket 0.0.0.0:10000
removing socket /home/antoine/.xpra/desktop-10
killing xvfb with pid 9939
Server terminated successfully (0). Closing log file.

This also worked fine. Using SIGTERM has the same effect. I've tried both with and without --no-daemon.

And now with control-C from the controlling terminal:

^C
got signal SIGINT, exiting
child 'xterm' with pid 10181 has terminated
xpra is terminating.
closing tcp socket 0.0.0.0:10000
removing socket /home/antoine/.xpra/desktop-10
killing xvfb with pid 10172
Server terminated successfully (0). Closing log file.

The only way that I can get the server to not cleanup its socket is to use SIGKILL or to kill the vfb from underneath it, which is not something we can handle gracefully anyway, so just don't do that.

Here is the command line I have used for most of this testing:

dbus-launch xpra start :10 --no-daemon --no-pulseaudio

(adding/removing dbus and pulseaudio does not seem to make any difference) I am only adding dbus-launch because of the warning in your logs, looks to me like you are running from a desktop session and should either be using dbus-launch (if you aren't already) or --no-notifications.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #352

    • Property Owner changed from Antoine Martin to ahuillet
    • Property Status changed from assigned to new
  • Ticket #352 – Description

    v1 v2  
    88It also doesn't kill X, so the Xdummy process remains, and the server doesn't start.
    99
    10 Trimmed output when killed with ^C:
     10Trimmed output when killed with control-C:
    1111{{{
    1212got signal SIGINT, exiting
    1313Tray.cleanup()
    1414Tray.cleanup() done
    15 failed to release dbus notification forwarder: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
     15failed to release dbus notification forwarder: \
     16    org.freedesktop.DBus.Error.NoReply: Did not receive a reply. \
     17    Possible causes include: the remote application did not send a reply, \
     18    the message bus security policy blocked the reply, \
     19    the reply timeout expired, or the network connection was broken.
    1620cleanup will disconnect: []
    1721}}}