Re: Boxes on Mageia



On Wed, Jan 11, 2012 at 08:11:55PM +0100, Marc-André Lureau wrote:
> On Wed, Jan 11, 2012 at 6:50 PM, Olav Vitters <olav vitters nl> wrote:
> > above about .ppm files repeat every few seconds. The files itself are 0
> > bytes.
> 
> Ah, if the file is 0 byte it's a different issue than shared-mime-info.

Rebuilding anyway :P

> Which version of libvirt & libvirt-glib do you have?

$ urpmq -yf virt | grep lib | grep -v i586
lib64virt-devel-0.9.9-1.mga2.x86_64
lib64virt-gconfig-gir1.0-0.0.3-1.mga2.x86_64
lib64virt-gconfig1.0-devel-0.0.3-1.mga2.x86_64
lib64virt-gconfig1.0_0-0.0.3-1.mga2.x86_64
lib64virt-glib-gir1.0-0.0.3-1.mga2.x86_64
lib64virt-glib1.0-devel-0.0.3-1.mga2.x86_64
lib64virt-glib1.0_0-0.0.3-1.mga2.x86_64
lib64virt-gobject-gir1.0-0.0.3-1.mga2.x86_64
lib64virt-gobject1.0-devel-0.0.3-1.mga2.x86_64
lib64virt-gobject1.0_0-0.0.3-1.mga2.x86_64
lib64virt-static-devel-0.9.9-1.mga2.x86_64
lib64virt0-0.9.9-1.mga2.x86_64
libvirt-debug-0.9.9-1.mga2.x86_64
libvirt-glib-debug-0.0.3-1.mga2.x86_64
libvirt-glib-python-0.0.3-1.mga2.x86_64
libvirt-java-0.4.7-1.mga2.noarch
libvirt-java-0.4.7-1.mga2.noarch
libvirt-java-devel-0.4.7-1.mga2.noarch
libvirt-java-devel-0.4.7-1.mga2.noarch
libvirt-java-javadoc-0.4.7-1.mga2.noarch
libvirt-java-javadoc-0.4.7-1.mga2.noarch
libvirt-utils-0.9.9-1.mga2.x86_64

> I had this issue last week, which I thought was solved by reverting
> c5a239423a215435626bf6d1af75458c5ec03147 in libvirt-glib, but I can't
> reproduce the pb anymore.. You could perhaps try it?

I'll try that after installing shared-mime-info. Also try and reboot.
Initially qemu didn't have spice support. I hope that is not in the
kernel module, but could be.


Since the message, did notice a few more things.

>From dmesg:
Bridge firewalling registered
ADDRCONF(NETDEV_UP): virbr0: link is not ready

>From /var/log/messages:
Jan 11 20:10:11 bkor NetworkManager[1414]: <warn> error monitoring
device for netlink events: error occurred while waiting for data on
socket
Jan 11 20:10:11 bkor NetworkManager[1414]: NetworkManager[1414]: <warn>
error monitoring device for netlink events: error occurred while waiting
for data on socket
Jan 11 20:10:41 bkor NetworkManager[1414]: <warn> error monitoring
device for netlink events: error occurred while waiting for data on
socket
Jan 11 20:10:41 bkor NetworkManager[1414]: NetworkManager[1414]: <warn>
error monitoring device for netlink events: error occurred while waiting
for data on socket
Jan 11 20:11:11 bkor NetworkManager[1414]: <warn> error monitoring
device for netlink events: error occurred while waiting for data on
socket
Jan 11 20:11:11 bkor NetworkManager[1414]: NetworkManager[1414]: <warn>
error monitoring device for netlink events: error occurred while waiting
for data on socket
Jan 11 20:11:41 bkor NetworkManager[1414]: <warn> error monitoring
device for netlink events: error processing netlink message: recvmsg
failed (errno = No buffer space available)
Jan 11 20:11:41 bkor NetworkManager[1414]: NetworkManager[1414]: <warn>
error monitoring device for netlink events: error processing netlink
message: recvmsg failed (errno = No buffer space available)
Jan 11 20:12:11 bkor NetworkManager[1414]: <warn> error monitoring
device for netlink events: error processing netlink message: recvmsg
failed (errno = No buffer space available)
Jan 11 20:12:11 bkor NetworkManager[1414]: NetworkManager[1414]: <warn>
error monitoring device for netlink events: error processing netlink
message: recvmsg failed (errno = No buffer space available)

and stuff like this (seems to often create a new session):
Jan 11 20:15:01 bkor systemd-logind[1425]: New session 3856 of user olav.



-- 
Regards,
Olav


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]