From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Virt-Manager Not Connected
Date: Sat, 29 Apr 2023 03:52:46 +0200 [thread overview]
Message-ID: <20230429015246.DrPcJ5BqqQdoHiDIxF_Iqlk_LH8f8OWIOkcR8Wb4ibQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41397@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3155 bytes --]
Closed issue by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397
Description:
### Is this a new report?
Yes
### System Info
Void 6.0.15_1 x86_64 AuthenticAMD uptodate FFF
### Package(s) Affected
virt-manager
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Run as normal
### Actual behaviour
[mrtuxa@mrtuxa ~]$ virt-manager --debug
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (cli:204) Version 4.1.0 launched with command line: /usr/bin/virt-manager --debug
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:167) virt-manager version: 4.1.0
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:168) virtManager import: /usr/share/virt-manager/virtManager
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:205) PyGObject version: 3.42.2
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:209) GTK version: 3.24.34
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (systray:476) Showing systray: False
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (inspection:206) python guestfs is not installed
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:113) Loading stored URIs:
qemu:///system
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:461) processing cli command uri= show_window=manager domain=
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:464) No cli action requested, launching default window
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (manager:185) Showing manager
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:316) window counter incremented to 1
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:211) Initial gtkapplication activated
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:903) Scheduling background open thread for qemu:///system
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:838) conn.close() uri=qemu:///system
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:482) conn=qemu:///system changed to state=Disconnected
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:179) Autostart connection error: Unable to connect to libvirt qemu:///system.
Verify that the 'libvirtd' daemon is running.
Libvirt URI is: qemu:///system
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 923, in _do_open
self._backend.open(cb, data)
File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open
conn = libvirt.openAuth(self._open_uri,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/libvirt.py", line 147, in openAuth
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
### Steps to reproduce
Search on Github and Stackoverflow and Arch Linux Wiki
prev parent reply other threads:[~2023-04-29 1:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 20:03 [ISSUE] " mrtuxa
2023-01-01 20:04 ` classabbyamp
2023-01-01 21:06 ` realcharmer
2023-01-01 21:06 ` realcharmer
2023-01-01 21:06 ` realcharmer
2023-01-01 21:07 ` realcharmer
2023-01-01 22:00 ` mrtuxa
2023-01-01 22:00 ` mrtuxa
2023-01-01 22:05 ` classabbyamp
2023-01-01 22:08 ` realcharmer
2023-01-02 9:12 ` mrtuxa
2023-01-02 9:13 ` mrtuxa
2023-01-02 9:16 ` realcharmer
2023-01-02 11:04 ` mrtuxa
2023-01-02 11:50 ` paper42
2023-01-02 13:48 ` mrtuxa
2023-01-02 13:50 ` realcharmer
2023-01-15 1:51 ` bugcrazy
2023-04-15 1:52 ` github-actions
2023-04-29 1:52 ` github-actions [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230429015246.DrPcJ5BqqQdoHiDIxF_Iqlk_LH8f8OWIOkcR8Wb4ibQ@z \
--to=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).