This seems more like a server issue. I think it could easily be possible for
the server to guarantee that XIDs are not reused within a certain time period
since it issued a DestroyNotify. That won't guarantee that clients are happy,
but it can certainly help. We just need to store a timestamp
Do you still have hardware to test this? Is it still an issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/35794
Title:
TV out is broken with VT1621 chip
Status in X.Org
This is coming from R128InitDDARegisters during init in r128_driver.c:
Roff = XclksPerTransferPrecise * (DisplayFifoDepth - 4);
Ron = (4 * info->ram->MB
+ 3 * MAX(info->ram->Trcd - 2, 0)
+ 2 * info->ram->Trp
+ info->ram->Twr
+ info->r
@colin-law no, this bug does not apply to Unity. This bug was filed
years before Unity even existed. If it is "fixed" by changing to Unity,
that's great for Unity users, but simply sweeping an issue under the rug
because you changed window systems doesn't change the fact the the bug
continues to
4 matches
Mail list logo
