Notices

Originally Posted by dfcamara

I'm using modest (diablo) with one imap GMail account configured. I'm experiencing crashes in the background process, and what is worse, sometimes it stays at 99% CPU usage draining battery power.

I can't leave my N810 in stand-by without risking it off with a flat battery. To make matters worse, full discharge of Lithium batteries shortens it's charge capacity.

Below is the output of the 'top' command showing 'maemo-launcher' process (PID 7802) with 98.9% CPU usage, and 'ps' command relating PID 7802 to modest executable:

Code:

$ top
Mem: 112060K used, 14736K free, 0K shrd, 60K buff, 38544K cached
Load average: 1.07 1.05 1.05
  PID USER     STATUS   VSZ  PPID %CPU %MEM COMMAND
 7802 user     SW     70408  7075 98.9 55.4 maemo-launcher
 7935 user     RWN     1960  7917  0.7  1.5 top
  358 root     SW       776   350  0.1  0.6 bme_RX-44
 7328 user     SW     67292  7326  0.0 52.9 browserd

Code:

$ ps | grep 7802
 7802 user      70408 SW  /usr/bin/modest

I've seen other people complaining about maemo-launcher processes with 99% cpu usage, modest background crashes and shorten battery live in Diablo. In my case I'm think they are related. If someone knows of some debug procedure I can do about to help, I'm interested.

P.S. I did a reflash to Diablo firmware without restoring any backup and configured modest only once. Didn't install any software outside official Diablo and Diablo extras.

Originally Posted by brontide

Unfortunately Nokia saw fit to release Modest on the masses before it was ready. All you can do is wipe modest out and make sure it's not auto-updating. I'm sure it will be fixed this year, but since it's been unstable since February I would not hold my breath.

Please search and vote for bugs in bugs.maemo.org so that your voice might be heard. Complaining here will likely produce no change in the status quo.