It never gets as far as apport. The GUI hangs and never recovers (that's what happened with the second backtrace) rather than segving.
As it happens when a podcast has finished downloading but before rhythmdb.xml is updated, it might make sense that it's some thread related write locking problem on rhythmdb.xml which then leaves the gui in a wait state until the write is complete (never). But that's a punt at a possible explanation without looking at the code. This seems to happen with any feed so I assume it would be fairly easy to replicate. -- [Gutsy] Crash on podcast download https://bugs.launchpad.net/bugs/148646 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
