clicking on Revert silently removes the user's .gtkrc-2.0 file

[Micah Gersten]

Report from Vincent Lefevre in Debian:
I was wondering why Iceweasel was no longer working as expected...
I finally found the cause: my ~/.gtkrc-2.0 file had been removed.
Then I remembered that I used gtk-theme-config recently. After
some tests, clicking on the "Revert" button has this effect of
removing the ~/.gtkrc-2.0 file, without even leaving a backup!

When changing some settings, gtk-theme-config modifies this file.
But when the user clicks on "Revert", gtk-theme-config should just
remove the settings it added, e.g. by using begin/end markers, not
the whole file! Or if is this too difficult, it should warn the
user before doing a destructive operation.

Note also that it isn't documented at all that gtk-theme-config
uses the ~/.gtkrc-2.0 file. This is even more surprising as
gtk-theme-config depends on libgtk-3-0 (thus GTK+ 3, not GTK+ 2).

[Sean Davis (bluesabre)]

The fix for this is now committed and will be in the next release.

https://bazaar.launchpad.net/~gtk-theme-config-maintainers/gtk-theme-config/trunk/revision/132

[Sean Davis (bluesabre)]

Fix released. Included in GTK Theme Config 1.2.1

[Launchpad Janitor (janitor)]

This bug was fixed in the package gtk-theme-config - 1.2.1-0ubuntu1

---------------
gtk-theme-config (1.2.1-0ubuntu1) wily; urgency=medium

  * New upstream bugfix and translations release
    - Fixes destructive config file editing (lp: #1473821)
  * debian/patches:
    - All patches dropped, included upstream.
  * debian/control:
    - No change update to Standards-Version 3.9.6
  * debian/watch:
    - Update to point to current upstream releases

 -- Sean Davis <email address hidden> Thu, 08 Oct 2015 06:11:56 -0400