all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kun Liu <kun.liu@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 70760@debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Mon, 13 May 2024 23:17:16 -0700	[thread overview]
Message-ID: <CA+Nei8PR3Pb4xQ_pvDYoCLNtS1iXB_YNbfj4rcAHbn+X61+yyQ@mail.gmail.com> (raw)
In-Reply-To: <87cyq0tb5w.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]

I tried various things including upgrading the guest Linux to Debian 12,
and trying master vs 29 branches. Still seeing crashes.

Today I tried configure emacs 29 without "--with-native-compilation". It
appears that core dump is no longer happening. Now when I copy on the host,
I see the following message in Emacs:

dbus-check-event: D-Bus error: "Not a valid D-Bus event", (dbus-event 10 14)

Backtrace buffer shows the following:

Debugger entered--Lisp error: (dbus-error "Not a valid D-Bus event"
(dbus-event 10 14))
  signal(dbus-error ("Not a valid D-Bus event" (dbus-event 10 14)))
  dbus-check-event((dbus-event 10 14))
  dbus-event-bus-name((dbus-event 10 14))
  dbus-notice-synchronous-call-errors((dbus-event 10 14) (dbus-error "Not a
valid D-Bus event" (dbus-event 10 14)))
  run-hook-with-args(dbus-notice-synchronous-call-errors (dbus-event 10 14)
(dbus-error "Not a valid D-Bus event" (dbus-event 10 14)))
  dbus-handle-event((dbus-event 10 14))
  funcall-interactively(dbus-handle-event (dbus-event 10 14))
  call-interactively(dbus-handle-event nil [(dbus-event 10 14)])
  command-execute(dbus-handle-event nil [(dbus-event 10 14)] t)

On Sun, May 5, 2024 at 10:34 AM Michael Albinus <michael.albinus@gmx.de>
wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi Eli,
>
> >> 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?
>
> `dbus-handle-event' is the handler for D-Bus events (sic!). It is
> invoked, when a D-Bus event arrives in the keyboard buffer, see
> `special-event-map'.
>
> It isn't called explicitly anywhere in Emacs. So I assume that the
> "D-Bus" event is pushed to the keyboard buffer by accident, when
> communicating with the VirtualBox.
>
> > Thanks.
>
> Best regards, Michael.
>

[-- Attachment #2: Type: text/html, Size: 3398 bytes --]

  reply	other threads:[~2024-05-14  6:17 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+Nei8PR3Pb4xQ_pvDYoCLNtS1iXB_YNbfj4rcAHbn+X61+yyQ@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.