Quoting David Favor (da...@davidfavor.com):
Correct. It appears the default template processing (default meaning no
template specified) seems like it could use a bit of work.
Ok, thanks.
Seems like specifying no template should either throw an error or create
some form of container that will
Blueprint changed by Yolanda Robla:
Work items changed:
Work items for ubuntu-14.04:
[yolanda.robla] Check, enable, and test apache2: DONE
[yolanda.robla] Check, enable, and test bind9: DONE
[yolanda.robla] Check, enable, and test dovecot (imapd): DONE
[yolanda.robla] Check, enable, and
*** This bug is a duplicate of bug 1261873 ***
https://bugs.launchpad.net/bugs/1261873
** This bug has been marked a duplicate of bug 1261873
'net usershare' returned error 255
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The recent update of Munin (Ubuntu Security Notice USN-2090-1, Munin
1.4.6-3ubuntu3.4) still has this issue, so the patch had to be applied
manually (again).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
Has this been tested in 14.04 with libvirt 1.2.1? There was a bug when
merging libvirt 1.2.0 which should be resolved now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1180281
Title:
If I understand correctly, the new libvirt version I just pushed should
fix this bug. Please re-mark Confirmed if I am wrong and more patches
are needed.
status: fixreleased
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because
Override component to main
python-taskflow 0.1.2-0ubuntu3 in trusty: universe/python - main
python-taskflow 0.1.2-0ubuntu3 in trusty amd64: universe/python/optional/100%
- main
python-taskflow 0.1.2-0ubuntu3 in trusty arm64: universe/python/optional/100%
- main
python-taskflow 0.1.2-0ubuntu3 in
Override component to main
python-networkx 1.8.1-0ubuntu3 in trusty: universe/graphics - main
python-networkx 1.8.1-0ubuntu3 in trusty amd64: universe/graphics/optional/100%
- main
python-networkx 1.8.1-0ubuntu3 in trusty arm64: universe/graphics/optional/100%
- main
python-networkx
Override component to main
oslo.rootwrap 1.0.0-0ubuntu1 in trusty: universe/python - main
python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty amd64:
universe/python/optional/100% - main
python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty arm64:
universe/python/optional/100% - main
python-oslo.rootwrap
$ ./change-override -c main -S -y python-concurrent.futures
Override component to main
python-concurrent.futures 2.1.6-1ubuntu1 in trusty: universe/python - main
python-concurrent.futures 2.1.6-1ubuntu1 in trusty amd64:
universe/python/optional/100% - main
python-concurrent.futures 2.1.6-1ubuntu1
Public bug reported:
$ cat /proc/sys/fs/binfmt_misc/qemu-arm64
enabled
interpreter /usr/bin/qemu-arm64-static
flags:
offset 0
magic 7f454c46020101000200b7
mask ff00fe
$ ls -l /usr/bin/qemu-arm64-static
ls: cannot access /usr/bin/qemu-arm64-static:
** Changed in: qemu (Ubuntu)
Status: New = Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Just as a note, the new kernels are not only needed on LTS for hardware
enablement (and I'm guessing relatively few people need hardware
enablement in a VMware guest), but also to run Docker, which I suspect
affects more people (me included).
--
You received this bug notification because you are
I didn't look too much into this, but would it be possible to make lxc-
wait check the container's runlevel, and have a new booted state
(unless you want to change the meaning of RUNNING) become true once the
runlevel stops being unknown or N or S?
--
You received this bug notification because
** Also affects: gccgo-go (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gccgo-go (Ubuntu)
Importance: Undecided = High
** Summary changed:
- [MIR] juju-core, juju-mongodb
+ [MIR] juju-core, juju-mongodb, gccgo-go
--
You received this bug notification because you are a
** Description changed:
+ gccgo-go
+
+ Availability
+
+
+ In universe, available on all required architectures (x86, armhf, arm64,
+ ppc64el).
+
+ Rationale
+ -
+
+ 'go' build tool built using gccgo, avoiding the need to promote two
+ golang toolchains to Ubuntu main.
+
I'd prefer to wait until the system is fully booted (traditional
equivalent: rc2.d scripts are all complete), rather than just that
startup scripts are done (traditional equivalent: rcS.d scripts are all
complete).
It doesn't seem to be that waiting for everything to be started would be
much of
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
SRU for juju-core 1.16.3 into saucy: DONE
Work items for ubuntu-13.12:
[doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty:
DONE
Create juju-mongodb package from mongodb: DONE
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
SRU for juju-core 1.16.3 into saucy: DONE
Work items for ubuntu-13.12:
[doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty:
DONE
Create juju-mongodb package from mongodb: DONE
This bug was fixed in the package cinder - 1:2014.1~b2-0ubuntu1
---
cinder (1:2014.1~b2-0ubuntu1) trusty; urgency=low
[ James Page ]
* d/control: Add versioned dependency python-six = 1.4.1 (LP: #1259203).
* d/p/*: Refreshed.
[Chuck Short]
* New upstream release.
*
Ah... now I understand...
So this behavior is actually desirable. For example, to generate an
empty rootfs when creating a new OS template or App template. This way
the rootfs can be manually populated + tested before committing details
to the template.
Seems like having '-t none' might be good
** Changed in: nagios-plugins (Ubuntu)
Status: New = Triaged
** Changed in: nagios-plugins (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
Or maybe keep -t optional (so it works like always).
And generate the informational message if -t is missing or '-t none' is
specified.
As more + more people use LXC, having this simple message seems like a
life saver for newbies, like me.
Thanks for the info.
--
You received this bug
Here's a patch for this issue.
** Patch added:
0001-Remove-the-arm64-binfmt-misc-entry-on-upgrade-since-.patch
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+attachment/3960650/+files/0001-Remove-the-arm64-binfmt-misc-entry-on-upgrade-since-.patch
--
You received this bug
FWIW, I just tried the following:
sudo mknod /tmp/x1
sudo lxc-create -t ubuntu-cloud -n c1
sudo cat /var/lib/lxc/c1/config EOF
lxc.mount.entry = /tmp/x1 x1 none bind,create=file 0 0
EOF
sudo cat /var/lib/lxc/c1/rootfs/etc/init/x.conf EOF
description tell lxc monitor we are ready
author Serge
I'm sorry, this was the wrong bug!
status: triaged
** Changed in: libvirt (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Public bug reported:
Until 1.0.0beta2 I was using lxc-version command, beta3 seems to have
dropped it, leaving no way to programatically query for it:
* precise, saucy:
$ lxc-version
lxc version: 1.0.0.alpha1
$ lxc-cgroup --version
[ ... ERROR ]
* trusty (as of ~today):
$ lxc-version
I want it generic because I want adt-virt-lxc to work with any container
it is given, without having to tell the user to set up a special
container with special stuff in this special way.
Other tools will want this too. I have a simple generic trusty
container that I use to start-ephemeral (or
Quoting JuanJo Ciarlante (1273...@bugs.launchpad.net):
Public bug reported:
Until 1.0.0beta2 I was using lxc-version command, beta3 seems to have
dropped it, leaving no way to programatically query for it:
You can use lxc-start --version to get that information.
Also note that lxc-version
Quoting Robie Basak (1266...@bugs.launchpad.net):
I want it generic because I want adt-virt-lxc to work with any container
it is given, without having to tell the user to set up a special
container with special stuff in this special way.
Other tools will want this too. I have a simple
In this millenium the concept of finished booting becomes more and
more blurry anyway. We still have something like that with sysvinit if
you do an rc2.d/S99_something, but with upstart/systemd/udev rules this
already isn't accurate.
To use the least common denominator we could have a late rc2.d
On Tue, Jan 28, 2014 at 02:06:30PM -, Serge Hallyn wrote:
Each distro+release guest would need to be updated using its own init
system to inform us when the boot is complete, resulting in
container-specific changes to the rootfs which is something we want
to avoid.
I understand your
Today I installed 12.04.4 and all the above fixes didn't work on a
client machine.
Even if in some other thread (i think bug 958704) this was discouraged,
i added:
start wait-for-state WAIT_FOR=ypbind WAITER=autofs WAIT_STATE=running
after line 11 of /etc/init/autofs.conf, below the modprobe
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This bug should probably be fixed upstream, and then Ubuntu will pick it
up. Have you considered testing the latest upstream release of
spamassassin, and if affected then reporting the bug in the upstream
*** This bug is a duplicate of bug 1273407 ***
https://bugs.launchpad.net/bugs/1273407
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since this is the same issue as bug 1273407, I'll mark this as a
duplicate and open a libdbi task there.
** This bug has
Each distro+release guest would need to be updated using its own init
system to inform us when the boot is complete
LXC could provide a default implementation (like the above wait until
runlevel switches to 2 and then notify the caller), and then templates
could optionally provide a more refined
Adding libdbi task to close duplicate bug. Does this make gnucash
completely unusable? Does gnucash just need a rebuild against the latest
libdbi?
** Also affects: libdbi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
local provider bootstrapped ok:
juju status --debug
2014-01-28 15:02:33 INFO juju.provider.local environprovider.go:35 opening
environment local
2014-01-28 15:02:34 DEBUG juju state.go:75 waiting for DNS name(s) of state
server instances [localhost]
2014-01-28 15:02:34
Speaking as the upstream for LXC and package maintainer, the only way I
consider to be acceptable for this is the one Serge and I described by
adding a new socket owned by LXC which allows for a simple text based
communication between the container and its host. This protocol would
allow state
** Attachment added: machine-0.log
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1273712/+attachment/3960716/+files/machine-0.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Marking bug as invalid since there's a replacement command and our
existing documentation is correct with regard to the version currently
available in that release.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1273712
Title:
jujud dies on ppc64el architecture
To manage
Can you please provide logs, including dmesg, /etc/fstab, and other
supporting evidence of this change?
** Changed in: open-vm-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
While doing some libvirt tests, I experienced errors executing any iface-*
commands. After debugging, I found that libvirt uses netcf for these
operations. I tracked the problem down to a source-directory line in my
/etc/network/interfaces file. Once I removed that
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the default
** Also affects: gcc-4.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1273712
Title:
jujud dies on ppc64el architecture
To
Blueprint changed by Chuck Short:
Work items changed:
Work items for ubuntu-13.11:
Setup Trusty Icehouse in Openstack-CI: DONE
Setup Precise Icehouse in Openstack-CI: DONE
Write MIR report for httpretty: INPROGRESS
Write MIR report for mox3: INPROGRESS
Setup staging PPA for precise
** Changed in: websockify (Ubuntu Trusty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to websockify in Ubuntu.
https://bugs.launchpad.net/bugs/1231970
Title:
[FFe] nova-novncproxy requires
Switching to building with doko's preview 4.9 snapshot, this problem
goes away, which points to a bug in the libgo runtime.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1273712
** Branch linked: lp:ubuntu/trusty-proposed/qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1273654
Title:
qemu-arm64-static binfmt registration for non-existent binary
To manage
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1273205
Title:
/etc/init/ttyAMA0.conf causes endless tty
Blueprint changed by Ben Howard:
Work items changed:
Work items for ubuntu-13.12:
[james-page] File bug for openvswitch module move from extras to generic (bug
1253102): DONE
[utlemming] EARLY- gpt partition table early: DONE
[utlemming] EARLY- single image on ebs: TODO
[sforshee]
Alright, good enough for libdumbnet. I'd still like to see its test
suite fixed up and enabled. But if the cloud team is on top of things
(and they are subbed to bugs), we'll be able to fix any problems.
** Changed in: libdumbnet (Ubuntu)
Status: Incomplete = Fix Committed
--
You
Fixed in b2 upload for icehouse/trusty.
** Changed in: nova (Ubuntu Trusty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1062336
Title:
Canonical's Cloudware team is confident that we can support libdumbnet.
While it may have some rough edges, we have evaluated the package
extensively. We will take ownership for issues related to this package.
Additionally, libdumbnet is know at libdnet for SuSE/SLES and Fedora/Red
Hat/Centos.
I just got hinted at lxc-attach. With that, clients like adt-virt-lxc
can implement their own polling/waiting loop to wait until the runlevel
switches away from unknown/S, which is a lot better (and more generic)
than the current hackery that it's doing. I captured that in bug
1273725.
--
You
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1273654
Title:
qemu-arm64-static binfmt registration for non-existent binary
To manage notifications about this
Public bug reported:
After some initial testing of juju (with local provider) on ppc64el - we
need todo some work to fully enable this option.
1) LXC templates need to support ppc64el as a valid container arch
2) ubuntu-cloudimg-query is not avaliable on ppc64el
3) Juju is explicit in its
Maybe also worth to have a look at: https://bugs.launchpad.net/cloud-
archive/+bug/1246924
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1224517
Title:
please add glusterfs support
** Branch linked: lp:cloud-utils
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1273769
Title:
ppc64el enablement for juju/lxc
To manage notifications about this bug go to:
This looks fine, thanks! Approved.
** Changed in: ruby-rgen (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby-rgen in Ubuntu.
https://bugs.launchpad.net/bugs/1271857
Title:
[MIR]
** Tags removed: verification-done
** Tags added: verification-done-precise verification-done-quantal
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1262692
Title:
oops using
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1273769
Title:
*** This bug is a duplicate of bug 1246924 ***
https://bugs.launchpad.net/bugs/1246924
** This bug has been marked a duplicate of bug 1246924
qemu not built with GlusterFS support
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
python-sure no longer depends on python-steadymark so that task is
invalid and this MIR should be reevaluated.
python-sure (1.2.2-2) unstable; urgency=low
* Drops dependency on python-steadymark (Closes: #722507).
* Drops build-dependency on openstack-pkg-tools (and make it optional in
** Changed in: juju-core (Ubuntu)
Status: Incomplete = New
** Description changed:
gccgo-go
Availability
In universe, available on all required architectures (x86, armhf, arm64,
ppc64el).
Rationale
-
'go' build tool built using gccgo,
Override component to main
libdumbnet 1.12-4 in trusty: universe/libs - main
libdumbnet-dev 1.12-4 in trusty amd64: universe/libdevel/optional/100% - main
libdumbnet-dev 1.12-4 in trusty arm64: universe/libdevel/optional/100% - main
libdumbnet-dev 1.12-4 in trusty armhf:
Override component to main
open-vm-tools 2:9.4.0-1280544-5ubuntu2 in trusty: universe/admin - main
open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty amd64:
universe/admin/extra/100% - main
open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty arm64:
universe/admin/extra/100% - main
open-vm-dkms
(I have obviously no way of testing them, I'm expecting the lxc-ubuntu
template to work fine and the lxc-ubuntu-cloud template to fail horribly
due to missing images or missing support in ubuntu-cloudimg-query).
--
You received this bug notification because you are a member of Ubuntu
Server
Does this make gnucash completely unusable?
It affects all gnucash files stored as sqlite3.
I would asume that due to libdbi1 it might also affect gnucash files stored in
mysql or pgsql
GNUCash xml files seem not to be affected. Tested opening of an existing
gnucash xml, didn't test a new
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1273712
Title:
I have sent patches enabling arm64 and ppc64el for both the ubuntu and
ubuntu-cloud template, they should be in by the next 1.0 milestone (next
week or so).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Anyways ... please fill pull requests over there in https://github.com
/monitoring-plugins/monitoring-plugins, the upstream has changed it's
name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
Override component to main
libdumbnet 1.12-4 in trusty: universe/libs - main
libdumbnet-dev 1.12-4 in trusty amd64: universe/libdevel/optional/100% - main
libdumbnet-dev 1.12-4 in trusty arm64: universe/libdevel/optional/100% - main
libdumbnet-dev 1.12-4 in trusty armhf:
FYI lxc-start --version fails on precise (and saucy), which then
makes this check release dependent (and/or over existence of lxc-version
binary).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
(sorry, early comment posting) - ie querying the version now cross
releases would involve something alike:
version=$((lxc-version 2/dev/null || lxc-start --version) | sed 's/.*
//')
That 'sed' is to cope with lxc-version textual formatting, while lxc-
start --version shows it straight.
--
You
Public bug reported:
When installing php5-curl, the installation completes with succes, but
module isn't activated ( no symlink created in /etc/php5/conf.d or
/etc/php5/apache2/conf.d)
So restarting/reloading apache doesn't reload curl module.
If i manualy link curl.ini to conf.d, after apache
oh dear, this is what I was afraid of
On Wed, Jan 29, 2014 at 5:45 AM, Curtis Hovey cur...@canonical.com wrote:
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
--
You received this bug notification because you are subscribed
Doko, these seem up your alley
** Changed in: gccgo-go (Ubuntu)
Assignee: (unassigned) = Matthias Klose (doko)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
This bug was fixed in the package mysql-5.5 - 5.5.35-0ubuntu0.12.04.2
---
mysql-5.5 (5.5.35-0ubuntu0.12.04.2) precise; urgency=medium
[ Eduardo Damato ]
* Fix upstart script to account for datadir disk shortage (LP: #1121874)
-- Dave Chiluk chi...@canonical.com Tue, 21 Jan
This bug was fixed in the package mysql-5.5 - 5.5.35-0ubuntu0.12.10.2
---
mysql-5.5 (5.5.35-0ubuntu0.12.10.2) quantal; urgency=medium
[ Eduardo Damato ]
* Fix upstart script to account for datadir disk shortage (LP: #1121874)
-- Dave Chiluk chi...@canonical.com Tue, 21 Jan
** Changed in: pollen (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollen in Ubuntu.
https://bugs.launchpad.net/bugs/1246098
Title:
MIR: pollinate
To manage notifications about this
I am happy to carry out the work if pointed in the right direction.
Thanks,
Armando
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1273877
Title:
neutron-plugin-nicira should be
Public bug reported:
This is not a bug per se, but more like a feature request.
As per:
https://blueprints.launchpad.net/neutron/+spec/nicira-plugin-renaming
During the Icehouse timeframe the Nicira NVP plugin is being renamed to
VMware NSX plugin.
Canonical's packages for Neutron should
So yes, if you want the upstream version number in a generic way which
works with older and newer lxc, you'll need something like what you
listed above.
However, note that in most distributions, the upstream version number is
mostly irrelevant due to the amount of cherry-picking that's done, The
To fix this we need a python-tx-tftp package refresh from upstream.
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Milestone: None = 14.04
** Also affects: python-tx-tftp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: maas
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/1250491
Title:
pserv log is cluttered with tftp
Blueprint changed by Andres Rodriguez:
Work items changed:
Work items for ubuntu-13.12:
[andreserl] Modify packaging to allow HA deployments without pulling
unnecessary deps: DONE
Work items for ubuntu-14.01:
[andreserl] Charm maas-region: INPROGRESS
- [andreserl] Charm maas-cluster:
I have the exact same hang just trying to ssh into the host (remotely).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1254085
Title:
ssh fails to connect to VPN host - hangs at
The next time I removed the X forwarding ( ssh -X ) and it didn't hang
so X-forwarding (or the attempted access thereof) may play a role in
this bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Ok, I will send it on my next reboot.
For information, I was unable to suspend the laptop because it was awakening
some seconds later.
I made it working by using the following script (/etc/pm/sleep.d/20_zenbook) :
case ${1} in
hibernate|suspend)
# Unbind ehci_hcd for first device
Quoting David Favor (da...@davidfavor.com):
Correct. It appears the default template processing (default meaning no
template specified) seems like it could use a bit of work.
Ok, thanks.
Seems like specifying no template should either throw an error or create
some form of container that will
Public bug reported:
When I do a sudo apt-get dist-upgrade on trusty, i get this notice :
Processing triggers for libglib2.0-0:amd64 (2.39.3-0ubuntu4) ...
Aucune clé nommée « auto-launch » dans le schéma « com.ubuntu.update-notifier »
comme défini dans le fichier «
This bug was fixed in the package gthumb - 3:3.3.1-1
Sponsored for Jackson Doak (noskcaj)
---
gthumb (3:3.3.1-1) experimental; urgency=medium
[ Jackson Doak ]
* New upstream release
* Drop 25-fix_URL_in_About_and_copyright_year.patch, fixed upstream
* Drop
Hi Jérôme - thank you for reporting this issue. However, this is not a
bug in Upstart - Upstart simply records all output from the programs it
starts, so that output is entirely up to the programs being run, not
Upstart. The 2 examples you give do indeed prefix every line with their
program name,
Mailed linux-in...@vger.kernel.org with requested info.
Re a url I cannot see it when I search http://www.spinics.net/lists
/linux-input/ for Novatech touchpad but I suppose it takes a while to
be put in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@ Ray Velez , I feel this is not a satisfying solution (I didn't try)
because it is like a weakness in security settings.
My script is not working well: although it works fine as long as the computer
don't ends in sleep, when sleep happens then on resume then login the script
won't do the job.
@ Ray Velez , I feel this is not a satisfying solution (I didn't try)
because it is like a weakness in security settings.
My script is not working well: although it works fine as long as the computer
don't ends in sleep, when sleep happens then on resume then login the script
won't do the job.
*** This bug is a duplicate of bug 1261873 ***
https://bugs.launchpad.net/bugs/1261873
** This bug has been marked a duplicate of bug 1261873
'net usershare' returned error 255
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I sent the mail from a normal (as far as I know it is like gmail) Google
Apps email account but the mailer says the message containes HTML and
has rejected it:
Delivery to the following recipient failed permanently:
linux-in...@vger.kernel.org
Technical details of permanent failure:
Google
1 - 100 of 1010 matches
Mail list logo
