From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Christian Miller <miller.christian@proton.me>,
"64073@debbugs.gnu.org" <64073@debbugs.gnu.org>
Subject: bug#64073: libvirtd requires restart to function
Date: Sat, 17 Jun 2023 18:02:14 +0200 [thread overview]
Message-ID: <87352q5b7d.fsf@jpoiret.xyz> (raw)
In-Reply-To: <UudC9AwPmARDdZ3cSUTcE7SlFGz2JQjAcTkviK04JjSBDcR5YcevXjEFX5bUDLwC41Wpi1BYVUBlsZ_aWgtI1AhhV6bJQaOk1B_2mFI-WBY=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
Hi Christian,
Christian Miller via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Hi,
>
> there is not an error message upon starting it but by stopping it:
> Jun 14 23:52:18 localhost shepherd[1]: Stopping service libvirtd...
> Jun 14 23:52:18 localhost libvirtd: 157: error : virGDBusGetSystemBus:99 : internal error: Unable to get system bus connection: Could not connect: No such file or directory
Seems that dbus is needed for libvirt, but it is not listed as a
requirement for the shepherd service. I don't use libvirt, but would
you be able to test the following patch?
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-06-17 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 22:40 bug#64073: libvirtd requires restart to function Christian Miller via Bug reports for GNU Guix
2023-06-15 12:37 ` Ludovic Courtès
2023-06-16 20:44 ` Christian Miller via Bug reports for GNU Guix
2023-06-17 16:02 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-06-17 16:03 ` bug#64073: [PATCH] services: libvirt: Add requirement on dbus Josselin Poiret via Bug reports for GNU Guix
2023-06-19 19:29 ` bug#64073: libvirtd requires restart to function Christian Miller via Bug reports for GNU Guix
2023-06-20 12:21 ` Josselin Poiret via Bug reports for GNU Guix
2023-07-07 19:48 ` Josselin Poiret via Bug reports for GNU Guix
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=87352q5b7d.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=64073@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=miller.christian@proton.me \
/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).