workspaces-issues icon indicating copy to clipboard operation
workspaces-issues copied to clipboard

[BUG] 'Display Manager' and therefore access to 'native resolution' does not appear in the control panel.

Open gorstj opened this issue 1 year ago • 1 comments

Existing Resources

  • [ x] Please search the existing issues for related problems
  • [ x] Consult the product documentation : Docs
  • [ x] Consult the FAQ : FAQ
  • [ x]x Consult the Troubleshooting Guide : Guide
  • [ x] Reviewed existing training videos: Youtube

Describe the bug 'Display Manager' and therefore access to 'native resolution' does not appear in the control panel.

To Reproduce Upgraded from 1.14 --> 1.15 Since then unable to find the High DPI setting within the 'control panel' In 1.14 this used to be within the 'streaming' section In 1.15 I understand it has changed to 'native resolution' within the 'Display Manager' section of control panel There is no 'Display Manager' in my control panel. I have added the appropraite setting for all users control_panel.show_display_manager = true (see screenshot)

I have tried on:

  • Chrome on Mac Os X (M1 Macbook, single screen, 2560 x 1600) - see screenshot below
  • Edge on Windows 10 (dual screen setup QHD and surface laptop 2304 x 1536 (201 PPI))
  • Chrome and Safari on iOS/iPhone

Expected behavior A tab for 'Display Manager' so I can access native resolution

Screenshots image image

Workspaces Version v 1.15

Workspaces Installation Method Single Server

Client Browser (please complete the following information):

  • OS: Mac Os x
  • Chrome
  • 126.0.6478.183

Workspace Server Information (please provide the output of the following commands):

  • uname -a Linux kit 5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  • cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
  • sudo docker info
Client: Docker Engine - Community
 Version:    26.1.4
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.5.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-compose

Server:
 Containers: 20
  Running: 20
  Paused: 0
  Stopped: 0
 Images: 40
 Server Version: 26.1.4
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d2d58213f83a351ca8f528a95fbd145f5654e957
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-116-generic
 Operating System: Ubuntu 22.04.4 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 11.91GiB
 Name: kit
 ID: ae10b3d9-344f-4c0b-b7b0-66838c02be1a
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
  • sudo docker ps | grep kasm
fe05a2b6c518   kasmweb/ubuntu-jammy-desktop:1.14.0      "/dockerstartup/kasm…"   11 hours ago   Up 11 hours             4901/tcp, 5901/tcp, 6901/tcp                                                                     johngorst.me_fc8b10d6
dd3e555bce39   kasmweb/nginx:1.25.3                     "/docker-entrypoint.…"   21 hours ago   Up 11 hours             80/tcp, 0.0.0.0:8443->8443/tcp, :::8443->8443/tcp                                                kasm_proxy
50e833b3faa5   kasmweb/agent:1.15.0                     "/bin/sh -c '/usr/bi…"   21 hours ago   Up 11 hours (healthy)   4444/tcp                                                                                         kasm_agent
fdcac6c682d7   kasmweb/share:1.15.0                     "/bin/sh -c '/usr/bi…"   21 hours ago   Up 11 hours (healthy)   8182/tcp                                                                                         kasm_share
73c4e237c6f9   kasmweb/api:1.15.0                       "/bin/sh -c '/usr/bi…"   21 hours ago   Up 11 hours (healthy)   8080/tcp                                                                                         kasm_api
794bf12a3ae3   kasmweb/manager:1.15.0                   "/bin/sh -c '/usr/bi…"   21 hours ago   Up 11 hours (healthy)   8181/tcp                                                                                         kasm_manager
072c1b1fc51d   kasmweb/kasm-guac:1.15.0                 "/dockerentrypoint.sh"   21 hours ago   Up 11 hours (healthy)                                                                                                    kasm_guac
dae93c9ad520   redis:5-alpine                           "docker-entrypoint.s…"   21 hours ago   Up 11 hours             6379/tcp                                                                                         kasm_redis
3c700758fa7c   postgres:12-alpine                       "docker-entrypoint.s…"   21 hours ago   Up 11 hours (healthy)   5432/tcp   

Additional context nil

gorstj avatar Jul 24 '24 07:07 gorstj

Partially resolved by updating the underlying container to 1.15

However, RDP connections still do not have Display Manager within control panel (accepting that multiple displays are unlikely, but still need to access native resolution setting)

gorstj avatar Jul 24 '24 20:07 gorstj

We’re currently enhancing our GitHub issue tracker to improve organization and efficiency.

As part of this process, we’re closing older issues to help keep the tracker focused on current and active topics.

If this issue is still relevant or you’re still experiencing the problem, please feel free to create a new issue.

Thank you for your understanding!

teja-kasm avatar Oct 14 '25 17:10 teja-kasm