From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Joe Corneli <joseph.corneli@hyperreal.enterprises>
Cc: 56869@debbugs.gnu.org
Subject: bug#56869: 29.0.50; segfault, "assertion 'GDK_IS_DEVICE (device)' failed"
Date: Thu, 18 Aug 2022 10:38:06 +0800 [thread overview]
Message-ID: <874jyap981.fsf@yahoo.com> (raw)
In-Reply-To: <8735dvx9r1.fsf@Proteus> (Joe Corneli's message of "Wed, 17 Aug 2022 14:47:14 +0100")
Joe Corneli <joseph.corneli@hyperreal.enterprises> writes:
> Joe Corneli writes:
>>
>> In light of the previous, I think this is what’s needed. Details will
>> be forthcoming with the next crash!
>>
>> joe@Proteus:~$ sudo apt-get source libgtk-3-0
>
> OK, here’s the next round of backtrace. Now it includes some Lisp
> details, implicating feebleline (https://melpa.org/#/feebleline) as the
> source of the problems.
Async input can be read almost anywhere, and that includes from Lisp.
So feebleline is most likely not the problem here.
> #0 gdk_x11_device_manager_xi2_translate_event
> (xevent=<optimised out>, event=<optimised out>, display=<optimised out>, translator=<optimised out>)
> at ../../../../../gdk/x11/gdkdevicemanager-xi2.c:1794
> #1 gdk_x11_device_manager_xi2_translate_event
> (translator=<optimised out>, display=<optimised out>, event=<optimised out>, xevent=<optimised out>)
> at ../../../../../gdk/x11/gdkdevicemanager-xi2.c:1478
> #2 0x00007ffff757e989 in _gdk_x11_event_translator_translate
> (translator=translator@entry=0x55555647e400, display=0x55555645a0e0, xevent=xevent@entry=0x7ffffffe9730)
> at ../../../../../gdk/x11/gdkeventtranslator.c:51
> #3 0x00007ffff757e4cc in gdk_event_source_translate_event (xevent=0x7ffffffe9730, event_source=0x55555648b380)
> at ../../../../../gdk/x11/gdkeventsource.c:230
> #4 _gdk_x11_display_queue_events (display=0x55555645a0e0) at ../../../../../gdk/x11/gdkeventsource.c:341
> #5 0x00007ffff75460e4 in gdk_display_get_event (display=display@entry=0x55555645a0e0)
> at ../../../../gdk/gdkdisplay.c:441
> #6 0x00007ffff757e0e6 in gdk_event_source_dispatch
> (source=<optimised out>, callback=<optimised out>, user_data=<optimised out>)
> at ../../../../../gdk/x11/gdkeventsource.c:363
As I said, the line number is unfortunately not very informative, so
please type "l" to show a listing of the GDK code at that particular
line.
Thanks.
next prev parent reply other threads:[~2022-08-18 2:38 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
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 [this message]
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=874jyap981.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56869@debbugs.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).