Thanks for Your reply! Of course I'll try dmesg, but: 1) Maybe I didn't describe it precisely enough - the systems (Ubuntu/Xubuntu i386) I checked in VirtualBox were installed on another machine and gave the same results as on my laptop; 2) it's hard to imagine that a corrupted hard disk changes md5sum of a file to md5sum of the file's previous version; 3) I reported similar problem a year ago with 12.04 https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1150737 4) there was no problem with debsums after fresh install of 14.04.0... that's why I thought it's rather packaging problem during building the release iso. Why I marked is as a security issue? If my theory is OK - we have files in our systems that are not updated. Not updated means for me potentially buggy. If this is random situation, out of anyone's control, the problem seems to be serious. Rgds!
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363519 Title: start-stop-daemon fails debsums check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1363519/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
