Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S switcheroo-control
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • Bastien Nocera
  • switcheroo-control
  • Issues
  • #21
Closed
Open
Created Apr 14, 2021 by Dominik Mierzejewski@rathann

switcheroo-control.service unit prevents display-manager.service startup

After installing switcheroo-control and rebooting, the display manager (here: lightdm) doesn't get started by systemd anymore.

switcheroo-control.service has display-manager.target in the Before= line, but there's no such target unit. At least, there are no other references to display-manager.target on my system while there are many references to display-manager.service. I think the latter was meant here. Indeed, after replacing .target with .service, the display manager does get started correctly.

$ rpm -q switcheroo-control 
switcheroo-control-2.4-2.fc34.x86_64
Assignee
Assign to
Time tracking