Comment 16 for bug 74034

Revision history for this message
logunn (riku-nevala) wrote : One confirmation

I can confirm, REMOVING SETSERIAL AND BOOTING worked for me. Maybe just booting might have fixed the problem.