[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Changed in: unity/7.2 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Released Status in unity-greeter source package in Trusty: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Changed in: unity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Released Status in unity-greeter source package in Trusty: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Released Status in unity-greeter source package in Trusty: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
This bug was fixed in the package unity - 7.2.4+14.04.20141217-0ubuntu1 --- unity (7.2.4+14.04.20141217-0ubuntu1) trusty; urgency=medium [ Andrea Azzarone ] * Share lockscreen password between screens (lp: #1308540) * Allow a distinct pam config file for greeter and for lock-screen. (lp: #1305440) * Add an arrow activator in the lockscreen. (lp: #1332509) * Make sure GetScreenGeometry returns the correct value (lp: #1374785). * unmapped all windows prior to shutdown (lp: #1370017) (lp: #1375271) [ Brandon Schaefer ] * fix tooltip for the Show Desktop / Restore Windows icon in the Alt-Tab switcher (lp: #1237132) * Use CONFIG instead of CACHE to store the first_run.stamp (lp: #1328677) [ Eleni Maria Stea ] * LayoutSystem: make sure the exposed open windows are displayed in the preserved order (lp: #1349281). [ handsome_feng ] * added support for getting the distro name from /etc/os-release (lp: #1329584) [ Iain Lane ] * When grabbing keys, try prefixing XF86 if the key isn't found. GNOME gives us unprefixed keys sometimes (lp: #1302885). [ Marco Trevisan (Treviño) ] * make the Launcher icon count badge width depend on the text value width and scaling (lp: #1353070) (lp: #1354498) (lp: #796527) (lp: #1066971) (lp: #1361713) * DecoratedWindow: make edges independent from borders and properly update them on actions change (lp: #1276177), (lp: #1299741), (lp: #1301776), (lp: #1324104), (lp: #1364225), (lp: #1373695) * Lockscreen: scale the UI elements based on current monitor scaling (lp: #1292218) * UnityScreen: when filtering out windows in spread, make sure we unscale them (lp: #1316265). * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (lp: #1384910) (lp: #1384958) (lp: #1385285) * SearchBar, ActionButtons, IconRenderer: include the font scaling when scaling textual items (lp: #1332947) (lp: #1361751) (lp: #1362162) (lp: #1362346). * ApplicationLauncherIcon: make sure we close the dash if DnD is accepted and the application window is about to be focused (lp: #1350331). * SwitcherView: set progress on icon render args (lp: #1361679). * LockScreenController: wait for the primary shield to get the grab before setting the session locked (lp: #1368427) (lp: #1371764). * added decorations to windows in non-focused workspaces (lp: #1383468) [ Stephen M. Webb ] * updated the unity(1) manpage to match the actual command (lp: #1059275) * bumped package version to match upstream [ Marco Trevisan (Treviño) ] * Preparing for unity 7.2.4 -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 17 Dec 2014 20:52:10 + ** Changed in: unity (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Released Status in unity-greeter source package in Trusty: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Committed Status in unity-greeter source package in Trusty: New Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Tags removed: verification-needed ** Changed in: unity-greeter (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Committed Status in unity-greeter source package in Trusty: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
Hello Franck, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20141217-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity-greeter (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Committed Status in unity-greeter source package in Trusty: New Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
Attached debdiff between trusty-updates and SRU. ** Branch unlinked: lp:~unity-team/unity/trusty-1305440 ** Description changed: + [Impact] + It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome- keyring for example. + + [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. + + [Regression Potential] + + An additional configuration point could allow a system to be + misconfigured for reduced security. The default configuration is to use + the same PAM stack as the LightDM login process so no new regression is + introduced without user modification. + + [Other Info] + + The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where + it has been in production use for a few months and appears stable. ** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and unity_7.2.4+14.04.20141217-0ubuntu1 https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1305440/+attachment/4289402/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Branch linked: lp:~unity-team/unity/7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Bug description: It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Branch linked: lp:~unity-team/unity/trusty-1305440 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Bug description: It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Changed in: unity/7.2 Milestone: 7.2.3 = 7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Invalid Bug description: It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
This bug was fixed in the package unity - 7.3.1+14.10.20140811-0ubuntu1 --- unity (7.3.1+14.10.20140811-0ubuntu1) utopic; urgency=medium [ Michal Hruby ] * Split out dconf schemas into separate package [ Brandon Schaefer ] * Make sure we check if the Quicklist or Alt+F1 key nav is open (so we can close them) Bore checking if something as a WM grab. As we cant open the hud is in Quicklist or KeyNav anymore. (LP: #1353167) [ Stephen M. Webb ] * Changed log message on failure to open xpathselect library from an error to a warning. The xpathselect library is used for introspection during automated test runs. It is not an error for this library to be unavailable in normal successful operating conditions. (LP: #1345296) [ Andrea Azzarone ] * Add an arrow activator in the lockscreen. (LP: #1332509) * Allow a distinct pam config file for greeter and for lock-screen. (LP: #1305440) [ Marco Trevisan (Treviño) ] * Autopilot, Switcher: use correct right/left scroll buttons for next/prev mouse selection (LP: #1353383) * UScreen, PanelService: get monitor at position, ignoring pre- multipled Gdk scale factor Get monitor position based on absolute coordinates, ignoring the pre-multipled scaling factor that Gdk applies to all the monitor sizes. In this way we get the proper monitor index for absolute coordinates, independently from the scaling factor. (LP: #1351591) * ApplicationLauncherIcon: make sure we close the dash if DnD is accepted And we're about to focus the application window(s) (LP: #1350331) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 11 Aug 2014 12:31:11 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Invalid Bug description: It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen
** Changed in: unity/7.2 Milestone: 7.2.2 = 7.2.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Invalid Bug description: It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
