[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 i

[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.

fedora hasn't built the acpi code for some time now: http://cvs.fedoraproject.org/viewvc/devel/xorg-x11-server/xserver-1.6.0 -less-acpi-brokenness.patch?revision=1.1&view=markup -- *dm upstart job should depend on acpid because X tries to connect to acpid socket very soon after starting. https:

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

[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

[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

[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 upst

[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.

[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 beca

[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