GNU bug report logs - #70760
29.3.50; core dumps when copy in other apps

Previous Next

Package: emacs;

Reported by: Kun Liu <kun.liu <at> gmail.com>

Date: Fri, 3 May 2024 21:32:02 UTC

Severity: normal

Found in version 29.3.50

Full log


Message #101 received at 70760 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: kun.liu <at> gmail.com, 70760 <at> debbugs.gnu.org
Subject: Re: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Sat, 18 May 2024 22:20:45 +0300
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: kun.liu <at> gmail.com,  70760 <at> debbugs.gnu.org
> Date: Sat, 18 May 2024 20:22:21 +0200
> 
> > But the only place in Emacs that generates dbus-event events is
> > dbusbind.c, right?  So in that case, the first suspect is some Lisp
> > package that pushes such events onto the Emacs event queue, do you
> > agree?
> 
> I agree, the Lispy D-Bus event should be generated only in dbusbind.c.
> 
> I've checked Emacs proper (lisp/ subdirectory), GNU ELPA and NonGNU ELPA
> for the string "dbus-event". Obviously, it is contained in dbus.el. In
> helm-core.el and tramp-gvfs.el, `dbus-event' is added to
> `while-no-input-ignore-events'. In notifications.el, secrets.el,
> tramp-gvfs.el and zeroconf.el accessor funtions of the `dbus-event'
> structure are used. None of this looks strange to me.

OK, I will try to look for some way of catching these events when they
enter the input queue.




This bug report was last modified 1 year and 29 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.