This bug is now marked resolved.
FWIW I need to add a comment to the final Note by JRalls:
"There are also instructions to unset the view in the error
dialog: Basically, start Gramps but don't open a database. You can
then change back to a functioning view without the bad one
crashing Gramps for you."
Gramps was crashing before I was able to start it without a
database; this option wasn't open.
I had also been premature in declaring the bug gone - after the
first apparent resolution with gramps -v I was no longer able to
start gramps at all. I kept getting this error.
I assume that gramps had got really screwed up as a result of
being repeatedly killed so I scrubbed it entirely by svn'ing to
the latest version.