Version 0.41 causes graphical glitches on Linux (Ubuntu 12.04). For the record, many other mods work fine.

Could you explain what "graphical glitches" mean and post screenshots?

There is constant flickering on the screen with horizontal black stripes. Sometimes it doesn't happen right away. It starts after getting back from map view, or after going back to the hangar or the menu. I took a lot of screen shots, but I didn't manage to catch the stripe effect as it shortly disappeared each time I tried to take a screen shot of it. That flickering effect (sometimes) happens in the menu view, in the hangar, and on the launchpad.

I also had a suspicion that KAS only causes the problem in conjunction with the map overlay from the kethane mod, but I ran some tests, first turning off the map overlay, and then by completely removing the kethane mod, but the problem persisted. The kethane mod does not cause any issues on it's own.

Although I didn't manage to take screenshot of the black stripe flickering, I did get some screenshots of other effects: black screen in the menu, in the hangar, and in the hangar, as well as stripes on the ground in the menu background.

I have experienced these graphical problems too. In my case, it occurs only when the game is very very close to it's memory limit. It is not tied specifically to KAS, though KAS seems to take more memory than other things, though it could just be the same as other large mods and being the straw that breaks the camel's back.

This is typical of too many mods loaded at once on KSP under Linux.

I've run into this before. From what I can tell some of the shader memory gets corrupted because too many textures and/or are loaded.

If you reduce texture sizes in your various mods you should be able to fix this while keeping all mods installed. All textures except MBM can be shrunk directly using GIMP. Keep in mind that it is the uncompressed size that matters, so compressing them better won't help. I recommend focusing on the 2048x2048 and 1024x1024 textures that some sets ship. If something has key details that cannot shrink, just skip it and move onto the next one. There is little to gain by shrinking 512x512 and almost nothing from shrinking 128x128 and smaller textures.

As of MBM textures, you can find a guide on how to edit them on the KSP forum. You can then either convert them back to MBM after you shrink them by reversing the process, or you can follow the instructions on the KSP forum post to change the models to use the new textures in whatever format you want. (They use PNG for their example.)

Additionally, you can delete out the parts you don't use from your various parts packs. This can save significant memory as well.

That would seem to make sense; I am no longer using quite as many mod parts and using the reduced squad/KW/B9 textures, and now everything is behaving, even with KAS installed. So I guess this is solved for me. I can't tell (without doing a downgrade) if .22 has had anything to do with it.

From what I can tell, 0.22 has a slightly larger base memory footprint than
0.21.x.
This may have a lot to do with it.