xmodmap segfaults here parsing this line: keycode 111 = Print removing this line makes it work ok; works ok with XFree 4.3.0 xmodmap (it assign the KeySym correctly).
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=138743 for probable explanation.
Created attachment 1286 [details] [review] [FIXED_X11R68x] Patch for 6.8.2 to fix this and the original xmodmap overflow This is now fixed on HEAD. Attaching patch to fix the original xmodmap overflow for 6.8.2: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83720 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=103161 including the fix for this bug.
Closing as fix has been committed to head.
Comment on attachment 1286 [details] [review] [FIXED_X11R68x] Patch for 6.8.2 to fix this and the original xmodmap overflow Approved for the X11R6.8.x branch in the 2004-11-17 release-wranglers phone call. Please don't commit it yourself, I'll handle that once the CVS service is available again.
*** Bug 1875 has been marked as a duplicate of this bug. ***
Comment on attachment 1286 [details] [review] [FIXED_X11R68x] Patch for 6.8.2 to fix this and the original xmodmap overflow Patch checked-in into X11R6.8.x stable branch: /cvs/xorg/xc/ChangeLog,v <-- ChangeLog new revision: 1.365.2.11; previous revision: 1.365.2.10 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. /cvs/xorg/xc/programs/xmodmap/pf.c,v <-- pf.c new revision: 1.1.1.1.6.1; previous revision: 1.1.1.1 /cvs/xorg/xc/programs/xmodmap/xmodmap.c,v <-- xmodmap.c new revision: 1.2.4.1; previous revision: 1.2 /cvs/xorg/xc/programs/xmodmap/xmodmap.h,v <-- xmodmap.h new revision: 1.2.4.1; previous revision: 1.2 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. Mailing the commit message to xorg-commit@lists.freedesktop.org...
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.