On 2018-03-06 00:44, Vincent Lefevre wrote: > It appears that while the bug was fixed in unstable > (384.111-1 -> 384.111-4), a new buggy version has just been uploaded > to unstable (387.34-4), as detected by apt-listbugs. Indeed, this bug > is marked as found in 387.34-1, but there's no fixed version for 387.*:
That driver will be replaced by 390.25 in sid in a few hours :-) Andreas
