Heh, I went to package that patch and discovered that I had looked at this patch once before in troubleshooting #439138, but the error message had been just a red herring. Notice especially starting with comment #32 on that bug report a proposal was made to add an acpid dependency but in further investigation this was identified as unnecessary.
That said, I don't have solid opinions one way or another as to whether to keep acpid support enabled in X or not. I no of no issues which would be caused or solved by this change. From what I understand of the code, X may issue this error message but it has timing code to try again later, so if acpid is just late coming up that's totally okay. And if acpid never comes up for whatever reason, it won't break X. Guidance from Steve Langasek is "unless there's evidence that the change actually fixes something, I think it should be postponed to M". This seems a sensible plan. Meanwhile, I've packaged the patch and stuck it in a PPA to make it easy for anyone who would like to do some testing with this: https://edge.launchpad.net/~bryceharrington/+archive/yellow -- *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting. https://bugs.launchpad.net/bugs/496859 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
