GNU bug report logs - #2709
emacs doesn't start

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 2709 in the body.
You can then email your comments to 2709 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Umberto Coletta" <umberto.coletta <at> fastwebnet.it>
To: <bug-gnu-emacs <at> gnu.org>
Subject: emacs doesn't start
Date: Wed, 18 Mar 2009 16:16:45 +0100

[Message part 1 (text/plain, inline)]

Hi!
Suddenly, after a Fedora 10 software update, emacs 22 doesn't start.
Can you help me?
Thanks
Bye
Umberto

[Message part 2 (text/html, inline)]

Message #10 received at 2709 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Umberto Coletta <umberto.coletta <at> fastwebnet.it>
Cc: 2709 <at> debbugs.gnu.org
Subject: Re: bug#2709: emacs doesn't start
Date: Fri, 20 Mar 2009 14:50:17 -0400

"Umberto Coletta" wrote:

> Suddenly, after a Fedora 10 software update, emacs 22 doesn't start.
> Can you help me?

This is pretty much the textbook definition of a bad bug report.

What exactly did you try? What exactly happened?

What does `rpm -q emacs' say?

What does `which emacs' say?

Does `/usr/bin/emacs -Q' work?

(You may have more luck on a Fedora list.)

Message #13 received at 2709 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 2709 <at> debbugs.gnu.org
Subject: Re: bug#2709: emacs doesn't start
Date: Thu, 26 Mar 2009 13:42:14 -0400

[ The message to which I am replying does not appear in the Emacs bug
tracker due to bug #936. I'm not resending things any more. ]

tfs <at> maithean.com wrote:

> works fine within a terminal window.  This is why I think it has to do
> with window system interaction.

https://bugzilla.redhat.com/show_bug.cgi?id=491813
https://bugzilla.redhat.com/show_bug.cgi?id=491979

This appears to be an issue with libX11 in Fedora, affecting several
applications, and possibly fixed by the latest Fedora libX11.

Previous Next

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