From: Bradley Haggerty <bradigger@gmail.com>
To: 34454@debbugs.gnu.org
Subject: bug#34454: GTK programs segfaulting
Date: Thu, 14 Mar 2019 04:19:31 +0000 [thread overview]
Message-ID: <CABGw91fTMSYz1Lhp-HOvaGGC-ZLAU9A6Y4BsLyrW3fOuBxmJqA@mail.gmail.com> (raw)
In-Reply-To: <20190212041627.31de67cb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Ludovic Courtès said:
> Could you then see if this can be reproduced in a VM? That is, run:
> guix system vm config.scm
> where config.scm is your system config, with Emacs added
I've started on this process but it's new to me so I'm a bit lost here.
I added emacs to the package list of my existing real config.scm, the one
at /etc/config.scm, then ran the guix system vm command on it. I read up a
bit
on what the command does, and I *think* I've now created a qemu-compatible
image that I now have to boot with qemu and it should be like my exact
system
minus user profile packages. I've never used qemu so I'm a bit intimidated
there,
but I plan to try to figure this out soon.
[-- Attachment #2: Type: text/html, Size: 911 bytes --]
next prev parent reply other threads:[~2019-03-14 4:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 10:16 bug#34454: After an update, icecat now segfaults very quickly after opening Bradley Haggerty
2019-02-12 10:31 ` bug#34454: (no subject) Bradley Haggerty
2019-02-15 18:28 ` bug#34454: Icecat crashes after several seconds Bradley Haggerty
2019-03-09 23:37 ` bug#34454: GTK programs segfaulting Bradley Haggerty
2019-03-10 17:45 ` Ludovic Courtès
2019-03-11 3:07 ` Bradley Haggerty
2019-03-12 13:11 ` Ludovic Courtès
2019-03-11 3:09 ` Bradley Haggerty
2019-03-14 4:19 ` Bradley Haggerty [this message]
2019-03-30 4:22 ` bug#34454: Gtk upstream bug #1280 causes crashes in IceCat and Emacs Mark H Weaver
2019-03-31 8:52 ` Bradley Haggerty
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=CABGw91fTMSYz1Lhp-HOvaGGC-ZLAU9A6Y4BsLyrW3fOuBxmJqA@mail.gmail.com \
--to=bradigger@gmail.com \
--cc=34454@debbugs.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/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).