Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mutter mutter
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1.2k
    • Issues 1.2k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 138
    • Merge requests 138
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • muttermutter
  • Issues
  • #120
Closed
Open
Issue created Apr 16, 2018 by Pierre Ossman (Work account)@CendioOssman

GNOME fights VNC over display size

There's a bit of a usability issue when running GNOME inside a VNC X11 server:

If the user has at some point changed the display size in GNOME Settings, then GNOME will try to enforce that size on every login after that. This might be the right thing for a physical monitor, but it's not generally what VNC users want as they want the size of the VNC client window to control the session size.

A quick hack would be to look for "VNC-*" in the output name (I think other parts of GNOME does this), but that's not very robust. Perhaps there is some other mechanism we can implement in the VNC server to indicate that this is not a real monitor and should be mostly left alone?

Assignee
Assign to
Time tracking