I have been unable to reproduce this in my tests. I've been using
software-center, since that uses aptdaemon. I tried installing kword;
you said "the libc-bin postinst script caused an apparently abrupt end
in the logging", but that's simply the last thing that runs in that
installation (libc-bin ships the ldconfig trigger, run at the end of
most installations that include libraries). I also tried installing a
random small unimportant package (knews - not a KDE package, despite the
name) that I knew to use debconf, in case that was the determining
factor, but I couldn't make it fail regardless of the setting of
debconf/priority.
Could you please give me some kind of specific test sequence that I can
run to reproduce this bug?
** Changed in: apt (Ubuntu Natty)
Status: Confirmed => Incomplete
** Changed in: dpkg (Ubuntu Natty)
Status: Confirmed => Incomplete
** Changed in: apt (Ubuntu Natty)
Assignee: Canonical Foundations Team (canonical-foundations) => Colin
Watson (cjwatson)
** Changed in: dpkg (Ubuntu Natty)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680328
Title:
Many postinst scripts fail using either AptDaemon, PackageKit, or QApt
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
