Hi folks,

I am running roundcube on an Ubuntu 10.04 LTS for some years now. I have an old user which is unable to check its mails or compose new. When trying to compose a new message I get this on the error log:

[19-Mar-2012 13:15:48] MDB2 Error: unknown error (-1): _doQuery: [Error message: Could not execute statement]
[Last executed query: DEALLOCATE PREPARE mdb2_statement_mysql_2c2b391612904b84a62da258fe79b33e2e8ad03fc]
[Native code: 2014]
[Native message: Commands out of sync; you can't run this command now]

[19-Mar-2012 13:15:48] MDB2 Error: unknown error (-1): _doQuery: [Error message: Could not execute statement]
[Last executed query: PREPARE mdb2_statement_mysql_3b8a178a5521b8c2fe131aeea5d22f803152283fb FROM 'UPDATE session SET vars=?, changed=\'2012-03-19 13:15:48\' WHERE sess_id=?']
[Native code: 2014]
[Native message: Commands out of sync; you can't run this command now]

[19-Mar-2012 13:15:48 -0300]: DB Error: _doQuery: [Error message: Could not execute statement]
[Last executed query: PREPARE mdb2_statement_mysql_3b8a178a5521b8c2fe131aeea5d22f803152283fb FROM 'UPDATE session SET vars=?, changed=\'2012-03-19 13:15:48\' WHERE sess_id=?']
[Native code: 2014]
[Native message: Commands out of sync; you can't run this command now]
 in /var/www/roundcube/program/include/rcube_mdb2.php on line 293 (GET /?_task=mail&_action=compose&_reply_uid=12424&_mbox=INBOX)
[19-Mar-2012 13:15:48] MDB2 Error: unknown error (-1): _doQuery: [Error message: Could not execute statement]
[Last executed query: DEALLOCATE PREPARE mdb2_statement_mysql_2e8cc86bba4898aea4305b0ac268bb7f89bd09dce]
[Native code: 2014]
[Native message: Commands out of sync; you can't run this command now]

[19-Mar-2012 13:15:48 -0300]: PHP Error: Invalid compose ID in /var/www/roundcube/program/steps/mail/compose.inc on line 52 (GET /?_task=mail&_id=1719649054f675bb43d3a7&_action=compose)


I googled for this error but got zarro boogs found, I mean, no google results. I had 0.7.1 installed, he was using without any problem, and then today he started to get this error. I upgraded to 0.7.2 in a hope to solve the problem, but no luck.

Can someone help me solve this or at least find what is wrong?

Thanks in advance, best regards.

--
Marcio Merlone