The problem really is isolated to gnome-keyring (as OP and others stated). Here's my workaround for Chrome... it might help others (like Photon). But in the end it is only a workaround. It does demonstrate that if you bypass the display manager (lightdm, gdm) triggering the gnome-keyring for you, everything works great.
By having a session not orchestrated by a display manager, apps work correctly: $ ssh -X localhost $ google-chrome & -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
