I'm still getting the same  bug with nvidia-driver 384.111-1 and kernel
4.14.0-2. Stems the bug wasn't fixed.

Reply via email to