[Bug 1530743] Re: Package samba failed to upgrade

2016-01-03 Thread Kapitan
Probably a missing "sudo rm /etc/init.d/samba" in the pre-removal script. -- 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/1530743 Title: Package samba failed to upgrade To manage noti

[Bug 1530743] [NEW] Package samba failed to upgrade

2016-01-03 Thread Kapitan
Public bug reported: Description:Ubuntu 14.04.3 LTS Release:14.04 Upgrading to 16.04 samba: Installed: 2:4.1.20+dfsg-1ubuntu5 Candidate: 2:4.1.20+dfsg-1ubuntu5 Version table: *** 2:4.1.20+dfsg-1ubuntu5 0 500 http://ca.archive.ubuntu.com/ubuntu/ xenial/main amd64 Packa

[Bug 1527374] Re: privilege escalation on attach through ptrace

2016-01-03 Thread Stéphane Graber
** No longer affects: lxd (Ubuntu) -- 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/1527374 Title: privilege escalation on attach through ptrace To manage notifications about this bug go

[Bug 1331214] Re: MAAS (amttool) cannot control AMT version > 8

2016-01-03 Thread Akash Chandrashekar
Update Hardware Tested : Intel NUC Model:NUC5i5MYHE with VPro extension running AMT Version: 10.0.45 MAAS Version : 1.8.3+bzr4053-0ubuntu1 (trusty1) Unit properly can be commissioned in MAAS and is in ready state, however "power on" function does not work. -- You received this bug notificat

[Bug 1331214] Re: MAAS (amttool) cannot control AMT version > 8

2016-01-03 Thread Akash Chandrashekar
Tested with: Intel NUC Model:NUC5i5MYHE with VPro extension running AMT Version: 10.0.45 To get this working properly with MAAS Version 1.8.3+bzr4053-0ubuntu1 (trusty1) , I had to also install the wsmancli package, which MAAS appears to now take advantage of to properly control the device. This

[Bug 1530674] [NEW] Trouble unlocking a password-locked private key

2016-01-03 Thread Simon Déziel
Public bug reported: My VPN configuration references a RSA private key that is password locked. When I manually start the VPN connection, the systemd wrapper doesn't properly prompt for the password: $ sudo systemctl start openvpn@cameleon Broadcast message from root@simon-laptop (Sun 2016-01-0

[Bug 1256279] Re: Typo in Package: ceilometer-agent-central: "aquire"

2016-01-03 Thread Pascal De Vuyst
https://translations.launchpad.net/ddtp-ubuntu/xenial/+pots/ddtp-ubuntu- main/fr/14775/+translate ** Changed in: ddtp-ubuntu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer in Ubu

[Bug 1524069] Re: [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes

2016-01-03 Thread Serge Victor
The bug persists in kernel 4.3.0-2-generic #11-Ubuntu. @Mike - thanks for a workaround, it works, indeed :-) --cpu=host-model-only for virt-manager. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpa

[Bug 296841] Re: root account has ! as default password

2016-01-03 Thread undefined
I respectfully disagree with Jamie Strandboge regarding his statement: "ssh public key logins are not disabled by the use of '!'." OpenSSH, when *not* relying on PAM for account checking (ie "UsePAM no"), will itself consider an account "locked" if the user's password field in the shadow file is p