Not sure what's to be done for that. The patch should work as is against
1.16. I've already asked on the list, but maybe someone here knows, am I
just supposed to make another patch like the other one and make this one
against the server-1.16-branch instead of against the master?
--
You received
Not sure what's to be done for that. The patch should work as is against
1.16. I've already asked on the list, but maybe someone here knows, am I
just supposed to make another patch like the other one and make this one
against the server-1.16-branch instead of against the master?
--
You received
The patch has been accepted as 1b94fd77792310c80b0a2bcf4bf6d4e4c4c23bca.
I believe this fixes the problem (it does for me), but will of course
defer to the poster if they're still around. Please test to confirm it
fixes your specific problem if you can.
--
You received this bug notification
The patch has been accepted as 1b94fd77792310c80b0a2bcf4bf6d4e4c4c23bca.
I believe this fixes the problem (it does for me), but will of course
defer to the poster if they're still around. Please test to confirm it
fixes your specific problem if you can.
--
You received this bug notification
No, this is **NOT** an nVidia (or any driver) problem (emphasis because
the common misconception seems to be that it is an nVidia/ATI/AMD
proprietary driver issue, even I shared this misconception before
looking at the code). It is a problem with the implementation of the
Bresenham (bres for
No, this is **NOT** an nVidia (or any driver) problem (emphasis because
the common misconception seems to be that it is an nVidia/ATI/AMD
proprietary driver issue, even I shared this misconception before
looking at the code). It is a problem with the implementation of the
Bresenham (bres for
Created attachment 101029
Patch to maintain no segfault in fbBresSolid while fixing the algorithmic
problems created in 863d528a9f76d0e8f122aebf19f8564a4c67a938
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As has been identified this is a problem with
http://cgit.freedesktop.org/xorg/xserver/commit/?id=863d528a9f76d0e8f122aebf19f8564a4c67a938
. Specifically the reordering created seriously messes up the algorithm
in certain cases (causing offsets of the starting point for instance). I
examined what
Created attachment 101029
Patch to maintain no segfault in fbBresSolid while fixing the algorithmic
problems created in 863d528a9f76d0e8f122aebf19f8564a4c67a938
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As has been identified this is a problem with
http://cgit.freedesktop.org/xorg/xserver/commit/?id=863d528a9f76d0e8f122aebf19f8564a4c67a938
. Specifically the reordering created seriously messes up the algorithm
in certain cases (causing offsets of the starting point for instance). I
examined what
10 matches
Mail list logo
