Comment 32 for bug 1924624

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also the link in comment #30 is NOT related to this bug. It's the wrong hardware generation. You need to open a new bug.