Skip to content

GitLab

  • Menu
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 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 104
    • Merge requests 104
  • 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
  • Plasma
  • KWinKWin
  • Merge requests
  • !1345

Closed
Created Aug 30, 2021 by Xaver Hugl@zamundaaaDeveloper
  • Report abuse
Report abuse

workspace: fix slotOutputDisabled

  • Overview 3
  • Commits 1
  • Changes 1

Setting output variables based on positioning leaves dangling pointers to the disabled output as slotOutputDisabled is called before the output actually gets removed.

This fixes the crash but is still far from ideal - desktopResized is still called when the to-be-removed output is still there, and when the positioning of outputs has not yet changed.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: work/fix-no-output-crash