unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Sven Joachim <svenjoac@gmx.de>
Cc: 3145@emacsbugs.donarmstrong.com, cyd@stupidchicken.com,
	Stephen Berman <stephen.berman@gmx.net>,
	rms@gnu.org
Subject: bug#3145: 23.0.92; detaching GTK+ tool bar crashes emacs --daemon
Date: Wed, 05 Aug 2009 11:41:09 +0200	[thread overview]
Message-ID: <4A7953B5.5060201@swipnet.se> (raw)
In-Reply-To: <87tz0n9yb7.fsf@turtle.gmx.de>

Sven Joachim skrev:
> On 2009-05-04 22:17 +0200, Jan Djärv wrote:
> 
>> Richard M Stallman skrev:
>>> It would be useful to make Emacs detect this case and give a clean
>>> error message such as "Due to GTK+ bug number XYZ, what you want to do
>>> is impossible", rather than just crashing.
>> The good news is that the bug has been marked as FIXED.  But I don't
>> know in which Gtk+ version the fix will appear in.  The only way to
>> detect this particular bug is by checking version numbers.
> 
> For the record, I see the following in
> /usr/share/doc/libgtk2.0-common/changelog.gz:
> 
> ,----
> | commit 00524901e1393618e469dd9a8f224401b8ba7e35
> | Author: Matthias Clasen <mclasen@redhat.com>
> | Date:   Sun May 3 22:27:12 2009 -0400
> | 
> |     Make GtkHandleBox work on multiple displays
> | 
> |  gtk/gtkhandlebox.c |    1 +
> |  1 files changed, 1 insertions(+), 0 deletions(-)
> `----
> 
> This is included in GTK+ 2.16.2, but the recipe to crash Emacs from the
> original report still works in
> GNU Emacs 23.1.50.4 (x86_64-unknown-linux-gnu, GTK+ Version 2.16.5)
> of 2009-08-04 on turtle .
> 
> Note that this recipe does not even involve multiple displays.
> 

You are correct, the fix in Gtk+ is no good, it is obvious that they didn't 
test the fix.
I've reopened the Gtk+ bug for this with new information:
http://bugzilla.gnome.org/show_bug.cgi?id=581110


Hopefully a better fix will come.

	Jan D.





  reply	other threads:[~2009-08-05  9:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  1:05 bug#3145: 23.0.92; detaching GTK+ tool bar crashes emacs --daemon Chong Yidong
2009-04-30  7:57 ` Jan Djärv
2009-05-02 16:51   ` Jan Djärv
2009-05-02 17:10     ` Chong Yidong
2009-05-02 23:35     ` Stephen Berman
2009-05-03 17:19       ` Jan Djärv
2009-05-03 18:24         ` Dan Nicolaescu
2009-05-03 20:25           ` Chong Yidong
2009-05-03 21:30       ` Richard M Stallman
2009-05-04 20:17         ` Jan Djärv
2009-08-04 19:25           ` Sven Joachim
2009-08-05  9:41             ` Jan Djärv [this message]
2011-09-16 20:34               ` Lars Magne Ingebrigtsen
2011-09-16 22:29                 ` Jan Djärv
2016-04-10 22:40                 ` Alan Third
2016-04-11  8:28                   ` Stephen Berman
  -- strict thread matches above, loose matches on Subject: below --
2009-04-28 14:41 Stephen Berman
2009-04-28 15:26 ` Stephen Berman

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=4A7953B5.5060201@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=3145@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=rms@gnu.org \
    --cc=stephen.berman@gmx.net \
    --cc=svenjoac@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).