Re: [arch-general] libxp.so.6 not found

2016-03-03 Thread Doug Newgard
On Fri, 4 Mar 2016 10:22:17 +0800 Fulcrum wrote: > Could any body help me figure this out? As per my understanding, my GUI > tool needs 32-bit libraries. The other libraries that I installed had > some packages like 'lib32-xyz' from multilib repo. But libxp has no 32 > bit package. Sure it do

[arch-general] libxp.so.6 not found

2016-03-03 Thread Fulcrum
Hi I need to run a GUI tool. It runs fine under Ubuntu but when I try to run under Arch, it says: >./gmv ./gmv: error while loading shared libraries: libXp.so.6: cannot open shared object file: No such file or directory Earlier, multiple other libraries were missing too, such as libxt, but

Re: [arch-general] libvirt and VirtualBox

2016-03-03 Thread Jukka Salmi
Jukka Salmi --> arch-general (2016-03-03 16:11:01 +0100): > Damjan Georgievski --> arch-general (2016-03-03 14:43:03 +0100): > > since the update of libvirt to 1.3.2, it seems the sd_notify support > > is broken, and the daemon is killed. > > > > is the daemon even running for you? > > Hmm, this

Re: [arch-general] Heads up: If you are using SSLv2 turn it off immediately

2016-03-03 Thread P . A . López-Valencia
On jue, 2016-03-03 at 08:37 +0100, Nicolas F. wrote: > On 01/03/16 23:23, P. A. López-Valencia wrote: > > > > The vulnerability is so bad[1], it doesn't only have a CVE number,  > > CVE-2016-0800[4], but a name and its own website: HTTPS > > DROWN[1][2][3]. > Just as many other vulnerabilities the

Re: [arch-general] libvirt and VirtualBox

2016-03-03 Thread Jukka Salmi
Damjan Georgievski --> arch-general (2016-03-03 14:43:03 +0100): > since the update of libvirt to 1.3.2, it seems the sd_notify support > is broken, and the daemon is killed. > > is the daemon even running for you? Hmm, this seems to be another issue, because the issue I was talking about (`virsh

Re: [arch-general] libvirt and VirtualBox

2016-03-03 Thread Damjan Georgievski
since the update of libvirt to 1.3.2, it seems the sd_notify support is broken, and the daemon is killed. is the daemon even running for you? On 3 March 2016 at 14:37, Jukka Salmi wrote: > Hello > > On an up-to-date Arch x86-64 system, I fail to manage VirtualBox VMs > with libvirt virsh: > > $

[arch-general] libvirt and VirtualBox

2016-03-03 Thread Jukka Salmi
Hello On an up-to-date Arch x86-64 system, I fail to manage VirtualBox VMs with libvirt virsh: $ virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API Is this supposed to work out of the box? Both VirtualBox (5.0.14