Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
I'm seeing this too, strace show it spinning on:
select(8, [0 3 6 7], [], [6], NULL) = 1 (in [0])
recvmsg(0, 0x7fffdb2aa6d0, 0) = -1 ENOTSOCK (Socket operation on non-socket)
accept(0, 0, NULL) = -1 ENOTSOCK (Socket operation on non-socket)
select(8, [0 3 6 7], [], [6], NULL) = 1 (in [0])
Unlike the l3 agent package the vpn agent package is lacking the
/etc/init/neutron-l3-agent.conf file required to start the l3 agent.
Does the vpn agent provide a superset of functionality which means that
if you're already running the vpn agent you don't need to separately run
the l3 agent? Or
On 01/05/14 07:45, Colin King wrote:
I'm seeing this too, strace show it spinning on:
select(8, [0 3 6 7], [], [6], NULL) = 1 (in [0])
recvmsg(0, 0x7fffdb2aa6d0, 0) = -1 ENOTSOCK (Socket operation on non-socket)
accept(0, 0, NULL) = -1 ENOTSOCK (Socket operation on non-socket)
select(8, [0
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
--
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/1314686
Title:
Please add support for utopic
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
From a packaging perspective, all that we can do here is the MIR, right?
** Changed in: maas (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1314629
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Confirmed in Trusty. This needs checking on Debian, and perhaps
submission to the Debian BTS.
Marking Importance: Medium since there's an easy workaround available
(modify /etc/init.d/nginx).
** Changed in:
** Changed in: net-snmp (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1314760
Title:
first hrSWInstalledIndex is 0, should be 1
To
I've just noticed this bug.
IMHO, /usr/share/nginx/www/ should never be used to actually serve
files. To serve static files, the document root should be changed.
Somewhere under /srv is suitable under the FHS.
It would be nice if this were documented better somehow (I don't know
how), but this
IMHO, /usr/share/nginx/www/ should never be used to actually serve
files.
Apart from the default ones provided by packaging, of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like this fix is suitable for an update to Trusty, assuming
that LDAP auth does not work at all without it. In order to do this,
we'll need a test case that has exact to reproduce the problem so that
we
test case that has exact to reproduce
That has exact steps, that is.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1313848
Title:
AuthnProviderAlias does not work w/ authnz_ldap
Thank you for your report.
If you're trying to downgrade from 5.6 to 5.5, then this is not an
automatically supported path, will require manual intervention as you
discovered, and thus is not a bug. See the 14.04 release notes:
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#MySQL
If you're
I see the same error and same /proc/cmdline args while commissioning a
new maas setup. Rerunning the sudo maas-export-pxe-files does not help
in my case. I am on 12.0.4 LTS
vmdc-admin@ics3-ubuntu3:/var/log/maas$ dpkg -l | grep maas
ii maas
Can't we do this sanely instead of making the intended-to-be-user-editable
template file have such madness as :
{{if node.split_arch()[0] in {'i386', 'amd64'} }}
Why not make 'arch' actually mean 'arch' and 'subarch' mean 'subarch' as
variables available to the template.
--
You received
in response to comment 5, i'm not sure why the cache in the image
wouldn't have had either been updated or have had sane values built in.
that could be an image-build thing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
I'd never tested this, but I thought that the 'saucy-netboot' entry
kernel and initramfs at [1] would default to intstalling the linux-
generic-lts-saucy.
Now, it still may, as we're explicitly asking in the preseed listed
above to install the linux-server.
2 things are then possible:
a.) ew can
Public bug reported:
I have been using this laptop with ubuntu since day 0. It was working OK.
Did clean install ubuntu 14.04, now 90% of the times I does not resume.
I also noted that I don't have any option to hibernate (don't know if
that might be related)
NO envidia or any special hardware.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pm-utils (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
** Changed in: openssh (Ubuntu Saucy)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: openssh (Ubuntu Trusty)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: openssh (Ubuntu Saucy)
Status: New = Triaged
** Changed in: openssh (Ubuntu Trusty)
** Changed in: migrate (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to migrate in Ubuntu.
https://bugs.launchpad.net/bugs/1290817
Title:
Please merge migrate 0.8.5-1 (main) from
Public bug reported:
When using the cgroup manager, if an unprivileged user starts a
container from one login session, then ssh's back in and tries lxc-
attach, that will fail.
The workaround for this is simply to start a container under screen or
tmux, then re-attach to that session to
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1274720
Title:
[SRU] screen server process can be crashed by
When I tried the same thing with git master (latest) I get a different error:
qemu_chr_fe_claim_no_fail: error chardev (null) already used
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
This shows up in Trusty in a different location
Setting up krb5-config (2.3) ...
Use of uninitialized value $admin in string eq at
/var/lib/dpkg/info/krb5-config.config line 171, STDIN line 19.
[more output]
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I have the same problem as reported in the original post of this bug ...
except ... my use case is different.
I created an OpenStack instance of ubuntu 14.04.
I installed juju on that instance and configured it for Local Provider (re
lxc).
I then bootstrapped and deployed Juju-GUI which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logwatch (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
Hello James, or anyone else affected,
Accepted vsftpd into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/vsftpd/3.0.2-1ubuntu2.14.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
sysadmin@Ubuntu-4600:~$ sudo apt-get install samba
[sudo] password for sysadmin:
Reading package lists... Done
Building dependency tree
Reading state information... Done
samba is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not
Public bug reported:
proposing a SRU for trusty, changing the ruby default from 1.9.1 to 2.0,
and stop building the tcltk ruby bindings.
rationale: trusty currently has two ruby versions and two Tcl/Tk
versions in main. reducing these one of each lowers the maintenance
burden for the LTS.
The
Well my env has active directory but let me take a look at openldap see
how hard it would be to setup in some basic fashion.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1313848
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ruby-defaults (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby-defaults in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: puppet (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby-defaults in Ubuntu.
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=10490
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1310919
Hello styro, or anyone else affected,
Accepted samba into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-
1ubuntu2.14.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Also affects: ruby-defaults (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: puppet (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ruby-defaults (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: puppet (Ubuntu Trusty)
I believe I just tripped this bug; I compressed some qcow2 images using
this:
for f in sec-{lucid,precise,quantal,saucy,trusty}-{amd64,i386} ;
do echo $f ;
qemu-img convert -s pristine -p -f qcow2 -O qcow2 $f.qcow2 reclaimed.qcow2 ;
mv reclaimed.qcow2 $f.qcow2 ;
virsh snapshot-delete $f
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
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/1292234
*** This bug is a duplicate of bug 1292234 ***
https://bugs.launchpad.net/bugs/1292234
Public bug reported:
After compacting qcow2 filesystem images some of them are no longer
bootable.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu 2.0.0~rc1+dfsg-0ubuntu3.1
** Changed in: samba
Status: Unknown = Confirmed
** Changed in: samba
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1310919
Title:
FYI, I periodically use and follow the same procedure that Seth
described (in fact, I did it yesterday) and had no problems with qemu
1.5.0+dfsg-3ubuntu5.4 (which I've apt pinned since reporting this bug).
** Description changed:
The security team uses a tool
** Description changed:
proposing a SRU for trusty, changing the ruby default from 1.9.1 to 2.0,
and stop building the tcltk ruby bindings.
rationale: trusty currently has two ruby versions and two Tcl/Tk
- versions in main. reducing these one of each lowers the maintenance
+ versions in
** Changed in: juju-core
Importance: Critical = High
--
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/1313785
Title:
Can't SSH with juju ssh command to EC2 instance.
To manage
No matter what you do here, you can't demote anything to universe in a
released series. The release pocket is set in stone.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby-defaults in Ubuntu.
Am 02.05.2014 00:43, schrieb Adam Conrad:
No matter what you do here, you can't demote anything to universe in a
released series. The release pocket is set in stone.
references?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Summary changed:
- open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed
to build
+ open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed
to build [make[1]: arm-xilinx-linux-gnueabi-gcc: Command not found]
--
You received this bug notification
You have been subscribed to a public bug:
The upstream packages for keystone in Ubuntu 14.04 seem to be missing
the init.d upstart scripts, so the post install script fails, but the
package install is marked as successful. This seems like a rather large
omission.
apt-get install keystone
** Project changed: keystone = keystone (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse ubuntu packaging
To manage
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
screen not freezing up nor turning zombie, but i got the error described
above. it happens reliably. i just manufactured Ubuntu 14.04. when
exiting using ^A^D it does exactly what this bug describes. my
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
also, if i use screen directly, e.g. replace byobu-screen with just
screen, it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
52 matches
Mail list logo
