Hmm....

[1|root@Nokia-N800-43-7|~]asui dd; asui id
Downloading the debug binary...
Size: 576742
Stopping Advanced SystemUI....
Using debug binary for the service...
Starting Advanced SystemUI....
[1|root@Nokia-N800-43-7|~]


Before I was running this instead:

asui dd; asui k; asui rd

Both methods produce the same log file, I'm just lazy and use asui id and asui it to switch back and forth, the script handles starting and stopping ASUI for me.

Okay. Sorry. I'm still not understanding all of your arguments with this.

Anyway, when you said for me to run "asui dd; asui id" this time, it won't log for me.

Okay whatever, just use asui it ; asui k ; asui rd then. Just because asui id isn't spewing text to the console doesn't mean it isn't logging. If you run rm /root/asui-debug* ; asui id ; asui it there will be a log file in /root.

Ah.

Gotcha.

Sorry for being such a simpleton.

Okay boss.

Here's my latest turd offering for you.

root
asui dd; asui k; asui rd

Power key
Center Dpad
Audio Lock Xmms
(no music playing) -< Can we figure a way to launch this correctly?
Power key
Center Dpad
Fired up Xmms, clicked on play, then minimized it
Power key
Center Dpad
Audio Lock Xmms
Pressed zoom in key x 6
Then mashed buttons after it stopped working, which again, was under 30 seconds.

So yeah, your feature does work. I was able to change tracks like 6 times before it pooped out on me.

I hope this helps.

asui-debug-20111222-141610-r2.zip

And another worthless log without any click or audio lock messages. You either sent the wrong log again, you stripped out those entries or you didn't touch the screen. There is no possible way it would write out every other message except for the clicks and audio lock messages.

One thing I did notice is that the blank window isn't opening because it can't grab focus. Do you have a menu open or something else that is grabbing focus? Something that is visible when you press the power button is preventing ASUI from working. You probably also have problems unlocking the screen because of this.

There is nothing I can do to fix this until I figure out how SystemUI closes them.

I have 2 Xterms open each time.

One is for typing in that debug junk.

The other one is to first launch Xkbd since that's the only way I know of to send a Ctrl C to stop this.

And yeah, it's definitely the correct log since I keep deleting the older ones.

Here's another turdy log file.

I think this one should have what you need.

I already had Xmms running in the background since it still doesn't begin to play when launching your Audio Lock Feature.

I was able to change tracks x 4.

Then it all became unresponsive again and I started mashing buttons out of horror and sadness. *lol*

I don't understand why your script doesn't hold for any more than 30 seconds.

Anyway, Merry Christmas my good friend.

asui-debug-20111224-141205-r2.zip

I told you how to fix this, please stop posting log files that show the same problem. ASUI is not able to steal focus away from an app that has explicitly grabbed focus like a menu and maybe xkbd. You need to make sure that nothing else is stealing focus until I can find a fix (it has been a known bug for almost a year, so don't hold your breath).

If you are able to remove the app stealing focus and audio lock is still not working then let me know. The next audio lock related log file you post that doesn't contain "found audio lock profile" will be the last log file I look at from you.