thanks! Installing python-configobj fixed it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283716
Title:
landscape-client missing python-configobj dependency
To manage notifications about this bu
This is the output
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/landscape/deployment.py", line 4, in
from configobj import ConfigObj, ConfigObjError
ImportError: No module named configobj
I've already tried purging the landscape-* packag
Here you go
** Attachment added: "python-import.log"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1283716/+attachment/3994061/+files/python-import.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
solskogen@friend:~$ landscape-sysinfo
solskogen@friend:~$ echo $?
2
(same with sudo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283716
Title:
No output from landscape-sysinfo
To manage notific
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283716
Title:
No output from landscape-sysinfo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
In trusty:
solskogen@friend:~$ landscape-sysinfo
solskogen@friend:~$ landscape-sysinfo -v
solskogen@friend:~$ landscape-sysinfo --help
solskogen@friend:~$ sudo landscape-sysinfo
[sudo] password for solskogen:
solskogen@friend:~$ dpkg -l | grep landscape
ii landscape-client
The problem went away after a reboot, I found out today.
On 16 Sep 2013 17:45, "Serge Hallyn" <1225...@bugs.launchpad.net> wrote:
> Ah, the bug appears to be with lxc-monitord starting up.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.la
Public bug reported:
With 1.0.0~alpha1-0ubuntu3 "lxc-ls --fancy" dies with "lxc_container: command
get_init_pid response data 1812070400 too long"
lxc-ls alone works fine.
Ubuntu 13.10.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificat
Public bug reported:
virt-manager 0.10.0 was released on wednesday June 19, 2013. Would love
to see it included for 13.10.
** Affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Well, this is a bug that was introduced in 3.8.0-28-generic. As
3.8.0-27-generic does not seems to be affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restar
That works too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restarting containers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.6-raring/linux-
image-3.8.13-03081306-generic_3.8.13-03081306.201308021435_amd64.deb
worked!
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream-v3.8.13
--
You received this bug notification because you are a member o
from kmsg:
<6>[ 75.398771] device vethldju4L entered promiscuous mode
<6>[ 75.398896] IPv6: ADDRCONF(NETDEV_UP): vethldju4L: link is not ready
<4>[ 75.402908] cgroup: lxc-start (2032) created nested cgroup for controller
"memory" which has incomplete hierarchy support. Nested cgroups may cha
apport information
** Attachment added: "HookError_cloud_archive.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/376/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768893/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
ke
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768895/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768890/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768892/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
apport information
** Description changed:
With 3.8.0-28-generic stopping a container (at least if there under a
minute or so it was started) will crash the kernel.
To repeat
Make sure you have that kernel (release kernel works fine) - its in the
raring-proposed.
Create a container
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768889/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kern
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768891/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768894/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768540/+files/HookError_ubuntu.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubunt
apport information
** Attachment added: "HookError_source_lxc.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768539/+files/HookError_source_lxc.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "HookError_cloud_archive.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768536/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
apport information
** Attachment added: "HookError_source_linux.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768538/+files/HookError_source_linux.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
apport information
** Attachment added: "HookError_generic.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768537/+files/HookError_generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
It's a bit hard, since this bug crashed the host system completly. But
can run that command after the machine boots. It will probably have
something in syslog.
** Tags added: apport-collected
** Description changed:
With 3.8.0-28-generic stopping a container (at least if there under a
minute
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1210859/+attachment/3768535/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
3.8.0-27-generic also works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restarting containers
To manage notifications about this bug go to:
https://bugs.lau
Public bug reported:
With 3.8.0-28-generic stopping a container (at least if there under a
minute or so it was started) will crash the kernel.
To repeat
Make sure you have that kernel (release kernel works fine) - its in the
raring-proposed.
Create a container (with ubuntu template)
Start it
Sto
31 matches
Mail list logo