unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Welsh Duggan <md5i@md5i.com>
Cc: 53146@debbugs.gnu.org
Subject: bug#53146: 29.0.50; Lock up in X11 call
Date: Mon, 10 Jan 2022 08:39:32 +0800	[thread overview]
Message-ID: <87wnj8qv97.fsf@yahoo.com> (raw)
In-Reply-To: <875yqs3dbh.fsf@md5i.com> (Michael Welsh Duggan's message of "Sun, 09 Jan 2022 14:43:14 -0500")

Michael Welsh Duggan <md5i@md5i.com> writes:

> Due to what I believe is a bug in Gnome shell or a Gnome shell extension
> that I have running, I am experiencing places where Emacs will lock up
> completely.  
>
> Under some unknown circumstances, when idle for a long while, sometimes
> gnome shell on my system will enter the activities overview instead of
> blanking the screen.  Why it does this is unknown, is likely a bug in
> gnome shell or one of my gnome extensions, and is likely itself
> unrelated to Emacs.  When I exit this state, though, Emacs is in a
> locked-up, unpainted (blank) state and will not respond to anything
> short of a SIGTERM.  Sending a SIGTERM will cause a frame to redraw, but
> Emacs remains in a locked and useless state.  With a second SIGTERM,
> emacs exits.
>
> I have attached to the locked up Emacs in a gdb session.  I've done this
> twice, and each time the backtrace was nearly identical, locking up in
> deep within XSetICValues() in xic_set_preeditarea().  This has been
> ocurring about once every two days, on average, so I can probably
> recreate it, if desired.

Hmm, could you try this with the following X resource applied?

  Emacs.inputStyle: none

Thanks.

Also, what version of GNOME Shell is that, and which extensions have you
installed?





  reply	other threads:[~2022-01-10  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 19:43 bug#53146: 29.0.50; Lock up in X11 call Michael Welsh Duggan
2022-01-10  0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-10  6:39   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13  2:13     ` Michael Welsh Duggan
2022-01-13  3:12       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-10 17:35   ` Michael Welsh Duggan
2022-01-10 17:36   ` Michael Welsh Duggan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wnj8qv97.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53146@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=md5i@md5i.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).