On Sun, Jan 1, 2017 at 9:05 AM, Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2016-12-29 23:42:53 -0700, Jaimos Skriletz wrote: >> I am just seeing if you have figured out if this was a video driver >> bug or not? Do you still experience this with with fvwm 2.6.7? > > Due to the numerous bugs in the nouveau driver over the years and > the lack of bug fixes, I've been using only the Nvidia driver for > some time. I have never seen any problem with Fvwm and this driver. > So, it was probably a driver bug. >
Thanks. I am going to close this bug for now. It is probably better to (re)open a bug against nouveau, if it is still present and you decide to go back to nouveau and assign the bug to that package. But for now I don't see a reason to reassign it. In either case it doesn't appear to be a bug within fvwm. jaimos
