From: Frank Terbeck <ft@bewatermyfriend.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37671@debbugs.gnu.org
Subject: bug#37671: 27.0.50; Segmentation fault with --fg-daemon on Linux
Date: Sat, 01 Feb 2020 13:49:02 +0100 [thread overview]
Message-ID: <87y2tmwk01.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <83wo96ikdb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Feb 2020 14:04:48 +0200")
Eli Zaretskii wrote:
[...]
> It sounds like switching workspaces is relevant to the issue at hand.
> Can you try moving the mouse pointer off the Emacs frame before
> switching to the workspace where Emacs isn't visible, and moving the
> mouse pointer to a place where it won't be on any Emacs frame before
> switching back? If you do that, do the crashes still happen?
I will try and remember this. The issue is, though, that because the
problem occurs only as infrequently as it does, I can't guarantee that I
will remember doing it every time, I switch workspaces. Because over the
course of a couple of weeks, I switch workspaces hundreds of times easi-
ly without anything ever going wrong. :)
I usually have Emacs as a mostly full-screen window with small status
bars above and below it.
> Also, which window manager is the one you use?
It's XMonad¹ — which is one of those tiling window managers that are not
re-parenting window managers².
¹ https://xmonad.org
² https://en.wikipedia.org/wiki/Re-parenting_window_manager
>> Anyway. I'm running my emacs inside gdb again, in case it happens again.
>> Let me know if I can be of further assistance.
>
> Thanks. Next thing I'd like you to try is this simple band-aid:
[...]
Can do! Do you want me to try this right away or give the "move the
mouse pointer off of the window" routine a shot for a while first?
Regards, Frank
next prev parent reply other threads:[~2020-02-01 12:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 1:55 bug#37671: 27.0.50; Segmentation fault with --fg-daemon on Linux Frank Terbeck
2019-10-10 11:03 ` Eli Zaretskii
2019-10-10 18:27 ` Frank Terbeck
2020-01-08 3:23 ` Frank Terbeck
2020-01-08 16:28 ` Eli Zaretskii
2020-01-08 16:39 ` Frank Terbeck
2020-02-01 2:28 ` Frank Terbeck
2020-02-01 8:33 ` Eli Zaretskii
2020-02-01 2:43 ` Frank Terbeck
2020-02-01 8:46 ` Eli Zaretskii
2020-02-01 11:28 ` Frank Terbeck
2020-02-01 12:04 ` Eli Zaretskii
2020-02-01 12:49 ` Frank Terbeck [this message]
2020-02-01 13:08 ` Eli Zaretskii
2020-02-01 14:32 ` Frank Terbeck
2020-02-15 8:28 ` Eli Zaretskii
2020-02-15 11:32 ` Frank Terbeck
2020-03-05 7:19 ` Eli Zaretskii
2020-03-06 0:09 ` Frank Terbeck
2020-03-06 7:51 ` Eli Zaretskii
2019-10-10 20:56 ` Paul Eggert
2019-10-11 7:02 ` Eli Zaretskii
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=87y2tmwk01.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=37671@debbugs.gnu.org \
--cc=eliz@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.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).