+1 on adding to GUI. Priority-wise I think it goes after a decent chunk
of other goals, but it definitely fits into what we've said we want the
GUI to accomplish, and if we see a way to fit it in quickly hopefully we
can.
** Changed in: juju-gui
Status: New = Triaged
** Changed in:
+1 on adding to GUI. Priority-wise I think it goes after a decent chunk
of other goals, but it definitely fits into what we've said we want the
GUI to accomplish, and if we see a way to fit it in quickly hopefully we
can.
** Changed in: juju-gui
Status: New = Triaged
** Changed in:
PyPI release: https://pypi.python.org/pypi/juju-quickstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273865
Title:
[needs-packaging] juju-quickstart
To manage notifications about this bug go
Public bug reported:
URL: https://launchpad.net/juju-quickstart
License: GNU Affero GPL v3
Description: Help both new and experienced users quickly start Juju from
Ubuntu. Juju Quickstart is an opinionated command-line tool that quickly
starts Juju and the GUI, whether you've never installed
For anyone looking at this bug, the Juju GUI fix mentioned has been
released for several months now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1149410
Title:
Stuck on Trying to
For anyone looking at this bug, the Juju GUI fix mentioned has been
released for several months now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1149410
Title:
Stuck on Trying to connect to the
Hi Marius. I take it that you encountered this problem again? Under what
circumstances–what versions of the charm and GUI? ~juju-gui's trunk of
the charm + juju GUI trunk should do what you need but everything else
will not at the moment. We are blocked by ~charmers in getting the charm
published,
On 03/14/2013 08:17 AM, Marius B. Kotsbak wrote:
Yes, I encountered it again, using juju-gui-source: trunk. and
cs:precise/juju-gui. Maybe this was a slightly different problem, but
still at loading the main page and failing to connect to the API. I also
saw this in the log:
Starting or
Hi Marius. I take it that you encountered this problem again? Under what
circumstances–what versions of the charm and GUI? ~juju-gui's trunk of
the charm + juju GUI trunk should do what you need but everything else
will not at the moment. We are blocked by ~charmers in getting the charm
published,
On 03/14/2013 08:17 AM, Marius B. Kotsbak wrote:
Yes, I encountered it again, using juju-gui-source: trunk. and
cs:precise/juju-gui. Maybe this was a slightly different problem, but
still at loading the main page and failing to connect to the API. I also
saw this in the log:
Starting or
If someone encounters these symptoms in Precise, the more detailed
instructions to fix it is to adjust apparmor as described in
http://www.stgraber.org/2012/05/04/lxc-in-ubuntu-12-04-lts/ , in the
section labeled Container nesting. The apparmor change is part of
Quantal, so the blog post's steps
If someone encounters these symptoms in Precise, the more detailed
instructions to fix it is to adjust apparmor as described in
http://www.stgraber.org/2012/05/04/lxc-in-ubuntu-12-04-lts/ , in the
section labeled Container nesting. The apparmor change is part of
Quantal, so the blog post's steps
Note that the workaround helps significantly but is not always
sufficient. If I do not apply it, I can reliably encounter the problem
every single test run.
Another team is working on moving us to run on Precise in production,
which would let us use Precise containers. Precise containers do not
Note that the workaround helps significantly but is not always
sufficient. If I do not apply it, I can reliably encounter the problem
every single test run.
Another team is working on moving us to run on Precise in production,
which would let us use Precise containers. Precise containers do not
This was working very well for us, and the lxc-start-ephemeral TRIES=60
was working fine. Starting last week, we began seeing recurrence of
this problem, even with the workarounds applied and TRIES hacked to 180.
I intend to circle around with Serge and see if he has any other ideas.
--
You
This was working very well for us, and the lxc-start-ephemeral TRIES=60
was working fine. Starting last week, we began seeing recurrence of
this problem, even with the workarounds applied and TRIES hacked to 180.
I intend to circle around with Serge and see if he has any other ideas.
--
You
Serge, thank you! The workaround appears to work very well for us. The
containers started quickly, and it should not only give us more reliable
starts but also seems to have taken at least three minutes off our
average run time, as you might expect.
--
You received this bug notification
Serge, thank you! The workaround appears to work very well for us. The
containers started quickly, and it should not only give us more reliable
starts but also seems to have taken at least three minutes off our
average run time, as you might expect.
--
You received this bug notification
Public bug reported:
We are gathering more data, but it feels like we have enough to start a
bug report.
On Precise, on a 16 core/32 thread EC2 machine (instance type
cc2.8xlarge), when starting approximately eight or more Lucid containers
simultaneously, after the first seven or so connect to
** Description changed:
We are gathering more data, but it feels like we have enough to start a
bug report.
On Precise, on a 16 core/32 thread EC2 machine (instance type
cc2.8xlarge), when starting approximately eight or more Lucid containers
- simultaneously, after the first seven or
Public bug reported:
We are gathering more data, but it feels like we have enough to start a
bug report.
On Precise, on a 16 core/32 thread EC2 machine (instance type
cc2.8xlarge), when starting approximately eight or more Lucid containers
simultaneously, after the first seven or so connect to
** Description changed:
We are gathering more data, but it feels like we have enough to start a
bug report.
On Precise, on a 16 core/32 thread EC2 machine (instance type
cc2.8xlarge), when starting approximately eight or more Lucid containers
- simultaneously, after the first seven or
The improvement in the new version is significant, and there is no
regression.
The improvement is still insufficient for our use case, as I noted would
be likely in the updated description. For our use case of 32 LXC
containers running on a 32 core (16 hyperthreaded) EC2 box, 21 ephemeral
The improvement in the new version is significant, and there is no
regression.
The improvement is still insufficient for our use case, as I noted would
be likely in the updated description. For our use case of 32 LXC
containers running on a 32 core (16 hyperthreaded) EC2 box, 21 ephemeral
** Description changed:
[Impact]
- fill me in with explanation of severity and frequency of bug on users and
justification for backporting the fix to the stable release
+ This affects anyone using lxc-start-ephemeral as part of an automated process
for which intermittent failures are a
** Description changed:
[Impact]
- fill me in with explanation of severity and frequency of bug on users and
justification for backporting the fix to the stable release
+ This affects anyone using lxc-start-ephemeral as part of an automated process
for which intermittent failures are a
Public bug reported:
When lxc-start-ephemeral is given a command to run (-- do_something) it
wants to use lxc-attach to run the command, but lxc-attach is not ready
yet. Instead, it parses the dhcp leases to figure out the IP for the
container, and then tries to use ssh to run the command.
Public bug reported:
When lxc-start-ephemeral is given a command to run (-- do_something) it
wants to use lxc-attach to run the command, but lxc-attach is not ready
yet. Instead, it parses the dhcp leases to figure out the IP for the
container, and then tries to use ssh to run the command.
Thank you, this works very nicely on my laptop's touchpad.
It's not working on the Magic Trackpad, but it didn't before IIRC, in
which case it's not a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Salgado, would you be able to do this verification? If not, let me
know, and I'll do it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working
Salgado, would you be able to do this verification? If not, let me
know, and I'll do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid
This is easily and repeatably duplicatable on in my lxc lucid container.
The error for the last test (with the multiprocessing SemLock OSError
seems the most likely to be a shared root cause to me. Interestingly,
the OSError was slightly different for me, with a newer lxc: OSError:
[Errno 38]
This is easily and repeatably duplicatable on in my lxc lucid container.
The error for the last test (with the multiprocessing SemLock OSError
seems the most likely to be a shared root cause to me. Interestingly,
the OSError was slightly different for me, with a newer lxc: OSError:
[Errno 38]
Public bug reported:
It is possible to have an ephemeral container remaining after lxc-start-
ephemeral has been killed--trivially by calling kill -9 on lxc-start-
ephemeral. At that point, the script does not get a chance to clean up
after itself, and the system is left with a running ephemeral
I agree. I was thinking as I wrote this that we would be awfully close
to being able to get rid of the -- COMMAND stuff if this were
implemented, for instance; and generally close to being able to make
lxc-start-ephemeral behave very similarly to lxc-start in terms of
interaction patterns.
Public bug reported:
It is possible to have an ephemeral container remaining after lxc-start-
ephemeral has been killed--trivially by calling kill -9 on lxc-start-
ephemeral. At that point, the script does not get a chance to clean up
after itself, and the system is left with a running ephemeral
I agree. I was thinking as I wrote this that we would be awfully close
to being able to get rid of the -- COMMAND stuff if this were
implemented, for instance; and generally close to being able to make
lxc-start-ephemeral behave very similarly to lxc-start in terms of
interaction patterns.
I have duped the problem Benji reported, and did the kernel test in
order to let him work on other tasks.
The given kernel (reported in /proc/version as Linux version
3.3.0-030300-generic (apw@gomeisa) (gcc version 4.4.3 (Ubuntu
4.4.3-4ubuntu5.1) ) #201203182135 SMP Mon Mar 19 01:36:20 UTC 2012)
Public bug reported:
The -b flag in current Precise lxc-create sets up an fstab that has
$homedir $homedir none bind 0 0 instead of $homedir
/var/lib/lxc/$container/rootfs/$homedir none bind 0 0. This doesn't
seem to work, which is a regression.
I created a container with this:
$ sudo
I have duped the problem Benji reported, and did the kernel test in
order to let him work on other tasks.
The given kernel (reported in /proc/version as Linux version
3.3.0-030300-generic (apw@gomeisa) (gcc version 4.4.3 (Ubuntu
4.4.3-4ubuntu5.1) ) #201203182135 SMP Mon Mar 19 01:36:20 UTC 2012)
Public bug reported:
The -b flag in current Precise lxc-create sets up an fstab that has
$homedir $homedir none bind 0 0 instead of $homedir
/var/lib/lxc/$container/rootfs/$homedir none bind 0 0. This doesn't
seem to work, which is a regression.
I created a container with this:
$ sudo
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/959352
Title:
Ephemeral containers have /rootfs prefix in
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959352
Title:
Ephemeral containers have /rootfs prefix in /proc/self/maps entries
Public bug reported:
Because of the problems we've encountered with overlayfs over the past
couple of months, and because aufs did seem to be working earlier, I'd
like it if we could have an option to use aufs with lxc-start-ephemeral.
Because overlayfs is the well-advertised future and aufs is
We are discovering that this, or something very similar to it, is
serious. For our own use, at least, I'd raise this to high (we don't
have privileges to do so).
According to lsof, many, many processes (sshd, upstart, init, ntpd,
etc., as well as processes we start directly such as xvfb-run and
Hi Serge. Thanks for looking at this.
On an aufs-mounted ephemeral:
gary@lpdev-temp-tKJg9Ss:~$ cat /proc/self/maps
08048000-08054000 r-xp 08:12 414657
/var/lib/lxc/lpdev/rootfs/bin/cat
08054000-08055000 r--p b000 08:12 414657
Public bug reported:
Because of the problems we've encountered with overlayfs over the past
couple of months, and because aufs did seem to be working earlier, I'd
like it if we could have an option to use aufs with lxc-start-ephemeral.
Because overlayfs is the well-advertised future and aufs is
We are discovering that this, or something very similar to it, is
serious. For our own use, at least, I'd raise this to high (we don't
have privileges to do so).
According to lsof, many, many processes (sshd, upstart, init, ntpd,
etc., as well as processes we start directly such as xvfb-run and
Hi Serge. Thanks for looking at this.
On an aufs-mounted ephemeral:
gary@lpdev-temp-tKJg9Ss:~$ cat /proc/self/maps
08048000-08054000 r-xp 08:12 414657
/var/lib/lxc/lpdev/rootfs/bin/cat
08054000-08055000 r--p b000 08:12 414657
Public bug reported:
This fixes it:
=== modified file 'debian/local/lxc-start-ephemeral'
--- debian/local/lxc-start-ephemeral2012-03-12 13:22:06 +
+++ debian/local/lxc-start-ephemeral2012-03-14 01:10:20 +
@@ -100,6 +100,8 @@
esac
done
+COMMAND=$@
+COMMAND_LENGTH=$#
Public bug reported:
This fixes it:
=== modified file 'debian/local/lxc-start-ephemeral'
--- debian/local/lxc-start-ephemeral2012-03-12 13:22:06 +
+++ debian/local/lxc-start-ephemeral2012-03-14 01:10:20 +
@@ -100,6 +100,8 @@
esac
done
+COMMAND=$@
+COMMAND_LENGTH=$#
Hi Serge. I don't actually know the original intent of -b, but what you
say makes sense. I changed our code to change all bind mounts in the
ephemeral's container to an ephemeral overlay, instead. That's kind of
what I wanted anyway, but I was being lazy. :-) I also worried it would
not be
Hi Serge. I don't actually know the original intent of -b, but what you
say makes sense. I changed our code to change all bind mounts in the
ephemeral's container to an ephemeral overlay, instead. That's kind of
what I wanted anyway, but I was being lazy. :-) I also worried it would
not be
Public bug reported:
The directories mounted both using the ephemeral's fstab and using -b
are not ephemeral. Changes to them persist on the filesystem, and are
thus shared across other ephemeral instances that mount the same
directories.
We have a branch that addresses this concern. We took
Public bug reported:
If multiple lxc-waits are run simultaneously, all after the first will
fail with bind : Address already in use.
This is apparently a known issue.
http://comments.gmane.org/gmane.linux.kernel.containers.lxc.general/962
** Affects: lxc (Ubuntu)
Importance: Undecided
Public bug reported:
The directories mounted both using the ephemeral's fstab and using -b
are not ephemeral. Changes to them persist on the filesystem, and are
thus shared across other ephemeral instances that mount the same
directories.
We have a branch that addresses this concern. We took
Public bug reported:
If multiple lxc-waits are run simultaneously, all after the first will
fail with bind : Address already in use.
This is apparently a known issue.
http://comments.gmane.org/gmane.linux.kernel.containers.lxc.general/962
** Affects: lxc (Ubuntu)
Importance: Undecided
Public bug reported:
As smoser pointed out, lxc-start-ephemeral needs to do the same kinds of
things that lxc-clone does, such as this:
# change hwaddrs
mv ${c} ${c}.old
(
while read line; do
if [ ${line:0:18} = lxc.network.hwaddr ]; then
echo lxc.network.hwaddr=
Public bug reported:
As smoser pointed out, lxc-start-ephemeral needs to do the same kinds of
things that lxc-clone does, such as this:
# change hwaddrs
mv ${c} ${c}.old
(
while read line; do
if [ ${line:0:18} = lxc.network.hwaddr ]; then
echo lxc.network.hwaddr=
Public bug reported:
Because of the current ssh approach used in lxc-start-ephemeral in lieu
of lxc-attach, you need a password or key in the ubuntu account to
connect. If you want to do this with automation, you can use a key. If
you want to use this with another user and that user's key, you
Public bug reported:
Because of the current ssh approach used in lxc-start-ephemeral in lieu
of lxc-attach, you need a password or key in the ubuntu account to
connect. If you want to do this with automation, you can use a key. If
you want to use this with another user and that user's key, you
Running apport-collect led to bug 944429
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944386
Title:
Making a hard link of a 0444 permission file fails in overlayfs
[Precise]
To manage
Public bug reported:
On Precise updated as of a few minutes ago. Notice the error message
four lines from the bottom
gary@garubtosh:~$ mkdir upper
gary@garubtosh:~$ mkdir lower
gary@garubtosh:~$ mkdir tmp
gary@garubtosh:~$ cd lower/
gary@garubtosh:~/lower$ touch 1
gary@garubtosh:~/lower$ chmod
Public bug reported:
With a precise that is update as of a few hours ago, I continue to get
system hangs on my MacBook 5,3. These happen consistently when I do a
two finger scroll. Sometimes killing Compiz solves the problem;
sometimes that doesn't work and I have to reboot.
Please let me know
** Summary changed:
- two finger drag is causing intermittent hangs
+ two finger drag is causing intermittent hangs [Precise]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942800
Title:
two
** Description changed:
- With a precise that is update as of a few hours ago, I continue to get
- system hangs on my MacBook 5,3. These happen consistently when I do a
- two finger scroll. Sometimes killing Compiz solves the problem;
- sometimes that doesn't work and I have to reboot.
+ With a
Public bug reported:
We believe sshd just hasn't started quickly enough, sometimes.
Graham Binns worked out this kind of solution, if it works for you:
http://pastebin.ubuntu.com/844925/ (see lines 146-157 in particular).
Thanks
Gary
** Affects: lxc (Ubuntu)
Importance: Undecided
Public bug reported:
We believe sshd just hasn't started quickly enough, sometimes.
Graham Binns worked out this kind of solution, if it works for you:
http://pastebin.ubuntu.com/844925/ (see lines 146-157 in particular).
Thanks
Gary
** Affects: lxc (Ubuntu)
Importance: Undecided
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925024
Title:
apparmor makes it impossible to install
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925028
Title:
apparmor breaks lxc-start-ephemeral (apparmor+overlayfs
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925028
Title:
apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns
-EINVAL)
To manage
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925024
Title:
apparmor makes it impossible to install postgresql-common on Precise
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925028
Title:
apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925028
Title:
apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns
-EINVAL)
To manage notifications about
This seems related, but not identical, to bug 918327
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925520
Title:
lxc script non-root errors can be confusing
To manage notifications
Public bug reported:
A trivial thing, but at least a couple of people have been confused by
something like this, just being forgetful:
$ lxc-start -n lp
lxc-start: failed to cap_get_flag: Invalid argument
lxc-start: failed to create veth5HNAcN-vethyuiOEf : Operation not permitted
lxc-start:
Public bug reported:
A trivial thing, but at least a couple of people have been confused by
something like this, just being forgetful:
$ lxc-start -n lp
lxc-start: failed to cap_get_flag: Invalid argument
lxc-start: failed to create veth5HNAcN-vethyuiOEf : Operation not permitted
lxc-start:
This seems related, but not identical, to bug 918327
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925520
Title:
lxc script non-root errors can be confusing
To manage notifications about this bug
I tried the fix and I got the same symptom.
For clarity:
- I wiped out /var/lxc/cache before I started because lxc-create wasn't
working. That got lxc-create working. I used the same commands I
listed in the bug description.
- I changed the container's console.conf as described:
$ cat
Public bug reported:
Repro:
$ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise -a
i686 -b gary
$ sudo lxc-start -n precise
[log in as root]
root@precise:~# apt-get install postgresql-common
Reading package lists... Done
Building dependency tree
Reading state
Public bug reported:
Repro:
$ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise -a
i686 -b gary
$ sudo lxc-start-ephemeral -o precise
Setting up ephemeral container...
Starting up the container...
lxc-start: Invalid argument - failed to open
Serge, cool. The workaround is fine. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers
To manage notifications
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706220/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706221/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706222/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706219/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706224/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706223/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706227/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706226/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925028
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706225/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925028
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706230/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706229/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: PulseSinks.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706231/+files/PulseSinks.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706234/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925028
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706233/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925028
apport information
** Attachment added: PulseSources.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706232/+files/PulseSources.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/925028/+attachment/2706235/+files/UdevLog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
apport information
** Tags added: apport-collected running-unity
** Description changed:
Repro:
$ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise
-a i686 -b gary
$ sudo lxc-start -n precise
[log in as root]
root@precise:~# apt-get install
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/925024/+attachment/2706239/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
1 - 100 of 287 matches
Mail list logo
