GNU bug report logs - #5386
gtk daemon close display hang

Previous Next

Package: emacs;

Reported by: Dirk-Jan C. Binnema <djcb <at> djcbsoftware.nl>

Date: Fri, 15 Jan 2010 07:26:01 UTC

Severity: normal

Merged with 3360, 39222

Found in version 24.5

Full log


View this message in rfc822 format

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: "Dirk-Jan C. Binnema" <djcb <at> djcbsoftware.nl>, 5386 <at> debbugs.gnu.org
Subject: bug#5386: 23.1.91;
Date: Fri, 15 Jan 2010 11:31:34 -0800 (PST)
Chong Yidong <cyd <at> stupidchicken.com> writes:

  > Dan Nicolaescu <dann <at> ics.uci.edu> writes:
  > 
  > > That is fine, it's just a warning.
  > > And it has the added benefit that users are aware of what might go on,
  > > and it also adds a bit of pressure on the Gtk people to fix the bug.
  > 
  > How about issuing a warning when a new GTK frame is created?

When?
Every time a GTK frame is created?
That would be very annoying.

After we've had a disconnect?  I don't think there's a way to detect
that situation reliably.

Having the warning issued when starting emacs --daemon has the advantage
that it's only done once per session.  Sure, it does not cover all cases
(you still run into trouble by doing emacs -nw -f server-start then
create a GTK frame), but it does cover the most frequent use-case.






This bug report was last modified 5 years and 144 days ago.

Previous Next


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