** Changed in: guidance (upstream)
Status: Confirmed = Fix Released
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
The password cannot be read anyway. And frankly, I think the steps you
describe is shooting yourself in the foot. You are deliberately creating
a race condition.
If we want to support all such cases where we want guidance to still
work even when a user simultaneously uses different tools for the
I have a fix committed for a similar bug to Marmule's. If this still
persists with 0.7.1 (once it's in the archives), please open another
bug. This one definitely is dealt with, and as Luka says, it creates
confusion.
** Changed in: kde-guidance (Ubuntu)
Status: Confirmed = Fix Committed
Closing as this is a bug upstream apparently.
** Changed in: kde-guidance (Ubuntu)
Status: Confirmed = Rejected
--
guidance-power-manager: dcop problem message when starting in a terminal
https://launchpad.net/bugs/64406
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
I cannot reproduce this problem here. Changing the password, and then
trying to use this in a new shell does work here. (Note that you have to
open the shell you try in after you close userconfig, otherwise PAM's
caching apparently still has the old password.
Setting the USER ID had been
