[Bug 496654] [NEW] Ubuntu Server 9.10 (karmic): xenner: depends on non-existent library

[greno]

Public bug reported:

Binary package hint: xenner

I just installed xenner on Karmic (9.10) and have this error during
installation:

* Starting xen block devices xenblkbackd 
/usr/sbin/blkbackd: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory
                                                                                                                                  [fail]
 * Starting xen netblock netbackd 
/usr/sbin/netbackd: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory
                                                                                                                                  [fail]


Here is the install session:

##########################################################
Selecting previously deselected package libaio1.
(Reading database ... 131993 files and directories currently installed.)
Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu1_amd64.deb) ...
Selecting previously deselected package python2.6-dev.
Unpacking python2.6-dev (from .../python2.6-dev_2.6.4-0ubuntu2_amd64.deb) ...
Selecting previously deselected package python-dev.
Unpacking python-dev (from .../python-dev_2.6.4-0ubuntu1_all.deb) ...
Selecting previously deselected package python-xen-3.3.
Unpacking python-xen-3.3 (from .../python-xen-3.3_3.3.0-1ubuntu11_amd64.deb) ...
Selecting previously deselected package xenner.
Unpacking xenner (from .../xenner_0.41-1ubuntu5_amd64.deb) ...
Selecting previously deselected package xen-utils-3.3.
Unpacking xen-utils-3.3 (from .../xen-utils-3.3_3.3.0-1ubuntu11_amd64.deb) ...
[: 19: missing ]
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Setting up libaio1 (0.3.107-3ubuntu1) ...

Setting up python2.6-dev (2.6.4-0ubuntu2) ...
Setting up python-dev (2.6.4-0ubuntu1) ...
Setting up python-xen-3.3 (3.3.0-1ubuntu11) ...

Setting up xenner (0.41-1ubuntu5) ...
update-rc.d: warning: /etc/init.d/xenner missing LSB keyword 'default-stop'

update-rc.d: warning: xenner start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (2 3 4 5 6)
update-rc.d: warning: xenner stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (none)
 * Starting xenner xenner                                                [ OK ]  * Starting evtchnd evtchnd       
 * Starting xensored xenstored                                           [ OK ] 
 * Starting xenconsoled xenconsoled                                      [ OK ] 
 * Starting xen block devices xenblkbackd                                       /usr/sbin/blkbackd: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory
                                                                         [fail]
 * Starting xen netblock netbackd                                               /usr/sbin/netbackd: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory
                                                                         [fail]

Setting up xen-utils-3.3 (3.3.0-1ubuntu11) ...
update-rc.d: warning: xend stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (S 0 1 6)
grep: /proc/xen/capabilities: No such file or directory
update-rc.d: warning: xendomains start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (3 4 5)
update-rc.d: warning: xendomains stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 1 2 6)

Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
##########################################################

Also, it looks like xenner is quite old (0.41).  The latest xenner
release is 0.47.

** Affects: xenner (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Ubuntu Server 9.10 (karmic): xenner: depends on non-existent library
https://bugs.launchpad.net/bugs/496654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs