Re: [Announce] advanced-systemui
 

hrmf, even wireless fails when mce goes bad.

Re: [Announce] advanced-systemui
 

Then it is no doubt a mce bug, some race since it seems very timing dependent.
When it hit me, I was unable to debug it effectively because it only happened at boot and unreliably.

You said you can trigger it after booting with systemui and then stopping systemui and starting ASUI with asui-settings.
Can you repeat it by hand? I mean, boot with systemui, then stop systemui ("/etc/init.d/osso-systemui stop"), then start ASUI ("/usr/bin/advanced-systemui").
Then, is it repeatable? I mean, kill ASUI (ctrl-c in xterm), restart MCE ("/etc/init.d/mce restart"), start ASUI->bug happens?
If not, what if... restart mce, start osso-systemui, stop-osso systemui, start ASUI->bug happens?

Re: [Announce] advanced-systemui
 

even systemui is showing signs of problems now. Not sure if i can spend much time poking this the next 24 hours or so.

Re: [Announce] advanced-systemui
 

Does this happen on a clean boot when ASUI hasn't been running?

--

I looked over the communication between systemui and MCE again and there is nothing that ASUI doesn't emulate. ASUI ignores the system_ui:tklock_open method MCE calls whenever the screen is locked or turned off. I thought that might somehow break MCE in rare cases but the call doesn't expect a reply and systemui never invokes the callback MCE sends with the method so ignoring it should have no impact.

Re: [Announce] advanced-systemui
 

yep, got it on a systemui boot.

what i see is no systemui after boot when pressing power butRestarting MCE fixes that but results in dim only on screen lock , rather then blank.

Re: [Announce] advanced-systemui
 

@ maacruz, what minimal/full set of packages would he need to uninstall or downgrade to get rid of DT kernel so he can see if the problem goes away? You should probably post uninstall instructions in the DT thread.

Re: [Announce] advanced-systemui
 

@ tso, if you open asui-settings:services, uncheck alarmd and reboot does the problem go away? If you set PowerKeyDoubleAction=softpoweroff in /etc/mce/mce.ini, restart MCE and double tap the power button does the screen blank? Long power press will wake up from softpoweroff in case you don't know.

Re: [Announce] advanced-systemui
 

rebooting with disabled alarmd seems to have taken care of the issue!

Re: [Announce] advanced-systemui
 

New test and settings binaries.

• cosmetic changes to sounds button
• fix: overall UI throttling didn't use the 60 second limit for tap throttling, it does now
• setting to split lock buttons in two halves so both actions can be handled with short taps instead of short and long taps

The lock buttons will default to the current method of short and long presses but the long press action will now have a dotted border. Both top and bottom buttons will have a solid border when the split buttons setting is enabled.

You should install syslogd and klogd to see if alarmd is writing any errors. I know it can prevent screen from blanking when it has an active alarm and if it is malfunctioning it could maybe do the same.

Re: [Announce] advanced-systemui
 

To uninstall the DT kernel, you just uninstall the kernel package ("apt-get remove kernel-dt-sd"), that will remove the ramzswap package too.
But I'd rather find more about this to be able to make a proper fix/workaround than uninstall packages blindly.

@Tso: what happens if you boot with alarmd disabled and then, once the boot is finished, start alarmd by hand ("/etc/init.d/alarmd start"), does mce go bad or keeps sane?