Re: ANNOUNCE: Diablo-Turbo first beta available
 

That's right. I've delayed installing ASUI for this very reason -- to try to better isolate this problem.

Doing "systemui" or "systemui restart" from the terminal gives me an error message. But see below:

Ahhhh... sudo make a sandwich. That did it. Call me stupid if you like. I'm going to add sudo to my Personal Menu item as well. Thanks all!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

^ You're a goof.

Thanks for the chuckle. :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Ah yes, that. I recall noticing that MCE behaved differently depending on being restarted via user rights or root rights. And it was very damn subtle about it.

Still, that the dimming issue shows up for someone not using ASUI seems to indicate a turbo issue.

And on that note, i have not had the dimming issue the last couple of times my N800 have been booted using the charger and then entered the maemo desktop by way of a power button long press. Then again, i use ASUI.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Have you ever had ASUI installed? The dimming problem was thought to be an issue between alarmd and ASUI which persists even if you revert back to SystemUI.

I know ASUI is incorrectly dismissing alarms because the interface I found was wrong and I also know that ASUI is telling alarmd that the system is booted up even when in the charging runlevel. Both of these problems have been fixed but haven't been tested and released yet.

This changes everything if you have never used ASUI as it becomes a problem between alarmd and DT which might be harder to find. Anyone out there have a device not running DT and experiencing the alarmd problem with ASUI?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have certainly never had ASUI running on my machine. I'm pretty sure that I didn't start trying to install it & then stopped. (I'm just trying to be careful in my answer b/c I've thought about installing it many times.)

I have also had times where the alarm went off five minutes after it was supposed to, which is kind of odd. I think it only did that after installing DT. I've also had times where I've awakened on my own to find the alarm dialog sitting open but without making any alarm sound, although I am not certain that this wasn't because of my volume setting.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It is a mce bug.
mce sends a signal to systemui when the power button is pressed, then systemui shows the power menu button. Also, mce is responsible for dimming, and mce is related to alarmd.
I've suffered this issue before installing ASUI, and I have done may be a hundred tests trying to find a workaround or a fix before finally giving up.
Since mce has nothing to do with the kernel, it is not caused by the kernel (or otherwise many programs would crash or exhibit other symptoms).
It is caused by a race condition (http://en.wikipedia.org/wiki/Race_condition) in mce, probably related to gconf. The relation of the kernel here is that, for the different timing caused by the different schedulers, this mce bug is exposed when using other schedulers than O1.
How do I know that?
I saw it appear with the first alpha kernels, with both CFS and the SD schedulers, preemption or not. So it happens with two different schedulers, and the only thing affected by a scheduler is timing.
With the new gconf packages (which also have increased performance) it disappeared for me.
So yes, DT may expose this bug, and I can do nothing to fix it, short of rewriting the whole mce thing because it is closed source.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Well, that seems to put everything into perspective. Thanks, maacruz, for the additional detail into what I assume you have been telling us for some time now.
Which packages are those? Is it an option for the rest of us to install them to fix this problem?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

gconf2_2.16.0-1osso15_armel.deb and libgconf2-6_2.16.0-1osso15_armel.deb
You already should have them installed just by following the first post instructions.
Since very few people has noticed this issue, I guess the probability of it happening may be increased by some other package, although I can't discard some other possible influence

Re: ANNOUNCE: Diablo-Turbo first beta available
 

So who has this problem and wants to try installing powerlaunch and only enabling its MCE replacement? We don't have to rewrite MCE when powerlaunch already does that, just need to fill in any incomplete areas. I can fork the MCE service into its own package if it fixes the problem and works well enough.

I should have some free time in the next week or two to finish up the current batch of ASUI fixes and will then play around with powerlaunch's MCE if no one else has. Although it would be better if someone who has the problem frequently tested powerlaunch's MCE since I have only ever had alarmd running when performing tests and can't properly test it under real world conditions.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Would I have to drop ASUI to be a tester for this?

I really like everything you have done with it and would rather keep this if possible. :)