On Mon, 2008-12-22 at 01:06 +0000, Connor Imes wrote: > I would gather that this bug is not present in newer version, but can > anybody confirm? I set the confirmation on this bug earlier today > because it was expiring but had been confirmed by another user. Here > are the versions currently in the Ubuntu repositories: > > banshee | 0.10.10-0ubuntu10 | dapper/universe | source, amd64, i386, > powerpc > banshee | 0.13.1+dfsg-3 | gutsy/universe | source, amd64, i386, powerpc > banshee | 0.13.2+dfsg-9 | hardy/universe | source, amd64, i386 > banshee | 1.2.1-3ubuntu1 | intrepid/universe | source, amd64, i386 > banshee | 1.2.1-3ubuntu1.1 | intrepid-proposed/universe | source, amd64, > i386 > banshee | 1.4.1-1ubuntu1 | jaunty/universe | source, amd64, i386 > > ** Changed in: banshee (Ubuntu) > Status: Confirmed => Incomplete > I don't notice it, but to be fair, I should think that database locking would be a problem if some other application is attempting to access Banshee's database, and this bug is not Banshee's, but that particular application. Would any application you're using fit into that criterion? Perhaps GNOME Do's Banshee plugin? -- Chow Loong Jin
-- Banshee Encountered a Fatal Error: the database is locked https://bugs.launchpad.net/bugs/229616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
