> D. Michael McIntyre wrote:
>> On Friday, January 27, 2012, PMA wrote:
>>>>> You could reset your local configuration:
>>>>> rm -rf ~/.config/rosegardenmusic
>>>>> rm -rf ~/.local/share/rosegarden
>>>> I see that this would destroy some 200 files.
>> I probably wouldn't go for such a big sweep initially. Typically just
>> deleting ~/.config/rosegardenmusic/Rosegarden.conf is sufficient.
>> In any case, even if you do go for the double barrel approach, all of those
>> files should be replaced automatically the next time Rosegarden runs.
>>>> What about that would constitute a "reset"?
>> It reverts a great many things you might have changed back to factory stock.
>>> Just in case, is Rosegarden_4 (which chugged along happily
>>> on this system for a year) still available?
>> If you're going to go that route, it would be better to try building the
>> latest release, which should be pretty easy to do on Debian. A lot has
>> happened since April of 2010, and it's entirely possible your bug has gone
>> away since then.
>> If you did upgrade, and then purged all your local configuration nonsense, and
>> then still found this crash problem, that would be highly interesting.
>> Otherwise, not so much.
> Deleting Rosegarden.conf seems to have done the trick. Thanks!
FYI: The blow-ups happen again *if* I opt for my usual Preferences.
WIth one only -- Matrix editor as default -- there is no problem, so
I'm settling short-term for that alone. The others I'll test out later
singly to identify the culpirit(s), and report. Thanks for your help!