Bug 2273957 - Wayland Emacs is launched from X11 Xfce
Summary: Wayland Emacs is launched from X11 Xfce
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Oliver
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-08 10:55 UTC by Peter Oliver
Modified: 2024-04-19 21:33 UTC (History)
10 users (show)

Fixed In Version: emacs-29.3-5.fc40
Clone Of:
Environment:
Last Closed: 2024-04-19 21:33:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Oliver 2024-04-08 10:55:16 UTC
At https://bodhi.fedoraproject.org/updates/FEDORA-2024-7985b5f326#comment-3479986, nixuser reports:

> I get a warning running emacs from the launch icon, basically telling me to install and run emacs-gtk+x11 or emacs-lucid instead. emacs-gtk+x11 is already installed. If I run it manually I don't get the warning. Looks like the icon launches the program /usr/bin/emacs-desktop, is that supposed to work out what to actually run? If so under Xfce it's picking the wrong one.

Reproducible: Always

Comment 1 Peter Oliver 2024-04-08 10:58:57 UTC
nixuser: Could you run the following command and share the output?  Thanks.

sh -x emacs-desktop

Comment 2 Ian Laurie 2024-04-08 21:01:47 UTC
$ sh -x emacs-desktop
+ '[' x11 = x11 ']'
++ readlink -f /usr/bin/emacs
+ emacs=/usr/bin/emacs-29.2-gtk+x11
+ emacs=emacs-29.2-gtk+x11
+ emacs=emacs-29.2-gtk+x11
+ '[' emacs-29.2-gtk+x11 = emacs ']'
+ exec emacs



Recall though I fixed the issue by uninstalling emacs and explicitly installing emacs-gtk+x11 then uninstalling emacs again.

Do you need me to revert to the failing condition and re-run?

Comment 3 Ian Laurie 2024-04-08 23:33:08 UTC
OK I installed emacs on another native Fedora 40 system with Xfce.  I installed using this syntax:

$ sudo dnf -y install emacs

this launches with the problem warning message because it is launching the wrong binary.  On this system:

$ emacs
zuke$ sh -x emacs-desktop
+ '[' x11 = x11 ']'
++ readlink -f /usr/bin/emacs
+ emacs=/usr/bin/emacs-29.2
+ emacs=emacs-29.2
+ emacs=emacs-29.2
+ '[' emacs-29.2 = emacs ']'
+ exec emacs

Note that during the install emacs-gtk+x11 was also installed as a weak dependency, but it doesn't look like it's getting used.

I'll leave this system like this in case you need me to do/try something else.

Comment 4 Ian Laurie 2024-04-09 02:33:01 UTC
Upgraded the second system to emacs-29.3-2.fc40.x86_64.  Same results.

$ sh -x emacs-desktop
+ '[' x11 = x11 ']'
++ readlink -f /usr/bin/emacs
+ emacs=/usr/bin/emacs-29.3
+ emacs=emacs-29.3
+ emacs=emacs-29.3
+ '[' emacs-29.3 = emacs ']'
+ exec emacs

Comment 5 Fedora Update System 2024-04-09 16:10:38 UTC
FEDORA-2024-f9ce536a3e (emacs-29.3-5.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f9ce536a3e

Comment 6 Fedora Update System 2024-04-09 18:23:06 UTC
FEDORA-2024-f9ce536a3e has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-f9ce536a3e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f9ce536a3e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Ian Laurie 2024-04-09 23:09:19 UTC
emacs-29.3-5.fc40 fixes the issue for me.

$ sh -x emacs-desktop
+ '[' x11 = x11 ']'
++ readlink -f /usr/bin/emacs
+ emacs=/usr/bin/emacs-29.3
+ emacs=emacs-29.3
+ emacs=emacs
+ '[' emacs = emacs ']'
+ type emacs-gtk+x11
+ exec emacs-gtk+x11

Comment 8 Fedora Update System 2024-04-19 21:33:21 UTC
FEDORA-2024-f9ce536a3e (emacs-29.3-5.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.