Public bug reported:
If you create a private instance of Tomcat 6 using the tomcat6-instance-
create script, it can be used as a Tomcat 6 server in Eclipse by
creating a new server runtime environment that has its installation
directory set to be your private instance directory.
However, the
A simple `dpkg-reconfigure openssh-server` also does the trick:
root@host:/# dpkg-reconfigure openssh-server
Creating SSH2 ECDSA key; this may take some time ...
Restarting OpenBSD Secure Shell server: sshd.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: autofs5 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
The fix mentioned by Dave above does work.
Michael Brown, the committer of the patch, has mentioned on the iPXE
community channels that this might actually be a GCC bug/regression and
that the patch is just a workaround.
--
You received this bug notification because you are a member of Ubuntu
Blueprint changed by Yolanda Robla:
Work items changed:
Work items:
[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 test dovecot
Blueprint changed by Yolanda Robla:
Work items changed:
Work items:
[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 test dovecot
The password you log in with, is used to decrypt/unwrap the key used to
decrypt the ecryptfs.
Would there not be a way of using the ssh secret key, used for login with ssh
to also unlock/unwrap the ecryptfs ?
Probably something that would have to be added to sshd.
--
You received this bug
Blueprint changed by Yolanda Robla:
Work items changed:
Work items:
[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 test dovecot
Hi,
(You probably knkow this, but to explain my request, the RDP connection
goes over the VM's virtual network card to talk directly to the VM.
Provided you have only a single VM running, 'gvncviewer localhost:0' (or
the equivalent with ssh port forwarding if you can't run X on the host)
talks to
Patch to show the distribution
** Patch added: openssh_distribution.patch
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1195342/+attachment/3716085/+files/openssh_distribution.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Related to:
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-server-app-banner-updates
We need to show the Ubuntu distribution, instead of showing the Debian
one, for the Ubuntu packages.
** Affects: openssh (Ubuntu)
Importance: Low
Assignee: Colin
Unfortunately I don't have any hardware to reproduce this with.
Could you please:
1. Attach /var/log/libvirt/qemu/w.log
2. Try running this vm with kvm by hand as per
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM ?
(i.e. the kvm command in step 6, something like kvm
Applied, thanks.
** Changed in: openssh (Ubuntu)
Importance: Undecided = Low
** Changed in: openssh (Ubuntu)
Status: New = Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
You received this bug notification because you are a
** Description changed:
My precise client is member of a Windows Domain. A domain user can login
using samba/winbind without problem in tty and via lightdm if the user
password is ok.
If the password is expiring a domain user logs in correctly via TTY,
with a message Your password is
The attachment openssh_distribution.patch seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the patch flag from the attachment, remove the
patch tag, and
Hello Juerg, or anyone else affected,
Accepted python-boto into raring-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/python-
boto/2.3.0-1ubuntu0.13.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Juerg, or anyone else affected,
Accepted python-boto into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/python-
boto/2.2.2-0ubuntu3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Juerg, or anyone else affected,
Accepted python-boto into quantal-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/python-
boto/2.3.0-1ubuntu0.12.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Changed in: samba (Ubuntu Oneiric)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/900391
Title:
IE9 on Windows 7 cannot download files to samba 3.5.11 share
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/python-boto
/precise-proposed
** Branch linked: lp:~ubuntu-branches/ubuntu/quantal/python-boto
/quantal-proposed
** Branch linked: lp:~ubuntu-branches/ubuntu/raring/python-boto/raring-
proposed
--
You received this bug notification because
Pieter, the private key is never made available in any form to the sshd
server. The server only has access to the public portion of the key in
~/.ssh/authorized_keys. You would probably not want a file on the
filesystem to serve as the secret key for your encrypted directory, as
that defeats the
Hello James, or anyone else affected,
Accepted ceph into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/ceph/0.56.6-0ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Setting verification-failed to indicate we'd like 1.0+noroms-0ubuntu14.9
dropped. 1.0+noroms-0ubuntu14.10 is in Unapproved, and has the better
fix.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:ubuntu/raring-proposed/ceph
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1194166
Title:
[SRU] Ceph 0.56.6 point release update
To manage notifications about
Hello Steve, or anyone else affected,
Accepted network-manager into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/network-
manager/0.9.4.0-0ubuntu4.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
@Will - the version number you mentioned, 0.12.4+bzr477-0ubuntu3, is no
the one needing SRU verification. Was that a typo?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1174148
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package openldap - 2.4.31-1ubuntu2.1
---
openldap (2.4.31-1ubuntu2.1) raring-proposed; urgency=low
* Avoid deadlocks in back-bdb that truncate slapcat output (LP: #1185908):
- d/patches/bdb-deadlock.patch: Patch copied from Debian #673038
-- Ryan
This bug was fixed in the package openldap - 2.4.28-1.1ubuntu4.3
---
openldap (2.4.28-1.1ubuntu4.3) precise-proposed; urgency=low
* Avoid deadlocks in back-bdb that truncate slapcat output (LP: #1185908):
- d/patches/bdb-deadlock.patch: Patch copied from Debian #673038
-- Ryan
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.06:
[james-page] Enable google-perftools on armhf: DONE
[james-page] Upload cuttlefish (0.61.2) to saucy: DONE
[james-page] Upload cuttlefish to the havana cloud archive: DONE
[james-page] Upload cuttlefish
This bug was fixed in the package chromium-browser -
28.0.1500.52-0ubuntu1.12.10.2
---
chromium-browser (28.0.1500.52-0ubuntu1.12.10.2) quantal-security; urgency=low
[Chad MILLER]
* New stable release 28.0.1500.52
* New stable release 28.0.1500.45
* New stable release
This bug was fixed in the package chromium-browser -
28.0.1500.52-0ubuntu1.13.04.2
---
chromium-browser (28.0.1500.52-0ubuntu1.13.04.2) raring-security; urgency=low
[Chad MILLER]
* New stable release 28.0.1500.52
* New stable release 28.0.1500.45
* New stable release
This bug was fixed in the package chromium-browser -
28.0.1500.52-0ubuntu1.12.04.2
---
chromium-browser (28.0.1500.52-0ubuntu1.12.04.2) precise-security; urgency=low
[Chad MILLER]
* New stable release 28.0.1500.52
* New stable release 28.0.1500.45
* New stable release
Hello Ben, or anyone else affected,
Accepted upstart into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/upstart/1.8-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
not knowing about security updates are a security issue; changed the but
type
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/1031680
Title:
Public bug reported:
when starting instances on azure, there is a fair chance (seems more
likely for some users thanothers) that the instance will fail to reach
provisioned state.
I do not have a a good guess as to why this is.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: walinuxagent
as I'm trying to debug this instance that failed for me, and then came up after
a 'vm restart', there is no indication that / was ever mounted RW the first
time. Ie, there is no evidence in /var/log of *anything* having run.
cloud-init starts on mounted MOUNTPOINT=/
and logs pretty much
given my previous comment, i would have suspected that there was disk or kernel
failure.
however, ssh-keyscan seemed to indicate ssh was running:
$ ssh-keyscan us-west-1.cloudapp.net
# us-west-1.cloudapp.net SSH-2.0-OpenSSH_6.1p1 Debian-4
Connection closed by 137.135.115.232
--
You received
Public bug reported:
Hi, it seems that walinux-agent may be run during the build process. I
suspect this because when I got into an instance that was restarted and
came up after showoing bug 1195524, I saw timestamps in
/var/log/walinux.
Heres an example:
2013/06/21 04:33:47 WARNING:Moved
the solution here is to block jobs from running on 'apt-get install'.
the build process for cloud-images does this.
the way to prevent is to put something like this in /usr/sbin/policy-
rc.d (taken from VMBuilder/plugins/ubuntu/templates/nostart-policy-
rc.d.tmpl )
while true; do
case $1 in
You can get kdump working in Azure (not that you really need it for this)
with the attached patch.
Ref: http://support.microsoft.com/kb/2858695
On Thu, Jun 27, 2013 at 8:01 PM, Scott Moser smo...@ubuntu.com wrote:
given my previous comment, i would have suspected that there was disk or
This bug was fixed in the package openssh - 1:6.2p2-5
---
openssh (1:6.2p2-5) unstable; urgency=low
[ Colin Watson ]
* Document consequences of ssh-agent being setgid in ssh-agent(1); see
#711623.
* Use 'set -e' rather than '#! /bin/sh -e' in maintainer scripts and
42 matches
Mail list logo
