advanced-systemui (0.2.4)

• increased font size for the reboot and shutdown confirmation messages
• changed yes and kill buttons to red in reboot, shutdown and kill process dialogs
• text clipping (long process names won't have front chopped off in the kill confirmation dialog)
• fixed text centering and other alignment problems
• fixed selection of processes below the first page
• fixed the disappearing kill button after a rotation

advanced-systemui (0.2.5)

• battery idle time
• battery idle time, temperature scale, clock and start visible settings
• detects screen rotations produced by other apps
• flight mode query to libdbus
• increased memory query speed some more
• free dbus method return strings
• fixed problem with battery being queries multiple times in a short period
• fixed max battery mAh to retry if first attempt fails

You will need to install gconf-editor to change the settings (in /apps/asui). The battery idle time setting can be used with advanced-power but not the default battery applet.

Seems a segmentation fault made its way into 0.2.5.

Something has been causing all versions to randomly crash but dsme restarts it. Never happens when I'm running the test client though.

Can you reproduce it?

0.2.5 segaults on me too.

Yep, it happens every time i try to run it. neither restart nor reinstall had any effect.

May be that it is trying to read non-existent settings from gconf, as i do not see a asui dir in there.

http://qzx.com/asui/?p0=download

Can you run the test binary and tell me what it outputs before crashing?

Edit: Previous version is here if you want to download it and use dpkg -i advanced-systemui_0.2.4_armel.deb to downgrade.

Test binary ran without issue.

And it seems i was right. After i ran the test binary, the asui dir in gconf was present. And now 0.2.5 also works.

Btw, i am unsure if there is need for both a 24h and ampm option. Unless i am missing something, having one that toggles between the two, based on being set or not, would be enough.

I don't understand how the same binary crashes under DSME and runs fine without it.

Only difference between the 0.2.5 binary and the test binary are the half dozen printf's to give me an idea where it was segfaulting. Both binaries create the gconf keys if they don't exist.

Unchecking the 24h option enables a 12 hour clock without am/pm indicators. The ampm option turns on the indicator for those who like it, and makes it optional for those who don't.

some kind of issue between DSME and gconf?