Possible regression, need some assistance debugging

I am working with the amaroK team and have run into a little problem since 
upgrading mysql to 5.0.18.  We use mysql as one of the choices for the music 
collection database, and since upgrading mysql to 5.0.18, I am getting an 
error about the server having gone away after amaroK sits idle for awhile 
(overnight).  This is the error

      "[CollectionDB] MYSQL QUERY FAILED: MySQL server has gone away"

This error appears and continues until the application is killed and 
restarted.  I am not sure if it is a bug or desired behavior, so I thought I 
would ask here first before posting a bug.

When I RTFM, I see that there is an explanation about the  wait_timeout 
parameter here http://dev.mysql.com/doc/refman/5.0/en/gone-away.html  I 
didn't recall this behavior in 5.0.17 so I downgraded to test and after 
attempting the same task, the error does appear for a second in the console, 
but eventually the the query is completed successfully.  So, 5.0.17 allows a 
connection to be re-opened after being idle for the wait_timout period, but 
5.0.18 does not.

So the question is, what changed from 5.0.17 to 5.0.18 and is this intentional 
or a regression?  perhaps there is some test that must be performed in amaroK 
so that a new connection can be opened when the wait_timeout period is 
exceeded.

The amarok bug in the KDE database is here for further information.  
http://bugs.kde.org/show_bug.cgi?id=120198

-- 
Greg


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642