I spent some time debugging this, as the behavior was very random: sometimes messages would appear, sometimes they wouldn't and at some point it would stop working at all.
I wrote a test application that would create a new entry in the menu every 500ms, and when trying to run it I got some memory errors in the indicator-messages-service:
*** Error in `/usr/lib/arm-linux-gnueabihf/indicator-messages/indicator-messages-service': corrupted double-linked list: 0x001419b0 ***
and sometimes:
*** Error in `/usr/lib/arm-linux-gnueabihf/indicator-messages/indicator-messages-service': malloc(): memory corruption (fast): 0x013b6ee8 ***
So, the steps to reproduce:
1) Compile and run this test program for the device: http://ubuntuone.com/3XTnbxnqU0U8SYuiIDFIYH
2) Start the indicator-messages-service manually (to see the printed messages)
3) run the test program.
I spent some time debugging this, as the behavior was very random: sometimes messages would appear, sometimes they wouldn't and at some point it would stop working at all.
I wrote a test application that would create a new entry in the menu every 500ms, and when trying to run it I got some memory errors in the indicator- messages- service: arm-linux- gnueabihf/ indicator- messages/ indicator- messages- service' : corrupted double-linked list: 0x001419b0 ***
*** Error in `/usr/lib/
and sometimes:
*** Error in `/usr/lib/ arm-linux- gnueabihf/ indicator- messages/ indicator- messages- service' : malloc(): memory corruption (fast): 0x013b6ee8 ***
So, the steps to reproduce:
1) Compile and run this test program for the device: http:// ubuntuone. com/3XTnbxnqU0U 8SYuiIDFIYH messages- service manually (to see the printed messages)
2) Start the indicator-
3) run the test program.