Re: [PATCH] libx11 xkb/XKBMAlloc.c fix check for map->num_types

On 06/ 5/14 04:21 PM, Daniel Stone wrote: Hi, On 5 June 2014 15:46, walter harms mailto:wha...@bfs.de>> wrote: fix: check for map->num_types overflow compiletestested, i have no example to check this condition but i guess that this was the original author intended This isn't an

Re: [PULL 1.15] Misc XQuartz fixes and fbGlyphs origin

merged. 7b3aa3f..268eb96 server-1.15-branch -> server-1.15-branch On 06/05/2014 09:37 PM, Jeremy Huddleston Sequoia wrote: > In addition to the XQuartz cherry-picks, this includes the fbGlyphs origin > fix as well. > > --- > > The following changes since commit 7b3aa3f0be8d1334dbf23bd042

Re: [PATCH] render: Don't generate invalid pixman format when using a 24bpp framebuffer with a 32bit depth visual.

Some background on this patch: I've been trying to investigate why gnome-terminal doesn't render correctly when running Ubuntu 14.04 LTS inside qemu (on Ubuntu 14.10). The window is compressed in the X axis and has transparency (seems to be a buffer somewhere that is being written in RGB and read

Re: [PATCH mi 1/1] mi: Build fix: mieqProcessDeviceEvent returns void

On Thu, Jun 05, 2014 at 08:40:33PM -0700, Jeremy Huddleston Sequoia wrote: > mieq.c:520:9: error: void function 'mieqProcessDeviceEvent' should not return > a value [-Wreturn-type,Semantic Issue] > return 0; > ^ ~ > 1 error generated. > > Regression-from: 9fb08310b51b46736f3c

[PATCH] render: Don't generate invalid pixman format when using a 24bpp framebuffer with a 32bit depth visual.

When using the fb backend at 24bpp it allows a visual with 32 bit depth. This would cause RENDER to try and create an invalid pixman buffer and hit the following assertion when trying to render to it: *** BUG *** In create_bits_image_internal: The expression PIXMAN_FORMAT_BPP (format) >= PIXMAN_F

Re: [PATCH v2] mi: don't process events from disabled devices (#77884)

Introduces a build failure: http://tinderbox.x.org/builds/2014-06-05-0001/logs/xserver/#build mieq.c:520:9: error: void function 'mieqProcessDeviceEvent' should not return a value [-Wreturn-type,Semantic Issue] return 0; ^ ~ 1 error generated. make[1]: *** [mieq.lo] Error 1

[PULL 1.15] Misc XQuartz fixes and fbGlyphs origin

In addition to the XQuartz cherry-picks, this includes the fbGlyphs origin fix as well. --- The following changes since commit 7b3aa3f0be8d1334dbf23bd04258a8856a4329c7: XQuartz: Ensure we wait for the server thread to terminate (2014-04-14 18:48:39 -0600) are available in the git repository

[PATCH mi 1/1] mi: Build fix: mieqProcessDeviceEvent returns void

mieq.c:520:9: error: void function 'mieqProcessDeviceEvent' should not return a value [-Wreturn-type,Semantic Issue] return 0; ^ ~ 1 error generated. Regression-from: 9fb08310b51b46736f3ca8dbc04efdf502420403 Signed-off-by: Jeremy Huddleston Sequoia CC: Peter Hutterer ---

Re: [PATCH] libx11 xkb/XKBMAlloc.c fix check for map->num_types

Hi, On 5 June 2014 15:46, walter harms wrote: > > fix: check for map->num_types overflow > compiletestested, i have no example to check this condition > but i guess that this was the original author intended > This isn't an overflow check, but one to ensure that we always have at least XkbNumRe

[PATCH] libX11 fix:redundant null checks

This patch removes some redundant null checks before free it should not chance the code otherwise. Be aware that this is only the frist series. Signed-off-by: Harms --- src/FetchName.c | 4 ++-- src/Font.c | 22 +++--- src/FontInfo.c | 4 ++-- src/FontNames.c | 4

[PATCH] libx11 xkb/XKBMAlloc.c fix check for map->num_types

fix: check for map->num_types overflow compiletestested, i have no example to check this condition but i guess that this was the original author intended Signed-off-by: Harms --- src/xkb/XKBMAlloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/xkb/XKBMAlloc.c b/src/x

Re: [PATCH util/modular] Add gpg signing to release.sh

Hi Peter, On Thu, 5 Jun 2014 10:05:15 +1000, Peter Hutterer wrote: > On Sun, Jun 01, 2014 at 03:13:13PM +0200, Stephen Kitt wrote: > > +[ -n "$targz" ] && rm -f ${targz}.sig && $GPG -b $targz && > > siggz=${targz}.sig || true > > +[ -n "$tarbz2" ] && rm -f ${tarbz2}.sig && $GPG -b $tarbz2

How to fix assert from ProcRRSetProviderOutputSource.

Hi, When you have two graphic cards that both have Source Output and Sink Output capabilities (intel and nouveau for example). It's very easy to flip parameters of xrandr --setprovideroutputsource and attempt to provide outputs of the main screen to the slave screen. That triggers assert fault