[Bug 218422] Re: dpkg seems to not always report an error state correctly which results in SIGSEGV on apt next call

Launchpad Bug Tracker 218422 at bugs.launchpad.net
Wed May 25 04:18:02 UTC 2011


[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apt (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/218422

Title:
  dpkg seems to not always report an error state correctly which results
  in SIGSEGV on apt next call

Status in “apt” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: dpkg

  Sometimes, dpkg seems not to report a failed exit state correctly.

  Symptoms: 
  apt or any package manager invoking apt fails after certain dpkg failures with a SIGSEGV.

  Fix:
  running 'sudo dpkg --configure -a && apt-get install' solves the problem in every case.

  test case: 
  unable to find a test case since I was not able to find a corresponding package so far.

  The only thing I can say about this one is: for all I know this
  happened on Ubuntu Hardy (8.04) 4 times and in Ubuntu 6.10.1 1 time so
  far.

  best regards,
  Kai




More information about the foundations-bugs mailing list