Topics not getting stored in subject cache

[Trekkie101]

The subject of topic #63 is currently not stored in the subject cache.
The subject of topic #64 is currently not stored in the subject cache.
The subject of topic #66 is currently not stored in the subject cache.
The subject of topic #67 is currently not stored in the subject cache.
The subject of topic #68 is currently not stored in the subject cache.
The subject of topic #69 is currently not stored in the subject cache.
The subject of topic #70 is currently not stored in the subject cache.
The subject of topic #71 is currently not stored in the subject cache.
The subject of topic #72 is currently not stored in the subject cache.
The subject of topic #73 is currently not stored in the subject cache.
The subject of topic #74 is currently not stored in the subject cache.
The subject of topic #75 is currently not stored in the subject cache.
The subject of topic #76 is currently not stored in the subject cache.
The subject of topic #77 is currently not stored in the subject cache.
The subject of topic #79 is currently not stored in the subject cache.
The subject of topic #80 is currently not stored in the subject cache.
The subject of topic #81 is currently not stored in the subject cache.
The subject of topic #82 is currently not stored in the subject cache.
The subject of topic #83 is currently not stored in the subject cache.
The subject of topic #108 is currently not stored in the subject cache.

Theres a lot more of that, any idea why it does that?
Shows up when I look for errors, SMF 1.1 RC2

Could this also break the button that shows new at new posts?

[EG]

Ive got a load of those too!

in Errors!

[dtm.exe]

Same on my forum.

[rendi]

same i got that error too this is a bug ?

[azc]

Same here.

Get those after clicking the "Empty out unimportant logs." link in the ACP Forum Maintenance section.

FWIW - Fedora FC-2, Apache 1.34,  PHP 4.3.11 w/ Zend v2.5.7, MySql 4.0.25

Could this also break the button that shows new at new posts?

Hey yeah, I had a 'new' button prob also, but forgot to document it.

[dtm.exe]

same i got that error too this is a bug ?

Yes.

[redone]

This is being reviewed as a bug within the last release.

[Trekkie101]

This is being reviewed as a bug within the last release.

It was in RC1 aswell, manged to confirm with an RC1 install

[David79]

I'm getting that error as well....every since I updated to RC1...and now getting it a lot more since switching to 1.1 RC2

[Omega X]

I get those as well. Is their some kind of quick fix to handle it or just let the maintainece script handle it?

[Grudge]

I'm almost certain this is now fixed?

[Harzem]

Unfortunately latest RC2 keeps giving tons of these errors in "repair errors" section. Sometimes, even repairing them doesn't fix them. At the very next check, they appear again.

* HarzeM delays the release of RC3

[EG]

Unfortunately latest RC2 keeps giving tons of these errors in "repair errors" section. Sometimes, even repairing them doesn't fix them. At the very next check, they appear again.

* HarzeM delays the release of RC3

me too

was there a patch I missed ?

[H]

Unfortunately latest RC2 keeps giving tons of these errors in "repair errors" section. Sometimes, even repairing them doesn't fix them. At the very next check, they appear again.

* HarzeM delays the release of RC3

I don't believe a patch was ever issued for this therefore RC2 will still experience this problem. The CVS (RC3) version should already have this fixed