GNU bug report logs - #72303
When emacs-pgtk fails to find a Wayland display available, it fails to run instead of opening in -nw mode

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 72303 in the body.
You can then email your comments to 72303 AT debbugs.gnu.org in the normal way.

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

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

From: Gunnar Wolf <gwolf <at> gwolf.org>
To: submit <at> debbugs.gnu.org
Subject: When emacs-pgtk fails to find a Wayland display available, it fails
 to run instead of opening in -nw mode
Date: Thu, 25 Jul 2024 20:37:40 -0600

Package: emacs

I have Emacs installed in all of my systems. Paricularly, I have
emacs-pgtk all systems where I often use a graphical environment (and
emacs-nox in those where I don't).

Back when I used X11, if I started Emacs and had no $DISPLAY set, it
would open in a terminal. With emacs-pgtk, the behavior is not the
same:

    $ emacs foobar

    (emacs:3988): Gtk-WARNING **: 19:19:10.887: cannot open display:
    $

This impacted me because I neede to use a remote machine to do work
via scripts (i.e. dch, debcommit) that call /usr/bin/editor and I
found impossible to hand-specify emacs to use -nw; I ended up
installing emacs-nox, but I don't find it to be an acceptable,
transparent-enough solution.

I think emacs-pgtk should behave just as emacs-gtk, falling back to
the console if a windowed environment is not found.

Thank you in advance!

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gunnar Wolf <gwolf <at> gwolf.org>, Po Lu <luangruo <at> yahoo.com>
Cc: 72303 <at> debbugs.gnu.org
Subject: Re: bug#72303: When emacs-pgtk fails to find a Wayland display
 available, it fails to run instead of opening in -nw mode
Date: Fri, 26 Jul 2024 08:48:18 +0300

> Date: Thu, 25 Jul 2024 20:37:40 -0600
> From: Gunnar Wolf <gwolf <at> gwolf.org>
> 
> Package: emacs
> 
> I have Emacs installed in all of my systems. Paricularly, I have
> emacs-pgtk all systems where I often use a graphical environment (and
> emacs-nox in those where I don't).
> 
> Back when I used X11, if I started Emacs and had no $DISPLAY set, it
> would open in a terminal. With emacs-pgtk, the behavior is not the
> same:
> 
>     $ emacs foobar
> 
>     (emacs:3988): Gtk-WARNING **: 19:19:10.887: cannot open display:
>     $
> 
> This impacted me because I neede to use a remote machine to do work
> via scripts (i.e. dch, debcommit) that call /usr/bin/editor and I
> found impossible to hand-specify emacs to use -nw; I ended up
> installing emacs-nox, but I don't find it to be an acceptable,
> transparent-enough solution.
> 
> I think emacs-pgtk should behave just as emacs-gtk, falling back to
> the console if a windowed environment is not found.

This is a known problem with the PGTK build, for which unfortunately
there's no known solution.  See bug#63555 and bug#65886.

Po Lu, it sounds like we need a PROBLEMS entry for this issue, as it
comes up very frequently.

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

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 72303 <at> debbugs.gnu.org, Gunnar Wolf <gwolf <at> gwolf.org>
Subject: Re: bug#72303: When emacs-pgtk fails to find a Wayland display
 available, it fails to run instead of opening in -nw mode
Date: Fri, 26 Jul 2024 22:19:00 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Thu, 25 Jul 2024 20:37:40 -0600
>> From: Gunnar Wolf <gwolf <at> gwolf.org>
>> 
>> Package: emacs
>> 
>> I have Emacs installed in all of my systems. Paricularly, I have
>> emacs-pgtk all systems where I often use a graphical environment (and
>> emacs-nox in those where I don't).
>> 
>> Back when I used X11, if I started Emacs and had no $DISPLAY set, it
>> would open in a terminal. With emacs-pgtk, the behavior is not the
>> same:
>> 
>>     $ emacs foobar
>> 
>>     (emacs:3988): Gtk-WARNING **: 19:19:10.887: cannot open display:
>>     $
>> 
>> This impacted me because I neede to use a remote machine to do work
>> via scripts (i.e. dch, debcommit) that call /usr/bin/editor and I
>> found impossible to hand-specify emacs to use -nw; I ended up
>> installing emacs-nox, but I don't find it to be an acceptable,
>> transparent-enough solution.
>> 
>> I think emacs-pgtk should behave just as emacs-gtk, falling back to
>> the console if a windowed environment is not found.
>
> This is a known problem with the PGTK build, for which unfortunately
> there's no known solution.  See bug#63555 and bug#65886.
>
> Po Lu, it sounds like we need a PROBLEMS entry for this issue, as it
> comes up very frequently.

Now taken care of, thanks.

Message #16 received at 72303-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: gwolf <at> gwolf.org, luangruo <at> yahoo.com
Cc: 72303-done <at> debbugs.gnu.org
Subject: Re: bug#72303: When emacs-pgtk fails to find a Wayland display
 available, it fails to run instead of opening in -nw mode
Date: Sun, 04 Aug 2024 11:17:03 +0300

> Cc: 72303 <at> debbugs.gnu.org
> Date: Fri, 26 Jul 2024 08:48:18 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Date: Thu, 25 Jul 2024 20:37:40 -0600
> > From: Gunnar Wolf <gwolf <at> gwolf.org>
> > 
> > Package: emacs
> > 
> > I have Emacs installed in all of my systems. Paricularly, I have
> > emacs-pgtk all systems where I often use a graphical environment (and
> > emacs-nox in those where I don't).
> > 
> > Back when I used X11, if I started Emacs and had no $DISPLAY set, it
> > would open in a terminal. With emacs-pgtk, the behavior is not the
> > same:
> > 
> >     $ emacs foobar
> > 
> >     (emacs:3988): Gtk-WARNING **: 19:19:10.887: cannot open display:
> >     $
> > 
> > This impacted me because I neede to use a remote machine to do work
> > via scripts (i.e. dch, debcommit) that call /usr/bin/editor and I
> > found impossible to hand-specify emacs to use -nw; I ended up
> > installing emacs-nox, but I don't find it to be an acceptable,
> > transparent-enough solution.
> > 
> > I think emacs-pgtk should behave just as emacs-gtk, falling back to
> > the console if a windowed environment is not found.
> 
> This is a known problem with the PGTK build, for which unfortunately
> there's no known solution.  See bug#63555 and bug#65886.
> 
> Po Lu, it sounds like we need a PROBLEMS entry for this issue, as it
> comes up very frequently.

With the PROBLEMS entry now added, I'm closing this bug.

Previous Next

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