Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • L librem5-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Librem5
  • librem5-base
  • Issues
  • #55
Closed
Open
Created Jan 01, 2022 by Guido Gunther@guido.guntherOwner

pam changes break adding GOA accounts

The pam changes to unlock the login keyring while working well when used on existing systems break on new installs as seen in https://matrix.to/#/!FwbcAdwtvCYkHekZKf:talk.puri.sm/$WuWhRt5D7J_pqUoE_TQ8Ike6yb12HSDtdmLbp7C28z8?via=talk.puri.sm&via=matrix.org&via=librem.one as gnome-keyring daemon spawns a senseless prompt that can't be cancelled (but the credentials do get added).

Since there's no way to add any goa accounts this is rather critical. Worst case we revert the pam change.

/cc @angus.ainslie since this would affect newly flashed devices when the factory floor image gets updated

Edited Jan 01, 2022 by Guido Gunther
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking