Project

General

Profile

Actions

action #58367

closed

vnc port information is wrong for > 99

Added by coolo about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2019-10-18
Due date:
% Done:

0%

Estimated time:

Description

You might be able to connect to the SUT at openqaworker9:107 via VNC with shared mode enabled (eg. vncviewer openqaworker9:107 -Shared for TigerVNC).

This is wrong, TigerVNC can't handle 107 because it thinks it's the real port - and because of that you need to use openqaworker9:6007. Always using the real port might be the best solution, but at least for >99 it's important

Actions #1

Updated by mkittler about 5 years ago

  • Status changed from New to In Progress
  • Assignee set to mkittler
  • Target version changed from Ready to Current Sprint
Actions #3

Updated by mkittler about 5 years ago

  • Status changed from In Progress to Resolved
  • Target version changed from Current Sprint to Done

PR has been merged

Actions

Also available in: Atom PDF