Thank you, Steve, that helps quite a bit. The 'client-side duping' I'm talking about is, I guess, a fairly recent arrival?
http://www.piware.de/2011/11/apport-1-90-client-side-duplicate- checking/ "So with the just released Apport 1.90 we introduce client-side duplicate checking. So from now, when you report a crash, you are likely to see “We already know about this” right away, without having to upload or type anything, and you will get directed to the bug page. You should mark yourself as affected and/or subscribe to the bug, both to get a notification when it gets fixed, and also to properly raise the “hotness” of the bug to bubble up to developer attention." Does this help explain my preceding posts? If not, excuse me again! :) To me, that's how I got to 628104, and from the looks of it, I think that's true for just about all the newer comments, that reference Precise. From what I can see, people are mostly not subscribing, as Martin proposes. That may be creating, inadvertently, some hit-and-run reporting, with not much follow-up. (It's this impression that has led me to be sort of knuckleheadedly persistent, in my fumbly efforts to pursue this.) I'll try to post more tomorrow, with more info about reproducing, and I'll see if this has made any better sense of things, yet. Thanks. -- 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
