all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <rvgn@disroot.org>
To: mail@cbaines.net, 36634@debbugs.gnu.org
Subject: bug#36634: Virtual Machine Manager (virt-manager)
Date: Sun, 21 Jul 2019 17:42:14 -0400	[thread overview]
Message-ID: <00999c57af938c7946871d8c12c9aabeb28e12af.camel@disroot.org> (raw)
In-Reply-To: <87sgqze1yq.fsf@cbaines.net>


> So, I've experienced this too. Even though this is a cgroup thing,
> I'm
> pretty sure this isn't an issue with Linux.

I see.

> I've tried reverting the changes in [1], and that seems to solve the
> issue. Unfortunately, I don't have any insight in to what's different
> between the problematic 5.5.0 release, and the working 5.4.0 release.

So, by reverting changes, do you mean you patched and made a new
commit?

Thank you!

Regards,
RG.

  reply	other threads:[~2019-07-21 21:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  5:06 bug#36634: Virtual Machine Manager (virt-manager) Raghav Gururajan
2019-07-14 12:42 ` Efraim Flashner
2019-07-14 21:21   ` Raghav Gururajan
2019-07-21 17:23 ` Christopher Baines
2019-07-21 21:42   ` Raghav Gururajan [this message]
2019-09-23  4:14   ` Chris Marusich
2019-09-23  4:30     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-05  5:41     ` Chris Marusich
2019-10-10  8:55       ` Chris Marusich
2019-07-25  9:46 ` bug#36634: ATTENTION REQUIRED Raghav Gururajan
2019-07-25 19:36   ` Tobias Geerinckx-Rice
2019-07-25 20:01     ` Tobias Geerinckx-Rice
2019-07-26  3:51       ` bug#36634: Raghav Gururajan
2019-07-26  3:47     ` bug#36634: Raghav Gururajan
2019-09-08 18:14 ` bug#36634: Virtual Machine Manager (virt-manager) Christopher Baines
2019-10-21 14:46 ` Miguel Arruga Vivas
2019-10-27  9:37   ` Miguel Arruga Vivas
2019-11-07  8:44     ` Chris Marusich
2019-11-08  0:53       ` Miguel Arruga Vivas
2020-03-19 10:06 ` bug#36634: (no subject) Brice Waegeneire

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=00999c57af938c7946871d8c12c9aabeb28e12af.camel@disroot.org \
    --to=rvgn@disroot.org \
    --cc=36634@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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.