Not with 4.9.2 specifically Michael, but the error that is beginning to get me down because it feels that it crops up at least twice a week, is this one:

Now this is in 4.9.2, and therefore in PE. If a PE customer has this problem, what will DNNCorp Support's reaction/advice be?

But unfortunately no actual answers given since it started in Jan 09.

Though it was pretty much a follow on from:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/272431/scope/posts/Default.aspx - started Dec 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/252337/scope/posts/Default.aspx - started Sep 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/248276/scope/posts/Default.aspx - started Aug 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/118/threadid/246886/scope/posts/Default.aspx - started Aug 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/213926/scope/posts/Default.aspx - started May 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/219973/scope/posts/Default.aspx - started Apr 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/219120/scope/posts/Default.aspx - started Apr 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/216345/scope/posts/Default.aspx - started Apr 08, my own bug confirmation request after a week of my time spent when bug was known
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/214608/scope/posts/Default.aspx - started Mar 08, myself first being told of bug
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/214858/scope/posts/Default.aspx - started Mar 08, thinking it
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/203003/scope/posts/Default.aspx - started Feb 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/203003/scope/posts/Default.aspx - started Feb 08
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/7/threadid/177341/scope/posts/Default.aspx - started Oct 07, told current bug version is only supported

So there is plenty on this for the last 1 1/2 years... but unfortunately if there is someone that's able to push it forward and get these bugs fixed - they mustn't yet be aware of this.  These are only the major threads on the Forum bug topic... many more smaller ones are there too.

The DNN Core itself seems mostly fine... but it can be running perfectly and it won't make a difference if the tools such as the DNN Core Forums that run on this are full of bugs and can take this long with absolutely no progress made.

It really is the whole DNN Core Package that needs to work together, and break in the chain affects the lot.
 

I'd like to agree with Sebastian's comment : there were several beta and RC versions of DNN 5.0, and the amount of issues logged pointed to the fact that not many people were using it in anger, and therefore not finding the bugs.  I'm as guilty of this as anyone.  I think the wide release of 5.0 was a good idea, as it finally prompted people to download and start using it.  The fact that it turned out to be a bit flaky is a result of not enough people testing and using the RC releases.  A new major release is expected to have some issues, and people can best contribute by not sniping, but figuring out answers and posting them to gemini.

I think the fact that the 5.0 release coincided with the announcement of DotNetNuke PE has nothing is pretty much irrelevant.  The PE edition is 4.9.2 AFAIK, which was always promised that the PE would be the most stable version going.