I was there when he had that crash. It is not easily reproducable. It claimed it had crash, but it didn't. I suspect this means a program or task rhythmbox created had crashed.
Looking at ProcStatus, it seems that its related to the indexing of meta-data. Which would also explain why the rhythmbox program itself wouldn't crash. My guess is: thats its a specific file that was causing this. Another possibility is that the file being indexed was currently locked or still being written to. Perhaps its not so much a situation of fixing the crash, but making it recover gracefully when the meta-data-extractor fails. But thats just my 2 cents worth of speculation. -- rhythmbox crashed but didn't really https://launchpad.net/bugs/89571 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
