Comment 4 for bug 1080396

Revision history for this message
Chuck Short (zulcss) wrote :

This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. We should reopen the bug by when
we have more information and set the bug status back to ''New''.