Public bug reported:
The systemd configuration for snapd to allow socket activation is in the
ubuntu-snappy package, but snapd is in the ubuntu-snappy-cli package.
This means you need install both packages to get snapd to "just work".
It seems like the systemd configuration should move into the
** Changed in: lightdm/1.14
Status: Fix Committed => Fix Released
--
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/1478087
Title:
Add libaudit support
To manage notifications
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
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/1478087
Title:
Add libaudit support
To manage notifications
Public bug reported:
Build with multiarch support
** Affects: libvirt (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Public bug reported:
Build with multiarch support
** Affects: bind9 (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Public bug reported:
Build with multiarch support
** Affects: netcf (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
Public bug reported:
Build with multiarch support
** Affects: libecap (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libecap in Ubuntu.
** Summary changed:
- ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3
+ Add libaudit support
--
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/1478087
Title:
** Changed in: lightdm/1.16
Status: Fix Committed => Fix Released
--
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/1478087
Title:
ISST-LTE: aureport -l couldn't print out
** Changed in: lightdm/1.10
Importance: Undecided => Medium
** Changed in: lightdm/1.10
Status: New => Triaged
** Changed in: lightdm/1.10
Milestone: None => 1.10.6
** Changed in: lightdm/1.10
Status: Triaged => Fix Committed
** Changed in: lightdm/1.14
Importance:
** Also affects: lightdm
Importance: Undecided
Status: New
** Also affects: lightdm/1.10
Importance: Undecided
Status: New
** Also affects: lightdm/1.2
Importance: Undecided
Status: New
** Also affects: lightdm/1.14
Importance: Undecided
Status: New
**
** Changed in: samba (Ubuntu)
Status: Triaged = Fix Released
--
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/1277432
Title:
Please update to samba 4.1.x from Debian/sid for
This one turns out to be more complex than it looks. Unfortunately due
to the way PAM works neither LightDM or the greeter know for sure the
context of the prompts that PAM sends. So they don't know they're being
asked for a username or something else in which whitespace might be
significant. It
Things worth checking:
a) If the LDAP server indicates in some way the correct unix username
for that account then make sure pam_ldap is correctly setting PAM_USER
it to this value (so other modules will use it).
b) If it is expected behaviour that the LDAP server ignores whitespace
then
** Changed in: samba (Ubuntu)
Status: Triaged = Fix Released
--
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/1043010
Title:
Update to 3.6.9
To manage notifications about this
** Summary changed:
- Update to 3.6.7
+ Update to 3.6.9
--
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/1043010
Title:
Update to 3.6.9
To manage notifications about this bug go to:
Public bug reported:
=
Release Notes for Samba 3.6.7
August 6, 2012
=
This is is the latest stable release of Samba 3.6.
Major enhancements in Samba 3.6.7
LightDM must run as root to do authentication correctly and be able to
create user session.
** Changed in: lightdm (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
This can't be fixed in the lightdm in Oneiric, as the architecture runs
the PAM code in the main process. We will change this for Precise, see
bug 881466.
** Changed in: lightdm (Ubuntu Oneiric)
Status: Confirmed = Invalid
** Changed in: lightdm (Ubuntu Precise)
Status: Confirmed
** Changed in: lightdm (Ubuntu)
Importance: Undecided = Medium
** Changed in: lightdm (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/830377
** Changed in: lightdm (Ubuntu)
Importance: Undecided = Low
** Changed in: lightdm (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/706354
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
sideshowmel: I'm not sure of the difference between your case and
Trifon's case. If it is different please generate keys and instructions
that reproduce it and post those to the upstream bug. Thanks.
** Changed in: gnome-keyring (Ubuntu)
Assignee: Robert Ancell (robert-ancell) = Ubuntu
rancor: Do you still have the same setup that you used to generate the
keys? If possible could you try and generate some new keys (ideally one
that fails and one that works) and attach them to this bug?
--
ssh are using ssh-userauth but ignores private key
24 matches
Mail list logo
