unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: William Lightner <William.Lightner@jbhunt.com>
Cc: 64500@debbugs.gnu.org
Subject: bug#64500: More information
Date: Thu, 20 Jul 2023 09:29:04 +0300	[thread overview]
Message-ID: <83351j3xlb.fsf@gnu.org> (raw)
In-Reply-To: <SN6PR1901MB2029A127176E0064478962CFE839A@SN6PR1901MB2029.namprd19.prod.outlook.com> (bug-gnu-emacs@gnu.org)

> Date: Wed, 19 Jul 2023 21:57:21 +0000
> From:  William Lightner via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I removed emacs again; discovered I’d also installed it under choco & removed that, too, then
> re-installed 28.2 using the Windows installer.
> 
> Still get this problem, apparently during compiling…?

Why does Emacs compile *.el files?  It isn't supposed to that when you
start it.

Anyway, I'm sorry to say that I don't understand what happens in your
case according to what you describe.  The GIO error message you show
in the original report seem to point to librsvg, but that is all I can
say.  The backtraces you post can only be interpreted on your system;
see the node "Crashing" in the Emacs user manual for how to convert
them to more useful ones if you have the necessary tools installed.

That's all I can say, sorry.  These Emacs versions work flawlessly for
me, FWIW.





  parent reply	other threads:[~2023-07-20  6:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 17:58 bug#64500: 28.2; Windows 10 errors version 28.* (including 28.2) William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-19 21:57 ` bug#64500: More information William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-19 22:25   ` William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20  6:29   ` Eli Zaretskii [this message]
2023-07-20 14:12     ` William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 14:23       ` William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 14:29         ` Eli Zaretskii
2023-07-20 15:02           ` William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 15:33             ` Eli Zaretskii
2023-07-20 16:41               ` William Lightner via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83351j3xlb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64500@debbugs.gnu.org \
    --cc=William.Lightner@jbhunt.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).