unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Thompson <robt105@yahoo.com>
Cc: 70930@debbugs.gnu.org
Subject: bug#70930: 29.3; emacs gives warning on startup
Date: Tue, 14 May 2024 09:31:02 +0300	[thread overview]
Message-ID: <86r0e4x5uh.fsf@gnu.org> (raw)
In-Reply-To: <1109877993.98251.1715639264331@mail.yahoo.com> (bug-gnu-emacs@gnu.org)

> Date: Mon, 13 May 2024 22:27:44 +0000 (UTC)
> From:  Robert Thompson via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Starting 'emacs', even 'emacs -Q', from the command line (eg a Terminal session) now gives
> the following warning:
> You are trying to run Emacs configured with the
> "pure-GTK" interface under the X Windows System. That confituration is
> unsupported and will lead to sporadic crashes during transfer of large
> selection data. It will also lead to various problems with keyboard
> input.
> Install emacs-gtk+x11 or emacs-lucid package.
> 
> But the packages are already installed:
> $ sudo dnf install emacs-lucid
> Fedora Core 40 - x86_64 - ATrpms                              0.0  B/s |   0  B     00:00    
> Error: Failed to download metadata for repo 'atrpms': repomd.xml parser error: Parse error at line: 1
> (Document is empty
> )
> Ignoring repositories: atrpms
> Last metadata expiration check: 2:39:08 ago on Mon 13 May 2024 12:32:09 PM PDT.
> Package emacs-lucid-1:29.3-6.fc40.x86_64 is already installed.
> Dependencies resolved.
> Nothing to do.
> Complete!
> $ sudo dnf install emacs-gtk+x11
> Fedora Core 40 - x86_64 - ATrpms                              0.0  B/s |   0  B     00:00    
> Error: Failed to download metadata for repo 'atrpms': repomd.xml parser error: Parse error at line: 1
> (Document is empty
> )
> Ignoring repositories: atrpms
> Last metadata expiration check: 2:40:57 ago on Mon 13 May 2024 12:32:09 PM PDT.
> Package emacs-gtk+x11-1:29.3-6.fc40.x86_64 is already installed.
> Dependencies resolved.
> Nothing to do.
> Complete!
> 
> This started after I upgraded to Fedora Linus 40 (Workstation Edition)
> Linux alfie 6.7.10-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Mar 18 18:56:52 UTC 2024 x86_64
> GNU/Linux
> 
> Help?

I think you should raise this issue with the maintainers of the Fedora
distro.  We here don't know how Fedora organizes the packaging of the
various variants of Emacs it distributes.

Thanks.





  reply	other threads:[~2024-05-14  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1109877993.98251.1715639264331.ref@mail.yahoo.com>
2024-05-13 22:27 ` bug#70930: 29.3; emacs gives warning on startup Robert Thompson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14  6:31   ` Eli Zaretskii [this message]
2024-05-14 12:54   ` Dave Marquardt

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=86r0e4x5uh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70930@debbugs.gnu.org \
    --cc=robt105@yahoo.com \
    /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).