Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • KWin KWin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 58
    • Issues 58
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 160
    • Merge requests 160
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PlasmaPlasma
  • KWinKWin
  • Issues
  • #42
Closed
Open
Issue created May 14, 2021 by Vlad Zahorodnii@vladzDeveloper0 of 3 checklist items completed0/3 checklist items

DRM backend without any outputs connected

Currently, if there is no any physical output connected, kwin will wait until one is connected and proceed with startup; or if the last output is disconnected, it won't notify the rest of kwin about it, which is a wild territory as it leads to inconsistency between Screens and platform outputs.

KWin should gracefully handle the case where there are no outputs. We may also need to consider the possibility of creating a virtual output if there are no outputs, however kwin still needs to handle the case where there are no outputs.

Sub-tasks:

  • port Workspace away from Screens, port most of int-based screen api in Toplevel to AbstractOutput
  • make Workspace and AbstractClient handle gracefully absence of any outputs connected
  • introduce DrmPlaceholderOutput or something?
Edited May 14, 2021 by Vlad Zahorodnii
Assignee
Assign to
Time tracking