From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: tfs@maithean.com
Newsgroups: gmane.emacs.bugs
Subject: Re: bug#2709: emacs doesn't start
Date: Wed, 25 Mar 2009 08:37:07 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <48c4696b-598b-47d7-a1dc-b20e64e3098f@x29g2000prf.googlegroups.com>
References: <000e01c9a7dc$8cfb8f70$112eff17@homea311f4d782> 
	<mailman.3656.1237575832.31690.bug-gnu-emacs@gnu.org>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: ger.gmane.org 1238057871 15958 80.91.229.12 (26 Mar 2009 08:57:51 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Thu, 26 Mar 2009 08:57:51 +0000 (UTC)
To: bug-gnu-emacs@gnu.org
Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Mar 26 09:59:08 2009
Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org>
Envelope-to: geb-bug-gnu-emacs@m.gmane.org
Original-Received: from lists.gnu.org ([199.232.76.165])
	by lo.gmane.org with esmtp (Exim 4.50)
	id 1LmlQS-0001MF-NK
	for geb-bug-gnu-emacs@m.gmane.org; Thu, 26 Mar 2009 09:59:00 +0100
Original-Received: from localhost ([127.0.0.1]:57153 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1LmlP5-0007oi-SI
	for geb-bug-gnu-emacs@m.gmane.org; Thu, 26 Mar 2009 04:57:35 -0400
Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!x29g2000prf.googlegroups.com!not-for-mail
Original-Newsgroups: gnu.emacs.bug
Original-Lines: 40
Original-NNTP-Posting-Host: 68.127.155.54
Original-X-Trace: posting.google.com 1237995427 15266 127.0.0.1 (25 Mar 2009 15:37:07
	GMT)
Original-X-Complaints-To: groups-abuse@google.com
Original-NNTP-Posting-Date: Wed, 25 Mar 2009 15:37:07 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: x29g2000prf.googlegroups.com; posting-host=68.127.155.54; 
	posting-account=dV9MrQoAAACvovWPCMLsgi6y8kK238ZS
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) 
	Gecko/2009030503 Fedora/3.0.7-1.fc10 Firefox/3.0.7, gzip(gfe), gzip(gfe)
Original-Xref: news.stanford.edu gnu.emacs.bug:54483
X-Mailman-Approved-At: Thu, 26 Mar 2009 04:51:02 -0400
X-BeenThere: bug-gnu-emacs@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Bug reports for GNU Emacs,
	the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>,
	<mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-gnu-emacs>
List-Post: <mailto:bug-gnu-emacs@gnu.org>
List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>,
	<mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe>
Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org
Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org
Xref: news.gmane.org gmane.emacs.bugs:26631
Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/26631>

On Mar 20, 11:50=A0am, Glenn Morris <r...@gnu.org> wrote:
> "Umberto Coletta" wrote:
> > Suddenly, after a Fedora 10 software update,emacs22doesn'tstart.
> > 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 -qemacs' say?
>
> What does `whichemacs' say?
>
> Does `/usr/bin/emacs-Q' work?
>
> (You may have more luck on a Fedora list.)

I am experiencing the same problem.  The emacs process starts and
hangs -- I think during window system initialization. I tried
uninstalling and re-installing with the same result.  The following is
version information:

$ rpm -q emacs
emacs-22.3-4.fc10.i386

$ which emacs
/usr/bin/emacs

$ file /usr/bin/emacs
/usr/bin/emacs: symbolic link to `/etc/alternatives/emacs'

$ file /etc/alternatives/emacs
/etc/alternatives/emacs: symbolic link to `/usr/bin/emacs-22.3'

$ emacs --no-window-system

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