Logic Pro crashes keycommands while session

Question

Logic 7.2, another mysterious bug. Some of the keycommands crash down while a usual logic-session. For example the "m" for mute. It doesn´t work anymore. If I go to alt-K (for changing keycommands--- it doesn´t work either, so I run the menu), everything seems to be alright, "m" is asigned to mute. But it still does not work. Sometimes I can´t even type something in this alt-K-menue, the keyboard seems to be disconnected. But this problem just occures in Logic.
Anyone could help? Thanks

Answer 1

I can get the project loaded with its plug-ins crossed out no problems (via launching from Spotlight and having Logic auto-load its last project, rather than double-clicking on the project file in a Finder window). I'm a Logic novice, though (does it show?! ), and at the moment the only way I can find to bypass a plug-in is to access the view of that plug-in (translucent black window) by double-clicking on its entry in the channel strip and clicking on the 'Bypass' button therein. This window doesn't work for disabled plug-ins, though; is there another way? I'll RTFM one day, but it's > 1000 pages...! In the mean time, I just removed plug-in instruments entirely from tracks to narrow it down. I've got as far as it being Waldorf Attack that's at fault, but I don't know which instance yet.
I would have assumed some sort of Logic preferences or actual project document corruption with the failures I was seeing and wouldn't have expected a plug-in to somehow end up corrupted, so your suggestion has been invaluable and I should be able to recover everything from here. I've no idea how to avoid this in future, as frequent saving didn't seem to be sufficient - a full history of the project files all crashed Logic today. Ho hum, I don't seem to have much luck with this Mac Pro really; shame as the laptop has been solid as a rock from the day it was bought.