From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: grokking Stuff <grokkingstuff@gmail.com>, 57417@debbugs.gnu.org
Subject: bug#57417: Emacs crashes due to symbol lookup error to rsvg_handle_set_stylesheet
Date: Fri, 26 Aug 2022 17:41:35 +0200 [thread overview]
Message-ID: <a02be1face44d39c89feb7e458a3e3406da7ba2d.camel@gmail.com> (raw)
In-Reply-To: <173C51E9-89F7-49D2-98E3-19C515FD406E@gmail.com>
Am Donnerstag, dem 25.08.2022 um 23:12 +0400 schrieb grokking Stuff:
> Hey fellow Guix users,
>
> I’m trying to use Emacs on my system but it tends to crash
> unexpectedly.
>
> When launching it from a terminal, I get:
>
> > grokkingstuff@grokkingNoether ~$ emacs
> > (process:32402): Gtk-WARNING **: 22:59:14.455: Locale not supported
> > by C library.
> > Using the fallback 'C' locale.
> > /home/grokkingstuff/.guix-profile/bin/emacs: symbol lookup error:
> > /home/grokkingstuff/.guix-profile/bin/emacs: undefined symbol:
> > rsvg_handle_set_stylesheet
Looking at this output, it seems Emacs is trying to dynamically link
librsvg. Two issues spring to mind: First, this kind of linkage is not
that well supported by Guix, so we tend to substitute* the full path.
Is this done for librsvg? Second, there might be a (version) mismatch
between the librsvg Emacs expects and the one it gets. Does
rsvg_handle_set_stylesheet actually exist as a symbol in your librsvg?
Cheers
next prev parent reply other threads:[~2022-08-26 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 19:12 bug#57417: Emacs crashes due to symbol lookup error to rsvg_handle_set_stylesheet grokking Stuff
2022-08-26 15:41 ` Liliana Marie Prikler [this message]
[not found] ` <588215250.356998251.1668103819659.JavaMail.root@zimbra81-e14.priv.proxad.net>
2022-11-10 18:13 ` arnaud.lechevallier
2022-11-10 22:31 ` Maxime Devos
2022-11-11 7:56 ` arnaud.lechevallier
2022-11-11 16:00 ` Maxime Devos
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a02be1face44d39c89feb7e458a3e3406da7ba2d.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=57417@debbugs.gnu.org \
--cc=grokkingstuff@gmail.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/guix.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).