Custom Query (230 matches)


Show under each result:

Results (58 - 60 of 230)

Ticket Resolution Summary Owner Reporter
#89 fixed xvnc status updates by watching server output (like nx does) Antoine Martin Antoine Martin

We should probably watch the output of the Xvnc process like we do for NX. Looks like we can detect if the session is connected or not: vncext: Listening for VNC connections on port 16064 Means no need to test using a wait_for_socket. Connections: accepted: Means we can remove the need for the client to set the CONNECTED status. Connections: closed: (Clean disconnection) As above for AVAILABLE.

Log Xvnc output to file ~/.Xvnc/:DISPLAY.log

Note: the code has only been tested with tigervnc...

#96 fixed binaries (debs/rpms,etc..) miss the Antoine Martin Antoine Martin
#99 fixed bump tigervnc to 1.0.1 (or even 1.1 if it is out) Antoine Martin Antoine Martin

Can't find the release notes, so I don't know how important this is..

Note: See TracQuery for help on using queries.