I did search and found old threads with similar problem
My n900 first starteda couple of weeks ago, showing a highligted number in my inbox saying i was having new conversation there, but there was nothing new..
then it mixed different conversations in 1, you could see different conversations in 1 box or number

Now i see the bubble on top that im getting a new message i can read it from the bubble, but when i go the inbox, theres nothing there.

My work around is do like if i m going to send a new sms to same person and it shows the old conversation with the new messages.

ANother one, From the inbox i pick the option, delete conversations, i choose several then delete, to my surprise, they remain there, the messages dont get deleted... zzz

last update. yesterday i noticed, my phone duplicated a IM message i had with a friend... check it out

xterm:
youll lose your history but your problem should be solved

it will delete all messages history ?

cuz they cannot be deleted 1 by 1

thanks

edit
im guessing i will need root with it

Yes, killall indeed needs to be performed as root.

No it doesn't, at least not in this case.

thank you all
let me get this right
should i do it exactly like that in 2 lines ? or how, in lines please

1 killall rtcom-messaging-ui
2 mv ~/.rtcom-eventlogger/el-v1.db ~/.rtcom-eventlogger/el-v1.db.bak

Yes, two separate commands.

the press enter: this command calls the Conversations process in general. You actually DON'T have to do this step, but it reduces the likelyhood of some very unpredictable bugs that may or may not occur if you get a new message while the next command is in progress. I never bothered with it when I had this problem, but I suppose it is slightly safer.

Anyway, then:
This will take the database that stores all your message histories (the el-v1.db file), and will rename it to el-v1.db.bak. This way, you can later use some other database reading programs to dig up your messages from within the now-renamed file. Meanwhile, because it's renamed, the Conversations app doesn't know it's there any more, so effectively, all your messages are deleted. Next time you get a message, the program should be able to recreate a new el-v1.db file, and everything should work normally from there.

What this problem is is when the database that contained the messages gets corrupted. MOST of the time, deleting it and letting it get remade fixes it. Sometimes, you have to go one step up, and delete the entire .rtcom-eventlogger directory - that was what I had to do - remaking the databases themselves didn't fix anything, but when I deleted the entire folder, it fixed itself.

*Shrug* Just a matter of luck which one is the problem, but usually, it's the database, so just go with the above commands first.

Metalist traceur, that was more than i expected.. thank you so much

edit
conversations were deleted successfully...
ill be updating

after doing this the only problem i ve noticed is that, call notify is not beeping anymore.
i think i ll have to re install it again

re installing didnt work, is it bcuz i changed the path, call notify is not working ?

anyone knows