From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unclean shutdowns cause google-chrome profile to be corrupted in various ways
Date: Fri, 22 Aug 2014 18:17:38 +0000 (UTC) [thread overview]
Message-ID: <pan$a7366$366442ed$60aa89a1$c636b8e3@cox.net> (raw)
In-Reply-To: 20140822155040.GU3875@merlins.org
Marc MERLIN posted on Fri, 22 Aug 2014 08:50:40 -0700 as excerpted:
> Fairly often (over 20 times for me so far with various kernel versions),
> when I reboot after a crash, my google-chrome profile is damaged in one
> of 2 ways:
> 1) open tabs don't reopen 2) google-chrome says that my profile is
> corrupted.
>
> In both cases rsyncing ~/.config/google-chrome from the last hourly
> snapshot has fixed the problem every time.
I've had a similar issue with firefox, tho I've narrowed it down to a
single file, IIRC preferences.js, which firefox keeps plenty of backups
of (I see seven, going back quite some way), and recovering it from the
last firefox backup or from my own backups has worked the three-ish times
it happened here. But it was a bit disconcerting to see firefox pop up
its new profile wizard the first time it happened, and it took me awhile
to figure out which file I needed to restore to get my skins and
extensions back to normal.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-08-22 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 15:50 Unclean shutdowns cause google-chrome profile to be corrupted in various ways Marc MERLIN
2014-08-22 17:32 ` Eric Sandeen
2014-08-22 18:46 ` Marc MERLIN
2014-08-22 18:17 ` Duncan [this message]
2014-08-22 18:49 ` Marc MERLIN
2014-08-23 2:52 ` Duncan
2014-08-23 3:10 ` Marc MERLIN
2014-08-23 5:45 ` Naohiro Aota
2014-08-23 12:32 ` Marc MERLIN
2014-08-23 13:09 ` Holger Hoffstätte
2014-08-23 5:56 ` Duncan
2014-08-23 12:34 ` Marc MERLIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$a7366$366442ed$60aa89a1$c636b8e3@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).