That must be it.
It's still a latent or potential bug in the transitional sreadahead
package. It replaces a package which asked to be triggered; its
postinst script should therefore silently ignore "triggered" state.
Attachment: output of --
cd /var/log
(zcat dpkg.log.{10,9,8,7,6,5,4,3,2}.gz; cat dpkg.log{.1,}) |
egrep 'chrome.*r33[49]|readahead' /tmp/dl |
uniq -c | sed 's/^ *//'
which shows the life history of the readahead/sreadahead/ureadahead
family on this system, plus the most recent chrome upgrade (for
reference, since it was done at the same time as the most recent
[su]readahead upgrade -- subsequent items are due to manual
install/remove/etc.)
** Attachment added: "*sreadahead* history from dpkg.log"
http://launchpadlibrarian.net/36684873/dpkg-excerpts-494350.log
--
/var/lib/dpkg/info/sreadahead.postinst called with unknown argument `triggered'
https://bugs.launchpad.net/bugs/494350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
