Comment 2 for bug 334524

Thanks for submitting this, but it's not a bug.

If Mixxx had been flooding your .xsession-errors to the point where it was causing your X to crash or it was filling your HDD to capacity, then we would have removed whatever particular debug statement was at fault.

In this case though, this is just normal terminal output that Mixxx produces (it would be impossible to diagnose user problems without some type of debug info telling us what Mixxx was doing when it misbehaved or right before it crashed). .xsession-error is just capturing everything streamed to stderr that you would otherwise see if you had started Mixxx from a terminal window.

-G