Installed a pristine trusty system, configured lib{nss,pam}-ldapd, and
confirmed that updating to nslcd 0.8.13-3ubuntu1 from trusty-proposed
allows LDAP users to unlock the Unity lockscreen.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
*** This bug is a duplicate of bug 658723 ***
https://bugs.launchpad.net/bugs/658723
** This bug is no longer a duplicate of bug 568401
Indicator applets open when pressing S or M key via NX, VNC
** This bug has been marked a duplicate of bug 658723
VNCServer - Super modifier is always
*** This bug is a duplicate of bug 658723 ***
https://bugs.launchpad.net/bugs/658723
** This bug has been marked a duplicate of bug 658723
VNCServer - Super modifier is always applied
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
Setting idle-delay does disable the screensaver, but at the expense of
having my session no longer marked idle at all. So for example,
configuring logind to suspend or shutdown an idle computer is no longer
effective. IMO this conflates two different things: whether or not the
session is marked
** Changed in: unity (Ubuntu)
Status: Incomplete = Invalid
** Changed in: unity
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
Public bug reported:
GNOME Screensaver allowed me to disable screen blanking while still
having the desktop marked idle if I don't touch it for some time. Unity
allows the idle-activation-enabled key for schema compatibility but
does not use it at all; the UI for disabling screen blanking
** Tags added: vivid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1237554
Title:
compiz crashed with SIGSEGV in _wordcopy_fwd_aligned()
Status in
I think the indicator-keyboard code for migrating settings is
responsible, at least for the layout setting. I worked around it by
writing a gschema override for org.gnome.libgnomekbd.keyboard.layouts,
the old location where settings are migrated from, instead of
Hello sponsors,
Please consider uploading the attached nslcd patch to trusty-proposed to
resolve this bug. Thank you!
** Description changed:
+ SRU justification:
+
+ [Impact]
+
+ * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able
+ to unlock the Unity lockscreen. Utopic
Hi,
Grzegorz Gutowski (gzegzol) wrote on 2014-04-29: Without suid it seems
that call (with correct username) to getspnam in function
get_account_info in file passverify.c in pam/modules/pam_unix returns
NULL. I don't understand this behaviour. I wrote a simple c program that
calls getspnam and it
Ahh, right. So this is almost certainly the change that fixed it for
utopic:
- nslcd will now return partial shadow information to non-root users to
avoid authorisation problems with setgid shadow authentication helpers
with some PAM stacks (closes: #706913)
I bet backporting
This seems to be fixed in later releases. Using lib{nss,pam}-ldapd and
nslcd, with no custom configuration beyond dpkg-reconfigure nslcd, I
experience this bug in trusty, but not in utopic or vivid.
Also, in trusty I do not experience it when using alternative lockers
such as gnome-screensaver or
Public bug reported:
On a system with a GeForce 6150SE integrated GPU, opening and closing
the Dash a few times results in moderate or severe corruption, and
eventually a complete lockup where the display is completely scrambled
in a repeating pattern. When the lockup happens, the system stops
** Changed in: accountsservice (Ubuntu)
Assignee: aminebend (alg-amine) = (unassigned)
** Changed in: accountsservice (Ubuntu Precise)
Assignee: aminebend (alg-amine) = (unassigned)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
Works for me as well on the current daily live image.
** Changed in: unity (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
Released
** Changed in: indicator-datetime (Ubuntu)
Status: In Progress = Fix Released
** Changed in: indicator-datetime
Assignee: Ryan Tandy (rtandy) = (unassigned)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime
://bugs.launchpad.net/indicator-datetime/+bug/976100/+attachment/3938390/+files/indicator-datetime_0.3.94-0ubuntu2.1.debdiff
** Changed in: indicator-datetime
Assignee: (unassigned) = Ryan Tandy (rtandy)
** Changed in: indicator-datetime
Status: New = In Progress
--
You received this bug notification
** Also affects: indicator-datetime
Importance: Undecided
Status: New
** Branch linked: lp:~rtandy/indicator-datetime/lp976100
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions:
** Changed in: accountsservice (Ubuntu)
Assignee: Marcus Colla Magnus O.R. (collamagnus-or) = (unassigned)
** Changed in: accountsservice (Ubuntu Precise)
Assignee: Marcus Colla Magnus O.R. (collamagnus-or) = (unassigned)
--
You received this bug notification because you are a member
Hi Marcus,
On Wed, Dec 18, 2013 at 12:09 PM, Marcus Colla Magnus O.R.
collamagnus...@gmail.com wrote:
** Changed in: accountsservice (Ubuntu Precise)
Status: Fix Committed = Fix Released
I don't think this is correct. The fixed package is still in
precise-proposed and hasn't been
The problem seems to go away after backporting accountsservice from
quantal.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Fixing the double free of user-language as per
http://cgit.freedesktop.org/accountsservice/commit/?id=4399a03316bfc2b5a6f666b0606e5eece167d44a
seems to be sufficient to fix this. I'll test this a few more times to
convince myself of that.
** No longer affects: gdm (Ubuntu)
--
You received this
I reported bug #1255356 separately and discovered the same double free
as the cause. I have verified that accountsservice from precise-proposed
fixes the bug reported by Wookey and fixes the bug I reported as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
*** This bug is a duplicate of bug 1004515 ***
https://bugs.launchpad.net/bugs/1004515
** This bug has been marked a duplicate of bug 1004515
segfault in accounts-daemon when logging in / gdm crash if user account is
added or deleted
--
You received this bug notification because you are
** Changed in: accountsservice (Ubuntu)
Assignee: shan (shan40) = (unassigned)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1004515
Title:
Still present in Saucy.
** Summary changed:
- Time and Date Settings don't load in Ubuntu Precise/Quantal/Raring with Gnome
Classic
+ Time and Date Settings don't load in Ubuntu Precise and newer with Gnome
Classic
** Tags added: saucy
--
You received this bug notification because you are a
26 matches
Mail list logo
