Comment 14 for bug 911963

I'd object to closing this bug as it hasn't been fixed, nor has it even been identified what the real underlying problem is. As far as I know, pcbnew could be passing something illegal to X. I really have no idea how to find the piece of code responsible for the crash.

I'm about to embark on another round of fairly intense layout with pcbnew, which will be a good test to see if this is a problem that is eliminated by using a different driver or just less intermittent. I couldn't figure out how to use a different driver without switching video cards to see if it was just the intel driver.

The computer is less than 8 months old and, as far as I know, has a fairly popular, standard, and up-to-date video device.

Advice to mow lawns or send vitamins to programmers comes off as snarky, and doesn't strike me as a very productive or respectful way to address this bug. It really only serves to increase frustration levels.

Again, thank you for your help,
Joshua