*** This bug is a duplicate of bug 453812 ***
https://bugs.launchpad.net/bugs/453812
Oh I deleted the power manager and no problems with that since
On Mon, Nov 16, 2009 at 11:23 PM, Robert Zaccour
wrote:
> Is there gonna be a fix for this?
>
>
> On Mon, Nov 16, 2009 at 4:02 AM, Guido Berhoer
*** This bug is a duplicate of bug 453812 ***
https://bugs.launchpad.net/bugs/453812
Is there gonna be a fix for this?
On Mon, Nov 16, 2009 at 4:02 AM, Guido Berhoerster wrote:
> *** This bug is a duplicate of bug 453812 ***
>https://bugs.launchpad.net/bugs/453812
>
> This problem is as
*** This bug is a duplicate of bug 453812 ***
https://bugs.launchpad.net/bugs/453812
This problem is as you wrote in the description closely related to, but not the
same as bug #415023, rather it is a duplicate of bug #453812 which is linked to
the appropriate upstream bug.
In short, the key
*** This bug is a duplicate of bug 415023 ***
https://bugs.launchpad.net/bugs/415023
** Description changed:
TL;DR: Whenever the screen tries to dpms off/standby/shutdown,
brightness change key events are generated, simulating activity and
instantly waking it. This is on an Advent 4211
*** This bug is a duplicate of bug 415023 ***
https://bugs.launchpad.net/bugs/415023
Attaching a short clip showing dbus-monitor as it catches the phantom
key events.
When I execute 'xset force dpms off' in the clip, the screen does go
black, but as soon as the d-bus call is monitored it wake
*** This bug is a duplicate of bug 415023 ***
https://bugs.launchpad.net/bugs/415023
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/35720143/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/35720144/ArecordDevices.txt
** Att
