Comment 13 for bug 1193332

Ok, so this issue is seen still regularly, even in recent QA-5.6 tree revisions. Requesting re-triage to high based on that, maybe even critical is warranted, all depends on severity of message itself. I assume original 'medium' was set based on disk space being full or not, but this issue now confirmed reproduces without disk full. Attempting to get good testcase (if needed).