> It's not common to install an app and need to re-login to be able to
use it. Makes for quite a strange user experience.
In fact it is common enough, just most of the other cases are pre-
installed so people never recognize it. But if you start with a minimal
image you'll hit a few.
> At the very least the error message should be better
The message currently should be like "Can't access
/var/run/libvirt/libvirt-sock" or something like it right?
What would be a good addition there, maybe "Please ensure that you can access
the file (group permissions)"
Since libvirt/virt-manager can have so many connections - local socket,
remote systems, different types - it is hard to have a good message.
Instead we could think of a message on-install that echoes like "If you
are going to use this please re-log to pick up the new group
membership". But TBH lessons-learned people don't read what is printed
on the console on install.
> but there should be a way to actually fix this.
Re-log (or a new) session that starts e.g. virt-manager is enough - so
there is a way to fix it.
** Changed in: virt-manager (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: virt-manager (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784872
Title:
Virt-manager doesn't work after install before a reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1784872/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
