From: Kun Liu <kun.liu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 70760@debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Sun, 5 May 2024 10:11:46 -0700 [thread overview]
Message-ID: <CA+Nei8OWaoVWf3LfYzcZekxKq=EAA2MavhHEiV-=NJcgpKtYqA@mail.gmail.com> (raw)
In-Reply-To: <CA+Nei8PUxSLmSisCGvx4NOTGiGSuAZCK7YpgGwKEZ-JgF8-+Tg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]
Scratch that. Just now I was able to see the following error in Emacs
without any shell buffer, while copying in Chome:
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
dbus-handle-event((dbus-event (if above 1 2)))
funcall-interactively(dbus-handle-event (dbus-event (if above 1 2)))
command-execute(dbus-handle-event nil [(dbus-event (if above 1 2))] t)
On Sun, May 5, 2024 at 9:44 AM Kun Liu <kun.liu@gmail.com> wrote:
> I am not sure how VirtualBox deals with Ctrl-C on the Windows side. I
> will look into it when I have time.
>
> I did more tests. Observations:
>
> 1) It *appears* that the problem is there only when I have a shell buffer
> (M-x shell). I will do more tests and report back.
>
> 2) The error messages seem to vary. For example, I saw the following two
> different ones when copying:
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> dbus-handle-event((dbus-event (calendar-cursor-holidays
> (calendar-current-date))))
> funcall-interactively(dbus-handle-event (dbus-event
> (calendar-cursor-holidays (calendar-current-date))))
> command-execute(dbus-handle-event nil [(dbus-event
> (calendar-cursor-holidays (calendar-current-date)))] t)
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> dbus-handle-event((dbus-event (if above 1 2)))
> funcall-interactively(dbus-handle-event (dbus-event (if above 1 2)))
> command-execute(dbus-handle-event nil [(dbus-event (if above 1 2))] t)
>
> On Sun, May 5, 2024 at 9:12 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
>> > From: Kun Liu <kun.liu@gmail.com>
>> > Date: Sun, 5 May 2024 08:45:34 -0700
>> > Cc: 70760@debbugs.gnu.org
>> >
>> > I did (setq debug-on-error t), went to
>> https://en.wikipedia.org/wiki/Emacs, randomly selected a fragment
>> > "Emacs has over", then did a ctrll+c.
>> >
>> > Emacs in VirtualBox immediately showed the following:
>> >
>> > Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p
>> nil)
>> > dbus-handle-event((dbus-event "[ \11]*$"))
>> > funcall-interactively(dbus-handle-event (dbus-event "[ \11]*$"))
>> > call-interactively(dbus-handle-event nil [(dbus-event "[ \11]*$")])
>> > command-execute(dbus-handle-event nil [(dbus-event "[ \11]*$")] t)
>>
>> Does VirtualBox have anything in its documentation that suggests that
>> Ctrl-C on the Windows side will cause a D-Bus event on the VM side?
>>
>> Michael, any idea what is this D-Bus event, and what does it have to
>> do with copying into the Windows clipboard?
>>
>> Thanks.
>>
>
[-- Attachment #2: Type: text/html, Size: 3617 bytes --]
next prev parent reply other threads:[~2024-05-05 17:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 21:30 bug#70760: 29.3.50; core dumps when copy in other apps Kun Liu
2024-05-04 7:11 ` Eli Zaretskii
2024-05-04 18:08 ` Kun Liu
2024-05-04 19:02 ` Eli Zaretskii
[not found] ` <CA+Nei8PsdEL-bOOQg86aZk1n1ahpb38XUokyHR98muaRTUY+5Q@mail.gmail.com>
2024-05-04 21:37 ` Kun Liu
2024-05-05 5:11 ` Eli Zaretskii
2024-05-05 15:45 ` Kun Liu
2024-05-05 16:12 ` Eli Zaretskii
2024-05-05 16:44 ` Kun Liu
2024-05-05 17:11 ` Kun Liu [this message]
2024-05-05 17:34 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 6:17 ` Kun Liu
2024-05-14 7:13 ` Eli Zaretskii
2024-05-15 10:35 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 16:27 ` Kun Liu
2024-05-15 17:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 18:25 ` Kun Liu
2024-05-15 21:06 ` Kun Liu
2024-05-16 9:20 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 19:07 ` Kun Liu
2024-05-17 16:23 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 17:34 ` Eli Zaretskii
2024-05-17 20:43 ` Kun Liu
2024-05-18 0:34 ` Kun Liu
2024-05-18 10:32 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 11:44 ` Eli Zaretskii
2024-05-18 11:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 12:09 ` Eli Zaretskii
2024-05-18 16:55 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 17:54 ` Eli Zaretskii
2024-05-18 18:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 19:20 ` Eli Zaretskii
2024-05-16 9:07 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CA+Nei8OWaoVWf3LfYzcZekxKq=EAA2MavhHEiV-=NJcgpKtYqA@mail.gmail.com' \
--to=kun.liu@gmail.com \
--cc=70760@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/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).