From: Leo Famulari <leo@famulari.name>
To: Catonano <catonano@gmail.com>
Cc: 27264@debbugs.gnu.org
Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Date: Thu, 8 Jun 2017 13:45:41 -0400 [thread overview]
Message-ID: <20170608174541.GA2313@jasmine> (raw)
In-Reply-To: <CAJ98PDx7jnf1Wdfst4FqB3zr62GAiNXco_7OBtTHLbapK25EOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Thu, Jun 08, 2017 at 07:29:06PM +0200, Catonano wrote:
> I'd love to help with testing the Gnome desktop
>
> The reason why I abstain is because if the desktop environment turns out to
> be broken, like in this case, I wouldn't know how to work around that
In general, you can always do a hard reboot and select an earlier GuixSD
generation from the GRUB menu if something goes wrong. It's not great to
do a hard reboot, but contemporary filesystems like ext4 tend to handle
it well enough.
> I'm lost in the command line, I'm not even sure I could manage to access
> the so called consoles or that I could open an alternative desktop
> environment
>
> If I had a spare computer I would use that.
>
> Unless using a qemu based virtual machine is a good enough solution
>
> If it is, then here I am
I think QEMU is a fine test environment for GNOME as long as you can use
the Kernel-based Virtual Machine in QEMU, which allows the VM to run at
near-native speed. When starting QEMU you'd pass '-enable-kvm'. Older
hardware may not offer KVM, unfortunately.
> Send me an email, indicate me a branch and I'll test it
Thanks, I'll keep you in mind :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-08 17:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 4:59 bug#27264: gnome-shell-3.24.2 consistently dies during initialization Mark H Weaver
2017-06-07 10:37 ` Ludovic Courtès
2017-06-07 13:15 ` Roel Janssen
2017-06-07 21:58 ` Mark H Weaver
2017-06-08 6:03 ` Marius Bakke
2017-06-08 6:29 ` Mark H Weaver
2017-06-08 12:35 ` Kei Kebreau
2017-06-08 16:13 ` Marius Bakke
2017-06-08 16:29 ` Marius Bakke
2017-06-09 6:23 ` Chris Marusich
2017-06-09 7:02 ` Mark H Weaver
2017-06-08 7:39 ` Ben Sturmfels
2017-06-08 6:48 ` pelzflorian (Florian Pelz)
2017-06-08 12:01 ` Ludovic Courtès
2017-06-08 12:23 ` Kei Kebreau
2017-06-08 13:09 ` Roel Janssen
2017-06-08 18:08 ` Roel Janssen
2017-06-08 18:34 ` Kei Kebreau
2017-06-08 14:01 ` Mark H Weaver
2017-06-08 14:54 ` Chris Marusich
2017-06-08 17:08 ` Leo Famulari
2017-06-08 17:19 ` Marius Bakke
2017-06-08 17:29 ` Catonano
2017-06-08 17:45 ` Leo Famulari [this message]
2017-06-08 18:12 ` Leo Famulari
2017-06-08 20:47 ` Ludovic Courtès
2017-06-11 8:57 ` Mark H Weaver
2017-06-11 13:16 ` Ludovic Courtès
2017-06-08 14:20 ` pelzflorian (Florian Pelz)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170608174541.GA2313@jasmine \
--to=leo@famulari.name \
--cc=27264@debbugs.gnu.org \
--cc=catonano@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.