Bugzilla – Bug 1852
Crash reported
Last modified: 2009-09-08 09:12:26 UTC
I had a crash with 6.1 over night. I was playing a music station from live365 - I think this stopped a little earlier than the crash, but the SqueezeBox was still working at that point. Potentially, it could have happened when the AutoDisplay plugin kicked in, otherwise I don't believe the SB was doing anything around the time of the crash (standby mode, I think): Operation `.=': no method found, left argument has no overloaded magic, right argument in overloaded package Class::DBI::Object::Has::Been::Deleted at /PerlApp/Slim/ Utils/Prefs.pm line 733.
Note, that this was reported on the list by Philip Meyer
I have had another occurance of my prefs being reset. I experienced a crash which happened when navigating through the Alien BBC menus on a SqueezeBoxG. Operation `""': no method found, argument in overloaded package Class::DBI::Object::Has::Been::Deleted at /PerlApp/YAML/Node.pm line 26. However, when I restarted the server, I noticed that my the web front end came up in the default skin, not my usual Fishbone skin. Alas, my slimserver.pref file has been overwritten. There was a discussion thread recently about changing the way that the prefs were flushed to disk. Has the code changed in the last week? As this problem happened to me a couple of weeks back, I assume no changes have happened yet. My slimserver.prefs file now has what I imagine are the standard default values, and there's no backup of my prefs to go back to. Looking in the file, there are paths that do point at my installation folder, which is not the standard path. I guess slimserver writes defaults to the file, taking into account the install dir. Perhaps slimserver had some memory problem; the preferences that were held in memory got overwritten, and thus caused slimserver to crash, but at the same time the preferences were flushed to disk?
*** Bug 1907 has been marked as a duplicate of this bug. ***
This might be fixed with the 08-09-2005 6.2 nightly (which will be built in 1.5 hours). Could you let me know if you see it again?
Philip - have you seen this since my probable fix went in? Thanks.
helps if phil is on the cc-list to answer that question :)
phil? are you out there? is anyone still seeing this?
Closing this - please reopen if someone sees it again.
Sorry, I didn't see the mail notifications of progress to this bug - probably got filtered or deleted when I got behind with mail after a vacation. I have not noticed any occurance of this problem, so it is probably fixed.