similar to: Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked

From: Martin Schwidefsky <schwidefsky at de.ibm.com> The SIE instruction on s390 uses the 2nd half of the page table page to virtualize the storage keys of a guest. This patch offers the s390_enable_sie function, which reorganizes the page tables of a single-threaded process to reserve space in the page table: s390_enable_sie makes sure that the process is single threaded and then uses

On 5/5/23 1:22 PM, Linus Torvalds wrote: > On Fri, May 5, 2023 at 6:40?AM Nicolas Dichtel > <nicolas.dichtel at 6wind.com> wrote: >> >> Is this an intended behavior? >> This breaks some of our scripts. > > It doesn't just break your scripts (which counts as a regression), I > think it's really wrong. > > The worker threads should show up as

Hi Konrad, Sometime ago i reported this one at boot up: [ 3009.778974] mcelog:16842 map pfn expected mapping type write-back for [mem 0x0009f000-0x000a0fff], got uncached-minus [ 3009.788570] ------------[ cut here ]------------ [ 3009.798175] WARNING: at arch/x86/mm/pat.c:774 untrack_pfn+0xa1/0xb0() [ 3009.807966] Hardware name: MS-7640 [ 3009.817677] Modules linked in: [ 3009.827524] Pid:

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

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

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

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:

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>

Adam Jackson (1): Suppress high-keycode warnings at the default warning level Alan Coopersmith (1): Update configure.ac bug URL for gitlab migration Andreas Boll (2): pkgconfig: Remove unneeded Requires.private configure: Remove unused AC_SUBST([REQUIRED_MODULES]) Andreas Wettstein (1): xkbcomp Fix missing support for "affect" and incorrect modifier

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

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

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

The 32-bit and 64-bit versions of copy_thread have functionally identical handling for copying the I/O bitmap, modulo differences in error handling. Clean up the error paths in both by moving the copy of the I/O bitmap to the end, to eliminate the need to free it if subsequent copy steps fail; move the resulting identical code to a static inline in a common header. Signed-off-by: Josh Triplett

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 ?

reassign 646987 linux-2.6 2.6.32-39 thanks This is a bug in the kernel. Bastian -- One does not thank logic. -- Sarek, "Journey to Babel", stardate 3842.4

In a hosted VMM like LinuxOnLinux or UML, context switch time can be a major problem (as mmap when repeated for each guest page frame takes a long time). One solution is to allow the host kernel to keep a cache of address space contexts, and switch between them in a single operation. The attached patch is a start at this. It works well for LinuxOnLinux; but I'd be interested from the

In a hosted VMM like LinuxOnLinux or UML, context switch time can be a major problem (as mmap when repeated for each guest page frame takes a long time). One solution is to allow the host kernel to keep a cache of address space contexts, and switch between them in a single operation. The attached patch is a start at this. It works well for LinuxOnLinux; but I'd be interested from the

I experienced a bug that is likely the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, doesn't appear in this kernel and doesn't apply cleanly either. Is there any point in trying to backport the patch? The backtrace is as follows: [ 32.304666] ------------[ cut here ]------------ [

The 32-bit and 64-bit versions of copy_thread have functionally identical handling for copying the I/O bitmap, modulo differences in error handling. Clean up the error paths in both by moving the copy of the I/O bitmap to the end, to eliminate the need to free it if subsequent copy steps fail; move the resulting identical code to a static inline in a common header. Signed-off-by: Josh Triplett

The 32-bit and 64-bit versions of copy_thread have functionally identical handling for copying the I/O bitmap, modulo differences in error handling. Clean up the error paths in both by moving the copy of the I/O bitmap to the end, to eliminate the need to free it if subsequent copy steps fail; move the resulting identical code to a static inline in a common header. Signed-off-by: Josh Triplett