Shouldn't they trigger abrt then? more importantly, is it possible to capture that in the QA process during distribution composition? I believe a lot of those warnings aren't environment dependent, but rather would appear in a generic installation, so it would be appropriate to detect them early and take some corrective action---either block them or at least log bugs.All those are warnings, not "garbage" or debug output. File bugs about those, there should be zero warnings in normal usage.