From: "Zhu Zihao" <all_but_last@163.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 41627@debbugs.gnu.org
Subject: bug#41627: Re: bug#41627: 28.0.50; Emacs with cairo build segfault in HELLO file
Date: Tue, 23 Jun 2020 12:10:54 +0800 (CST) [thread overview]
Message-ID: <10b018c2.445d.172df5f27d3.Coremail.all_but_last@163.com> (raw)
In-Reply-To: <83mu4vt1ou.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
But it's sad that I can't reproduce that bug in NixOS :(
At 2020-06-23 02:06:41, "Eli Zaretskii" <eliz@gnu.org> wrote:
>> Date: Tue, 23 Jun 2020 00:47:30 +0800 (CST)
>> From: "Zhu Zihao" <all_but_last@163.com>
>> Cc: eliz@gnu.org
>>
>> I'm able to reproduce this bug in NixOS 20.03 with Emacs 27.0.91 pretest version. I guess this bug is
>> caused by the mechanism of Nix/Guix. NixOS doesn't have FHS directory structure, it means that there's
>> nothing like /usr/share/fonts for Cairo to search fonts. And I try to copy some fonts to ~/.local/share/fonts
>> then Emacs won't crash again.
>
>If you can show a backtrace from the crash, perhaps we could find the
>reason and fix it.
>
>Thanks.
[-- Attachment #2: Type: text/html, Size: 1185 bytes --]
prev parent reply other threads:[~2020-06-23 4:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 11:32 bug#41627: 28.0.50; Emacs with cairo build segfault in HELLO file Zihao Zhu
2020-05-31 12:35 ` Pip Cet
2020-05-31 14:27 ` Zihao Zhu
2020-05-31 14:34 ` Pip Cet
2020-05-31 14:31 ` Zihao Zhu
2020-05-31 14:54 ` Eli Zaretskii
2020-05-31 15:38 ` Zihao Zhu
2020-05-31 17:24 ` Eli Zaretskii
2020-05-31 20:45 ` Pip Cet
2020-06-01 16:35 ` Eli Zaretskii
2020-06-01 18:02 ` Pip Cet
2020-09-27 14:29 ` Lars Ingebrigtsen
2020-10-21 15:58 ` Robert Pluim
2020-10-22 11:41 ` Lars Ingebrigtsen
2020-10-22 12:03 ` Zhu Zihao
2020-10-22 12:43 ` Lars Ingebrigtsen
2020-06-22 16:47 ` Zhu Zihao
2020-06-22 18:06 ` Eli Zaretskii
2020-06-23 4:10 ` Zhu Zihao [this message]
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=10b018c2.445d.172df5f27d3.Coremail.all_but_last@163.com \
--to=all_but_last@163.com \
--cc=41627@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).