it would be nice to update the menu link to support the command line option to detect the proper keystore Reproducible: Always
in addition to the URL listed on the bug report see also: http://code.google.com/p/chromium/issues/detail?id=77328
Well, we can't just add --password-store to the launcher flags because password sync has to be turned off to avoid instability: http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=1230517 I'm not sure what to do here, and would rather wait for the upstream.
How about looking for KDE or GNOME USE flags? If KDE and !GNOME you can safely enable --password-store=detect. Otherwise at least an ewarn about the issue should be there, so that everyone gets to know about that option and add it to the script manually if desired.
Unfortunately, upstream seems slow to deal with this issue. Anyway, the workaround is http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=1230517
That work around is not a resolution to the problem since every rebuild and upgrade will have the same issue. I like Marc's idea of using the use flags to update the desktop menu file with the --password-store=detect option. Until upstream has a real fix I don't see a reason to close this issue.
I think this has been fixed for chromium-12.x: http://code.google.com/p/chromium/issues/detail?id=70658 Sorry for the problems with this bug, but it's really an upstream issue. I'd rather not backport a patch that upstream doesn't want to backport, or add switches that are known to cause problems (deadlock).
