On Wed, May 24, 2017 at 10:23:35AM -0700, Marc MERLIN wrote: > On Wed, May 24, 2017 at 05:42:05PM +1000, Dave wrote: > > The bug is with Xorg. > > > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998310 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550533 > > Xorg won't fix it, as they consider this feature deprecated. The best > > solution is to modify your XKB system files. > > This is the bug we agreed is in X: loading an .Xmodmap while X is > running causes a long freeze which seems dependent on how many clients > you have running. > The issue I'm describing only happens with newer enlightenment on 2 > different machines, and does not happen with old enlightenment or > cinamon.
The bug reports above indicate that xmodmap triggers a settings manager reload for each key change. Then X pauses and an avalanche of dbus chatter is triggered. In older versions of E, I think the settings manager was optional (and may have been disabled by default? Too long ago.) I don't see a config option in E 0.21's settings, so it's probably mandatory now. That would explain why you didn't see freezes on old E, and why I didn't see freezes with fvwm - no settings manager to trigger. > Is there a chance E 0.21 does something different than other WMs and in > turn it still triggers a bug in X? > > > > > https://unix.stackexchange.com/questions/122151/xmodmap-problems-and-inconsistencies-with-more-than-4-alternative-symbols-per-ke After reading that, I'd say the bug is that xmodmap is still shippped... Ross ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
