unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Joe Corneli via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 56869@debbugs.gnu.org
Subject: bug#56869: 29.0.50; segfault, "assertion 'GDK_IS_DEVICE (device)' failed"
Date: Sun, 14 Aug 2022 12:21:54 +0100	[thread overview]
Message-ID: <87mtc73wa5.fsf@Proteus> (raw)
In-Reply-To: <83bkspod15.fsf@gnu.org>


Eli Zaretskii writes:

> The backtrace says:
>
>  . the main loop called some command
>  . that command signaled an error
>  . the error caused the Lisp debugger to be called
>  . the debugger was invoked and entered recursive-edit
>  . while waiting for user input, a timer fired
>  . the timer function called write-region
>  . write-region called lock-file
>  . lock-file called a Lisp function, probably to report some conflict
>    with another process(??) locking the file
>  . Emacs prompted the user, probably about the lock
>  . while waiting for user response, Emacs checked timers, and as
>    result called process_pending_signals
>  . one of the pending signals was SIGIO, so Emacs called read-socket,
>    which segfaulted inside GTK
>
> Does the above sound reasonable for your Emacs sessions?

Thanks, that’s certainly a reasonable chain of events, e.g. given that I
have mu4e running (which likes to use locks) and there might have been a
conflict between two different running instances.  Not sure about the
last step involving GTK.  In my workflow I think the crash occurred only
when I was switching between windows in my WM.


-- 
Dr Joseph A. Corneli (https://github.com/holtzermann17)

HYPERREAL ENTERPRISES LTD is a private company limited by shares, incorporated
25th, June 2019 as Company Number 634284 on the Register of Companies for
Scotland (https://beta.companieshouse.gov.uk/company/SC634284).





  parent reply	other threads:[~2022-08-14 11:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 13:08 bug#56869: 29.0.50; segfault, "assertion 'GDK_IS_DEVICE (device)' failed" Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02  1:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 14:17   ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 18:22     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03  1:14       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11  9:56         ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11 11:48           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11 13:34             ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12  1:17               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 11:45                 ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 12:35                   ` Eli Zaretskii
2022-08-12 13:23                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14 11:21                     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-12 12:36                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14 11:18                     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 14:00                       ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16  0:58                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 10:14                           ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 10:52                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 14:36                               ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-17 13:47                                 ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-18  2:38                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-18 13:20                                     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-19  1:42                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-21  9:57                                         ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-21 10:56                                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-21 11:00                                             ` Eli Zaretskii
2022-08-22  6:21                                               ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22  6:37                                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22 11:27                                                   ` Eli Zaretskii
2022-08-22 12:59                                                   ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03  9:13                                             ` Stefan Kangas

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=87mtc73wa5.fsf@Proteus \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56869@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joseph.corneli@hyperreal.enterprises \
    --cc=luangruo@yahoo.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).