On 01.10.2013 21:12, Knut Petersen wrote:
Hi everybody!
A full build of xorg (todays git sources) succeeded, but the
server fails to load the keymap.
[ 1231.896] (EE) Error loading keymap
/home/knut/fast/xorg/X11-z/usr/share/X11/xkb/compiled/server-0.xkm
[ 1231.896] (EE) XKB: Failed to load
Thank you Knut
Will commit it to PVCS tonight
Sergey Udaltsov
On Oct 2, 2013 10:01 AM, Knut Petersen knut_peter...@t-online.de wrote:
On 01.10.2013 21:12, Knut Petersen wrote:
Hi everybody!
A full build of xorg (todays git sources) succeeded, but the
server fails to load the keymap.
[
Hi Sergey / James!
There is nothing in Xorg.0.log, but redirecting stdout/stderr
to a file shows the following xkbcomp output:
[...]
The XKEYBOARD keymap compiler (xkbcomp) reports:
Internal error: Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
stderr gives better info than Xorg.0.log:
syntax error: line 19 of level3
The XKEYBOARD keymap compiler (xkbcomp) reports:
Error:Error interpreting include file level3
Exiting
Abandoning symbols file basic
Attached
On Wed, Sep 11, 2013 at 11:44:35AM -0400, Jasper St. Pierre wrote:
Though I'd love to look into the gnome-shell issue more (changing to the
overview should not call XIGrabKey/XIUngrabKey a ton of times), the
handling in the server here was ridiculous and this is obviously an
improvement.
syntax error: line 19 of level3
The XKEYBOARD keymap compiler (xkbcomp) reports:
Error:Error interpreting include file level3
Ouch. Sorry.
Exactly the same thing in symbols/level5. We just missed release 2.10,
unfortunately.
It seems a 2.10.1 release will be
On Wed, Oct 2, 2013, at 11:43, Knut Petersen wrote:
Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
This warning (though harmless) is fixed by this patch:
https://bugs.freedesktop.org/attachment.cgi?id=86805
attached to
On 02.10.2013 12:31, Benno Schulenberg wrote:
On Wed, Oct 2, 2013, at 11:43, Knut Petersen wrote:
Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
This warning (though harmless) is fixed by this patch:
Fixes freedesktop.org bug https://bugs.freedesktop.org/show_bug.cgi?id=67484
If t-bottom is close to MIN_INT, removing top can wraparound, so do the check
properly.
A similar fix should also be applied to pixman.
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
---
diff --git
Signed-off-by: Adam Jackson a...@redhat.com
---
dix/dispatch.c | 5 -
include/dixstruct.h | 1 +
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/dix/dispatch.c b/dix/dispatch.c
index 71fda48..59ba011 100644
--- a/dix/dispatch.c
+++ b/dix/dispatch.c
@@ -167,6 +167,7 @@
v4: Use the new PostDispatchCallback, to avoid recursing through
FlushCallback - WriteToClient - FlushCallback - ...
Screen 0 holds the real damage for all drawable types; the window
report hooks for other screens look up screen 0 and pile on. Therefore
we don't need to wrap Subtract, though we
On Wed, Oct 2, 2013 at 11:56 AM, Adam Jackson a...@redhat.com wrote:
maybe mention in the commit message that this is required to xineramify damage?
Alex
Signed-off-by: Adam Jackson a...@redhat.com
---
dix/dispatch.c | 5 -
include/dixstruct.h | 1 +
2 files changed, 5
I guess I will need 2.10.1 anyway. Even 2.10 was not properly made. My ssh
keys are in trouble, cannot get to xorg.fd.o. Could anyone on the list
please help me with that?
Sergey Udaltsov
On Oct 2, 2013 11:23 AM, Benno Schulenberg bensb...@justemail.net wrote:
syntax error: line 19 of
This reverts commit 282587cd0709850e7bacb1d8307065d95dc2c97d.
Requiring the glamor package by default breaks the build as this package
contains development files and is generally not installed by default in distros.
It also goes against user expectations that the X source tree can be built
out
On Wed, Oct 2, 2013 at 5:13 PM, Gaetan Nadon mems...@videotron.ca wrote:
This reverts commit 282587cd0709850e7bacb1d8307065d95dc2c97d.
Requiring the glamor package by default breaks the build as this package
contains development files and is generally not installed by default in
distros.
This is something of a pessimization, since now we'll call the
provider's MakeCurrent hook more often. But that's correct, since the
provider might have a current GL context itself (think glamor), so while
this cache might be useful it should be done down in the provider
itself.
Reviewed-by:
Losing the drawable does not change our notion of current client. Since
the GL under us doesn't understand having a current context without
current drawables (sigh), we do still need to loseCurrent so that we
re-bind the context on the next request.
Bugzilla:
I broke this, back in:
commit a48dadc98a28c969741979b70b7a639f24f4cbbd
Author: Adam Jackson a...@redhat.com
Date: Mon Mar 21 11:59:29 2011 -0400
glx: Reimplement context tags
In that, I changed the glx client state to not explicitly track the list
of current contexts for
We can just free the resource unconditionally here. ContextGone (which
FreeResourceByType will call) already does:
cx-idExists = GL_FALSE;
if (!cx-currentClient) {
__glXFreeContext(cx);
}
Signed-off-by: Adam Jackson a...@redhat.com
---
glx/glxcmds.c | 4 +---
1 file
On Tue, 2013-09-03 at 14:38 -0700, Eric Anholt wrote:
The following changes since commit 94d4e29aedc69431fa9b299ca1b67947173d7a24:
Xi: allow for XIAllowEvent requests larger than XI 2.2 size (#68554)
(2013-08-30 14:26:55 +1000)
are available in the git repository at:
On 13-10-02 05:17 PM, Alex Deucher wrote:
On Wed, Oct 2, 2013 at 5:13 PM, Gaetan Nadon mems...@videotron.ca wrote:
This reverts commit 282587cd0709850e7bacb1d8307065d95dc2c97d.
Requiring the glamor package by default breaks the build as this package
contains development files and is generally
21 matches
Mail list logo
