[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
Why does the X server care about ACPI events at all, as opposed to input events? Yes, if X still wants ACPI events, then we're dealing with acpid, for the nonce; I'm just surprised it should need to. -- *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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
On Wed, Mar 10, 2010 at 07:10:18PM -, Steve Langasek wrote: Why does the X server care about ACPI events at all, as opposed to input events? Legacy support? Yes, if X still wants ACPI events, then we're dealing with acpid, for the nonce; I'm just surprised it should need to. I guess we could fairly easily just disable it and see if anything breaks. I can do the patch but I'd like your direction on if this is sane or not at this point in the release. -- *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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
Hi Mark, No, xserver does not need acpi to be running. We've known for some time about the error message that gets produced when it isn't there; in fact I had to quell it because it'd spam the Xorg.0.log (see lp #247195). The spamming eventually got fixed upstream, but the acpi probing code (and corresponding error message) is still there. What the code in question is doing is setting up a listener to acpid for power management events (suspend/resume/battery-status) If it doesn't see acpid at boot, it sets a timer to try again later. So as I understand it, it's not really X *depending* on acpi for anything but rather honoring its presence if it is there. I checked a recently installed/updated desktop and laptop and see that acpid is still present on both, so assume it's appropriate for X to continue to listen for them. I'm subbing Steve in hopes he understands this notification path better and can shed some light for us. -- *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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- *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-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
the acpid code should be purged from the server. ** Package changed: xorg (Ubuntu) = xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Importance: Undecided = Wishlist ** Changed in: xorg-server (Ubuntu) Status: New = Confirmed -- *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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
make that acpi code -- *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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496859] Re: *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting.
Bryce, can you comment on: - what X does with acpid.socket - what the consequences of missing it on startup would be - whether we can drop the acpid.socket lookup at all, or - whether we can make X watch /var/run/acpid.socket with inotify and use it if it shows up Thanks! Mark -- *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-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
