[Bug 300667] Re: Shutting down after oem-config runs requires password
not an issue anymore ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/300667 Title: Shutting down after oem-config runs requires password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/300667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300667] Re: Shutting down after oem-config runs requires password
** Package changed: oem-config (Ubuntu) = ubiquity (Ubuntu) ** Tags added: oem-config -- Shutting down after oem-config runs requires password https://bugs.launchpad.net/bugs/300667 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300667] Re: Shutting down after oem-config runs requires password
I don't think I can easily proceed with debugging this until after beta, when the fix for bug 275432 lands. -- Shutting down after oem-config runs requires password https://bugs.launchpad.net/bugs/300667 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300667] Re: Shutting down after oem-config runs requires password
I have certainly reproduced this in the past, but my most recent attempt failed to reproduce it. I wonder if this is a race condition. My speculation would be that the ConsoleKit session doesn't get closed until D-BUS notices that its peer holding the session has gone away, and in some cases oem-config-firstboot manages to get in first and call deluser. That explains why deluser sometimes fails but probably doesn't directly explain why shutdown prompts, since that's probably quite a bit later in wallclock time. Perhaps once deluser has been called (IIRC it typically deletes the actual user but fails to delete its home directory), CK is unable to deregister the session? We'd need to catch it in some semblance of action. I think this may be easier to reproduce on the server CD; that's certainly where I've seen deluser failing frequently. One could use ck- list-sessions to look at what CK thinks is going on. -- Shutting down after oem-config runs requires password https://bugs.launchpad.net/bugs/300667 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300667] Re: Shutting down after oem-config runs requires password
** Changed in: oem-config (Ubuntu) Importance: Undecided = High Status: New = Confirmed -- Shutting down after oem-config runs requires password https://bugs.launchpad.net/bugs/300667 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300667] Re: Shutting down after oem-config runs requires password
** Attachment added: Screenshot of the dialog http://launchpadlibrarian.net/19833926/shutdown-dialog.png -- Shutting down after oem-config runs requires password https://bugs.launchpad.net/bugs/300667 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
