[Bug 982767] Re: aptdaemon crashes during update-manager run: "Could not cancel transaction"

[Edward Donovan]

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
Foundations Bugs, which is subscribed to aptdaemon in Ubuntu.
https://bugs.launchpad.net/bugs/982767

Title:
  aptdaemon crashes during update-manager run: "Could not cancel
  transaction"

Status in “aptdaemon” package in Ubuntu:
  Incomplete

Bug description:
  This crash is the subject of bug 628104 and bug 855394.  Those are
  marked fixed but it's still happening.  The latter bug was closed,
  with this comment:

    "As we have not received any duplicates of this bug since January
  and the bug pattern has received no hits, I am going to mark this bug
  report as Fix Released for Precise and set the Oneiric task to Won't
  Fix. In the event that anyone encounters this bug in the future please
  report a new crash report."

  This is that bug report. :)

  Brian also wrote:

    "There really was no clear indication, a changelog for example, that
  bug 628104 was really fixed."

  That might be true.

  A number of users have tried to report the crash through apport, but
  the traceback has always been duped to bug 628104.  Which none of us
  can re-open.

  I myself cannot reproduce it.  The recent information is all at
  628104.  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/982767/+subscriptions