Custom Query (230 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (127 - 129 of 230)

← 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 →
Ticket Resolution Summary Owner Reporter
#89 fixed xvnc status updates by watching server output (like nx does) Antoine Martin Antoine Martin
Description

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: 127.0.0.1::51920 Means we can remove the need for the client to set the CONNECTED status. Connections: closed: 127.0.0.1::51920 (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 build_info.py Antoine Martin Antoine Martin
#99 fixed bump tigervnc to 1.0.1 (or even 1.1 if it is out) Antoine Martin Antoine Martin
Description

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

← 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 →
Note: See TracQuery for help on using queries.