To be more explicit, I think the recent reports like mine, against 628104, *are* the new duplicates -- their equivalents, since the system intercepts them. (It's been my plan to mail Martin, to ask about this sort of thing, after release happens.)
Since we can't open the bug we're sent to, bug 915413 was a user's subsequent attempt to make an open bug, manually. It got re-traced and duped to our other friend, bug 855394. So this bug was my attempt to make an open bug, and I knew I had to omit the traceback. (See, it's all so simple. Wait, it's not. ;) For reproducing, I guess my comments in #7 cover it, but I can write that out in more of a list, if that makes it easier to read. Since I have the good luck of getting a slice of your attention, Steve, let me ask you a question about releasing, if you will. I'm chasing a few different bugs right now. I don't know whether this is a time to work urgently, for a remote chance of making Precise. Or whether that has really passed, for anything that isn't truly massive. In that case, if anything, I would hold back for this week, and leave the developers some quiet. And personally calm down a bit. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982767 Title: aptdaemon crashes during update-manager run: "Could not cancel transaction" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/982767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
