From: SyedZuhair <syed@riseup.net>
To: emacs-orgmode@gnu.org
Subject: [BUG] org-resolve-clocks use of read-char-exclusive without telling EXWM to change the focus back to Emacs results in deadlock
Date: Thu, 09 Nov 2023 17:40:48 -0500 [thread overview]
Message-ID: <87zfzmk0sv.fsf@hoborg.mail-host-address-is-not-set> (raw)
The deadlock happens if org-resolve-clocks is called automatically (for
resolving idle time) while focus is in a EXWM-mode buffer. The
result is that the focus is stuck with the EXWM-mode buffer away from
Emacs and the user can not tell EXWM to change the focus to the
mini-buffer to interact with org because org is grabbing all the input
away from EXWM.
The only way out for the user is to kill the application in EXWM buffer
from another ttyn terminal to be able to interact with
org-resolve-clocks.
See the issue discussion here as well: https://github.com/ch11ng/exwm/issues/921
Steps to reproduce:
1. Run X with EXWM as its window manager.
2. Clock in some tasks in an org-buffer.
3. Start some non-Emacs application (like Firefox)) it will run in an
EXWM-mode buffer.
4. Leave the input for more than org-clock-idle-time.
5. org-resolve-clocks is get called and you get stuck in your
EXWM-mode buffer till you kill the application somehow, because all you
keys are all going to the EXWM-buffer and those that are supposed to go
to EXWM to interact with Emacs is grabbed by org-resolve-clocks and ignored.
Thank you very much.
Emacs : GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.38, cairo version 1.17.8)
Package: Org mode version 9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)
next reply other threads:[~2023-11-09 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 22:40 SyedZuhair [this message]
2023-11-10 9:33 ` [BUG] org-resolve-clocks use of read-char-exclusive without telling EXWM to change the focus back to Emacs results in deadlock Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfzmk0sv.fsf@hoborg.mail-host-address-is-not-set \
--to=syed@riseup.net \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).