On Thu, 2016-01-21 at 14:33 +0200, Cristian Sava wrote:
> On Thu, 2016-01-21 at 11:55 +0100, thibaut noah wrote:
> > Did you report it? seems like someone forgot to check the pointer
> > before accessing it.
> Not yet. Further investigation is needed.
> What I've done now in virtual environment:
>
On Thu, 2016-01-21 at 12:22 -0700, Chris Murphy wrote:
> Weird. I've been using virt-manager with kernel 4.3.3 and 4.4.0 on
> Fedora 23 for some time without problems. Maybe check AVC messages?
>
> ausearch -m AVC
>
> Maybe it's worth relabeling:
>
> restorecon -rv /
>
> I don't know why but ev
Weird. I've been using virt-manager with kernel 4.3.3 and 4.4.0 on
Fedora 23 for some time without problems. Maybe check AVC messages?
ausearch -m AVC
Maybe it's worth relabeling:
restorecon -rv /
I don't know why but even after a clean install and no updates,
restorecon fixes labels. It's like
On Thu, 2016-01-21 at 11:55 +0100, thibaut noah wrote:
> Did you report it? seems like someone forgot to check the pointer
> before accessing it.
Not yet. Further investigation is needed.
What I've done now in virtual environment:
1-Install F23 server, default, no options.
2-Update, reboot
3-Instal
Did you report it? seems like someone forgot to check the pointer before
accessing it.
2016-01-21 9:12 GMT+01:00 Cristian Sava :
> I have a F23 server with minimal working X (no desktop).
> All was working well with kernel-4.2.x
> With kernel-4.3.x I get (in xterm):
>
> [a53@s ~]$ su -c virt-mana
I have a F23 server with minimal working X (no desktop).
All was working well with kernel-4.2.x
With kernel-4.3.x I get (in xterm):
[a53@s ~]$ su -c virt-manager
Password:
[a53@s ~]$ No protocol specified
Unable to init server: Could not connect: Connection refused
(virt-manager:54862): Gtk-CRITI
