[ghmerrill]

Okay, let me know if you need that.  The workaround (which is essentially de-automating a step) works for me.  It was just really surprising to encounter it.  I'm not sure exporting the settings will show anything.

When I do the restore and then follow that with an import of the settings, it ends up like it should (as far as I can see).  And it happened literally overnight.  I'd been using the old version late last night.  Then this morning after I'd updated (because I'd noticed that my Chrome version had updated), I ran straight into it -- at least that's my recollection.  The first sign was the display failure of that one PDF file, and then when I'd gotten around that via your suggestion, other things seemed to be revealed from there.  It's as though the database restore process ignores the settings and silently imposes the default ones.  But the Import Settings function appears to work.  And of course the ChromeOS (Android) version doesn't appear to even burp on the database restore.