[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2016-03-28 Thread Martin Wimpress
If the power settings are configured to suspend when the laptop lid is closed, the computer will suspend and lock. Raising the lid will wake the laptop and display the unlock screen. Simply suspending the computer will wake without being locked. The behaviour was tested on Ubuntu MATE 16.04 and is

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2016-03-02 Thread Martin Wimpress
Can someone confirm if this is still a problem in 16.04 daily images. This should be fixed. ** No longer affects: ubuntu-mate ** Changed in: mate-screensaver (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is sub

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2016-01-29 Thread Martin Wimpress
** Changed in: ubuntu-mate Assignee: abhilash (abhilashdesai123) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460442 Title: Ubuntu Mate 15.04 does not allow to set a password

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-11-14 Thread abhilash
** Changed in: ubuntu-mate Assignee: (unassigned) => abhilash (abhilashdesai123) ** Changed in: ubuntu-mate Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/14604

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-09-09 Thread Marc Deslauriers
** Changed in: ubuntu-mate Status: New => Triaged ** Changed in: mate-screensaver (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460442 Title: Ubuntu M

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-08-25 Thread Martin Wimpress
** Changed in: mate-screensaver (Ubuntu) Status: Incomplete => New ** Also affects: ubuntu-mate Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460442

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-08-21 Thread George
Interestingly I did not have the same problem, ie. locking works fine for me. I'm using xps 13 9343. However, when I enable locking, the login/credentials window turns white, causing me to unable to log back in after suspending. -- You received this bug notification because you are a member of

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-08-14 Thread longboringusername
If you go to: System - Preferences - Look and Feel - Screensaver Check the boxes: "Activate screensaver when computer is idle" and "Lock screen when screensaver is active" You will get a password prompt after coming out of Suspend. I'm not sure why the option is there or why it works that way but

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-06-20 Thread ullix
I am sorry but I don't have the faintest idea how to "communicate with upstream" and what a "debdiff" is. The problem should be obvious and easily reproducible by just using Ubuntu Mate 15.04, unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-06-19 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is availabl