> ideally systemd + homed will fix this when integrated with TPM properly, by generating secrets through it. But not something we want to handle with the current status quo
Thanks for looking into this. I don't know much about that stuff, but is there a related issue to watch in some other repo? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2073356 Title: Choose password for new keyring the first time chromium-browser is started on each session Status in chromium-browser package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I get this popup the first time I start chromium-browser: https://askubuntu.com/questions/1446379/why-am-i-always-asked-to- create-a-new-keyring either manually or via a startup script. Closing and restarting does not create the popup until I reboot. After the reboot, the password prompt is back again. What I do is just enter enter enter with empty password and life moves on. Under "Passwords and Keys" in settings, I just get a new "Default keyring" every time this happens. My disk is encrypted, I don't have a password to login, and I don't want to type any passwords after unlocking my disk during boot. Ubuntu 24.04, snap chromium version 126.0.6478.126. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2073356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
