Key repeat freezes emacs under Gnome 3/CentOS 7

Forum / NoMachine for Linux / Key repeat freezes emacs under Gnome 3/CentOS 7

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #7190
    reswaney
    Participant

    Hi,

    I am running NoMachine-workstation_4.5.0_1_x86_64.rpm on CentOS 7 with
    Gnome 3 desktop (as a virtual display).  Remote access to the server
    is via Enterprise Client on Windows 7.

    In Emacs, holding down a key repeat freezes Emacs within from 20 to a
    few hundred characters.  The key repeat characters are displayed in a
    visibly jerky way (until the point of freeze).  Also, the Emacs
    response is always a bit sluggish in general.  After freezing, it is
    necessary to end the process (the window-close button works).  (The
    mouse/cursor movement and the rest of the applications in the desktop
    session remain unaffected.)

    An odd thing: The above is always the behavior when the emacs instance
    is started as the normal login user.  However, if I start an emacs
    from a shell running as root, the response is not sluggish and the
    freeze-up does not occur.  This behavior is completely reproducible
    and can be obtained repeatedly by starting user and root Emacs
    processes within the same desktop session.

    Running Emacs in the same kind of Gnome 3 session on the physical
    display X server gives no problems for either user type.

    The Emacs version is that provided by the CentOS distribution: GNU
    Emacs 24.3.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.8.8) of
    2014-06-09.

    (The problem did not occur on the previous installation: RHEL 6,
    NoMachine-workstation-update_4.4.1_3_i686.rpm,
    emacs-el-1:23.1-21.el6_2.3 (x86_64))

    Any advice for remedy would be appreciated.

    #7203
    graywolf
    Participant

    May you get a gdb backtrace of frozen emacs process?

Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.