This bug was fixed in the package live-build - 3.0~a57-1ubuntu16.3
---
live-build (3.0~a57-1ubuntu16.3) vivid; urgency=medium
* debian/patches/upstart-not-in-bootstrap: Rewrite the old user-sessions
patch to handle when upstart isn't in the bootstrap set (LP: #1477051)
live-bui
This bug was fixed in the package live-build - 3.0~a57-1ubuntu11.2
---
live-build (3.0~a57-1ubuntu11.2) trusty; urgency=medium
* debian/patches/upstart-not-in-bootstrap: Rewrite the old user-sessions
patch to handle when upstart isn't in the bootstrap set (LP: #1477051)
live-bu
SRU verified per the test case on trusty, vivid, and wily.
** Tags removed: verification-needed
** Tags added: verification-done
--
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-s
Hello Rafał, or anyone else affected,
Accepted live-build into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/live-
build/3.0~a57-1ubuntu16.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Also affects: live-build (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: live-build (Ubuntu Trusty)
Assignee: (unassigned) => Adam Conrad (adconrad)
** Changed in: live-build (Ubuntu Vivid)
Assignee: (unassigned) => Adam Conrad (adconrad)
** Changed in: liv
Hello Rafał, or anyone else affected,
Accepted live-build into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/live-
build/3.0~a57-1ubuntu11.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. Se
This bug was fixed in the package live-build - 3.0~a57-1ubuntu19
---
live-build (3.0~a57-1ubuntu19) wily; urgency=medium
* debian/patches/dpkg-divert-{initctl,others}: Pull two commits from git
upstream to resolve issues where we would end up with files from their
release ve
** Description changed:
+ [ SRU Justification ]
+ Currently, systems installed from live media have several critical files
(like initctl and start-stop-daemon) failing debsums checks because they are
incorrectly using the files from the release pocket versions of their packages,
rather than the
** Also affects: live-build (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: live-build (Ubuntu Wily)
Status: New => Triaged
** Changed in: live-build (Ubuntu Wily)
Importance: Undecided => High
** Changed in: live-build (Ubuntu Trusty)
Importance: Undecided
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: live-build (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363519
T
As of today, debsums -c reports me
debsums -c
/usr/lib/x86_64-linux-gnu/gbm/old.gbm_gallium_drm.so
/usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0
Please, please, clean up all the wrong entries. There should be a test
which any package must pass before it can be rolled out.
The test should also in
** Package changed: dpkg (Ubuntu) => live-build (Ubuntu)
** Also affects: live-build (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363519
Spotted this again on a fresh 14.04.1 LTS server (amd64) installation.
Applied workaround from
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1363519/comments/11
and added it as another post-inst thing to do on all my installations,
along with a verification ("dpkg -V"/debsums/tripwire/etc).
Is there any workaround?
--
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/
To track it down, I took the 14.04.1 media
119cb63b48c9a18f31f417f09655efbd again and installed it without any
updates.
Doing that, I got the two
144bf4beed11fb77e5ad629452741310 /boot/vmlinuz-3.13.0-32-generic
b1b8894ae2e3b547dca0e288634cce4a /sbin/start-stop-daemon
again. So, the problem shoul
I am very concerned about this issue. I installed from media
119cb63b48c9a18f31f417f09655efbd ubuntu-14.04.1-desktop-amd64.iso. I
double-checked the hash comes from a SSL-trusted page and checked the
md5 sum of the file which was correct.
However, I also get
md5sum /boot/vmlinuz-3.13.0-32-generic
Just chipping in that I have just encountered this exact bug as reported
by Rafał Roncoszek on an Ubuntu Server 14.04.1 x64 server I admin. Was
initially very concerned to see a critical system binary failing a
debsums check but the md5sum's of the failing binary and the updated
binary via a 'apt-g
Tomorrow at work I'll try to get the syslogs of the VBox installations of
Ubuntu/Xubuntu i386.
Rgds!
** Attachment added: "/var/log/installer/syslog"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1363519/+attachment/4219638/+files/sys.txt
--
You received this bug notification because
Could you please include the log file from your install of Ubuntu? It
can be found in /var/log/installer/syslog. Thanks!
--
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-daem
Just a quick note that I've seen several bug reports filed since this
one that included some Dependencies.txt files with lines like "modified:
sbin/start-stop-daemon" -- I think this is more widespread than this bug
indicates. See 1374670 for an example.
--
You received this bug notification beca
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dpkg (Ubuntu)
Status: New => Confirmed
--
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
I'm seeing the exact same thing. On a fresh Ubuntu Server 14.04.1
install:
root@server1:~# md5sum /sbin/start-stop-daemon
b1b8894ae2e3b547dca0e288634cce4a /sbin/start-stop-daemon
root@server1:~# apt-get install --reinstall dpkg
Reading package lists... Done
Building dependency tree
Reading
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
BTW, please check dmesg output for error messages that may indicate
failing hardware -- most similar reports are filed when user's hard
drives are near death.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
25 matches
Mail list logo
