Displaying 20 results from an estimated 900 matches similar to: "[ANNOUNCE] xkbcomp 1.4.3"
2018 Mar 01
0
[ANNOUNCE] xkbcomp 1.4.1
This release adds the path of the xkbcomp executable to the pkgconfig
data, allowing the X server to find the right binary regardless of
where its (the X servers) $prefix is pointed. Without this the X server
will guess that xkbcomp is configured for the same prefix; since the
default prefix is /usr/local, and your distribution certainly did not
install xkbcomp there, 'make check' and
2017 May 01
0
[ANNOUNCE] xkbcomp 1.4.0
Hi,
This xkbcomp release mostly contains a couple of bugfixes and parser
improvements. Notably, ignoring keycodes that X11 can never support
means that we can start using those keycodes, which xkbcommon
supports.
Cheers,
Daniel
Benno Schulenberg (1):
When overriding a key, adjust also its number of levels (#57242).
Daniel Stone (2):
keycodes: Ignore high keycodes
xkbcomp
2018 Jun 07
0
[ANNOUNCE] xkbcomp 1.4.2
Only one patch, fixing keymap compilation errors when the keycodes maximum
is set to a value above the permitted X11 maximum of 255. While we already
ignored keys with codes above 255, we still failed on the maximum=374;
line that xkeyboard-config 2.24 produces now.
Peter Hutterer (2):
Ignore xkb_keycodes.maximum of > 255
xkbcomp 1.4.2
git tag: xkbcomp-1.4.2
2020 Nov 05
0
[ANNOUNCE] xkbcomp 1.4.4
Alan Coopersmith (1):
Fix spelling/wording issues
Miroslav Ko?k?r (1):
Fix lockdevbtn to be XkbSA_LockDeviceBtn action
Peter Hutterer (3):
For -R and after chdir, add the current directory to the path
Don't pretend unresolved symbols are an error
xkbcomp 1.4.4
git tag: xkbcomp-1.4.4
https://xorg.freedesktop.org/archive/individual/app/xkbcomp-1.4.4.tar.bz2
MD5:
2015 Nov 05
0
[ANNOUNCE] xkbcomp 1.3.1
Couple of minor fixes, the only user-visible change is that the warning when
a key type is shortened is now on a verbosity level above the default
verbosity. This effectively removes the warning below for all users of the
german keyboard layout (and others):
Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
Alan Coopersmith (1):
Stop including <X11/Xalloca.h>
2008 Mar 06
0
[ANNOUNCE] xkbcomp 1.0.4
Adam Jackson (2):
Bug #7645: Fix a conditional that always evaluates to FALSE.
xkbcomp 1.0.4
Alan Coopersmith (1):
Bug 14185: MAINTAINERCLEANFILES multiply defined in Makefile.am
Daniel Drake (1):
Bug #11025: xkbcomp COPYING file
James Cloos (3):
Rename .cvsignore to .gitignore
Add *~ to .gitignore to skip patch/emacs droppings
Replace static ChangeLog
2008 May 07
0
[ANNOUNCE] xkbcomp 1.0.5
Just two pretty minor changes here, but the last one might be a startup
time win, so might as well ship it. (Should be in 7.4.)
Daniel Stone (2):
xkbcomp: Take a device ID argument
Don't scan paths which make NO SENSE WHATSOEVER TO SCAN
git tag: xkbcomp-1.0.5
http://xorg.freedesktop.org/archive/individual/app/xkbcomp-1.0.5.tar.bz2
MD5: 6cc96c3e4ed5d9802fe717beac008f19
2006 Apr 26
0
[ANNOUNCE] xkbcomp 1.0.2
Bug #4851: Fix up have-no-file test.
CVS tag: xkbcomp-1_0_2
http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.2.tar.gz
65ad57be186352fbeeb530e44a8c6924 xkbcomp-1.0.2.tar.gz
1c36772c6ec5a63e6378ec92eb93512f21e99e6e xkbcomp-1.0.2.tar.gz
http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.2.tar.bz2
8b22a5e6d780ec70bf98d31cdbd65658 xkbcomp-1.0.2.tar.bz2
2020 Jul 22
0
xkbcomp is correctly applied to remap keyboard but it often gets reverted?
Why the xkbcomp correctly applied to remap keyboard, so frequently
gets reverted back?
Sometimes It'll have no affect anymore as if it wasn't ever run or
applied/deployed especially after a wake-up from suspend/sleep.
How to keep it fixedly persistent ?
2011 Nov 26
2
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
The function that returns ENOMEM is actually copy_mm. It returns
ENOMEM when dup_mm returns 0.
copy_mm receives clone_flags and task_struct * tsk. I think tsk
is pointing to the new task (the process being forked).
copy_mm assigns some values into *tsk, then:
tsk->mm = NULL;
tsk->active_mm = NULL;
then we check if current process has ->mm; if not, return 0
(effectively
1998 Feb 03
0
serious security problem in XKB
The Neverending Story of X11 Insecurity continues...
Summary:
On a system where X11R6.3-based Xserver with XKEYBOARD extension (R6.1 is
probably affected too) is run in setuid or setgid enviroment (e.g. typical
XFree86 installation has XF86_* installed setuid root), local users can
exploit a "feature" of XKB implementation to execute arbitrary commands
with the extra privileges.
2006 Nov 08
0
[ANNOUNCE] Broken sums in previous announcements
Hi all,
Sorry, the previous announcements had broken sums for the .tar.gz files;
I've pasted the corrected sums here. Thanks Tilman, or else I wouldn't
have noticed.
http://xorg.freedesktop.org/archive/individual/app/luit-1.0.2.tar.gz
MD5: 1acd244a489bae605a03a84d0754fb00 luit-1.0.2.tar.gz
SHA1: 3ea4328256a6576e12fcdac278263d2fef6edf63 luit-1.0.2.tar.gz
2012 Nov 07
4
[PATCH 2/2] 4.1.2 blktap2 cleanup fixes.
---------------------------------------------------------------------------
The following patch when applied on top of:
libxl: attempt to cleanup tapdisk processes on disk backend destroy.
Establishes correct cleanup behavior for blktap devices. This patch
implements the release of the backend device before calling for
the destruction of the userspace component of the blktap device.
Without
2013 Mar 26
3
iSCSI connection corrupts Xen block devices.
Hi, hope the week has started out well for everyone.
This report may be in the FWIW department since there may be a
fundamental reason why this doesn''t work. We elected to report this
to the Xen community since we thought any behavior which corrupted
disk images needed to at least be reported.
We are maintaining the Xen-SAN release which provides hotplug
functionality to allow Xen
2013 Apr 11
0
[xen-4.2-testing test] 17624: regressions - FAIL
flight 17624 xen-4.2-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/17624/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-oldkern 4 xen-build fail REGR. vs. 17611
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install
2013 Mar 10
1
XKB: Failed to compile keymap
I had to stop using the fglrx video driver from ELRepo, which isn't
supported with CentOS 6.4. Now I can't start X; I get the following:
> (II) [KMS] Kernel modesetting enabled.
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Cannot open "/tmp/server-0.xkm" to write keyboard
> description
> Exiting
> The XKEYBOARD
2009 Jan 31
1
[Bug 19860] New: xv texture adaptor kills X
http://bugs.freedesktop.org/show_bug.cgi?id=19860
Summary: xv texture adaptor kills X
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
ReportedBy:
2010 Nov 12
2
X11R7.6 Release Candidate 1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It's a bit after 11pm, on the 11th day of the 11th month of the year,
so what better time for a new release of X11!
Release Candidate 1 of X11R7.6 has been posted at:
http://www.x.org/releases/X11R7.6-RC1/
This includes all the source tar files for the versions of the modules
currently considered part of the core release set (aka the
2013 Mar 17
2
Re: Dom0 freeze on HVM DomU Windows reboot with VGA passthrough
On Mar 17, 6:14pm, Howell Tam wrote:
} Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA p
> Hi all again,
Hi, hope the weekend is going well for everyone.
> > > have you found a solution for this behaviour? Cause I''m currently
> > > seeing a similar result with my installation.
>
> I''ve been away for a few weeks and
2013 Mar 17
2
Re: Dom0 freeze on HVM DomU Windows reboot with VGA passthrough
On Mar 17, 6:14pm, Howell Tam wrote:
} Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA p
> Hi all again,
Hi, hope the weekend is going well for everyone.
> > > have you found a solution for this behaviour? Cause I''m currently
> > > seeing a similar result with my installation.
>
> I''ve been away for a few weeks and