P.S. What concerns this error, some type of exception handling should be built in Swami for such cases, in order that some dummy shortcut not to break app start.
Ok Swami is a program Jeff has mostly wrote and as he notes:
Swami is a newer tool and we've tested it for a variety of use cases - but obviously whatever state your current system is in right now was not one of them.
It is a work in progress with a limited amount of developers, a limited amount of time to develop, only Bodhi users testing it and most likely only forum users reporting issues. As such it is best to regard it as Beta-software. While it has been tested for typical users cases on Bodhi and it works without error as far as I know in these cases, the issue you stumbled across is not typical. A system file was borked for whatever reason.
As far as "exception handling should be built in Swami for such cases", perhaps but let me quote something I read on stackoverflow regarding exceptions and defensive programming:
You should be defensive but to a point. You should write exception handling but to a point.
The question is where is this point? To test for all possible errors, including hardware malfunctions is overkill for most applications excepting apps where someones life is at stake. Swami is not such an app. For an app such as swami it is more appropriate to test for expected 'normal' errors. To Jeffs defense a system file being broken was not expected and should not have occurred.
Ok that being said, I have taken note of your error as well as another related issue I noted a few days ago and patched swami locally to catch such cases. As soon as I find time I will run my patch thru some tests to ensure it hasn't broke any functionality, commit it to github and if Jeff approves update Bodhis deb file. This is way open source works. Judgmental whining about "poor coding practices" is hardly ever appropriate and this goes double if a patch is not posted or the complaint is from a non programmer.
Bodhi is what it is a small community an even smaller number of developers and all of us working essentially for free. As an operating system it satisfies my needs altho I modify it some, as a team member I try to fix issues reported or that I discover if I can and when I have time. And I work on the Bodhi projects that interest me or I myself use or those I think are critical or some of the stuff Jeff or another team member suggests I look at. Again when I have time. Probably the same is true for all Bodhi team members.