[Bug 1451565] Re: /var/log owned by wrong group (android_input) (again)
Selene Scriven
selene.scriven at canonical.com
Wed Sep 16 03:18:07 UTC 2015
I find it trivial to reproduce this issue:
1. adb reboot bootloader
2. ubuntu-device-flash foo
3. Note that syslog works normally.
4. adb reboot bootloader
5. ubuntu-device-flash foo
6. Note that syslog no longer works.
Steps 4/5/6 can be repeated if desired. The only way I've found to get
a good flash again is to flash a different build number.
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_input) (again)
Status in Canonical System Image:
Confirmed
Status in livecd-rootfs package in Ubuntu:
Incomplete
Bug description:
Bug 1425529 (or bug 1425869) is back. No syslog on arale image 31 and
krillin vivid 188 (which are about two weeks apart), and possibly on
other builds too. I'm not sure how widespread it is, but I've run
into this several times lately.
Sorry for the dupe, I was asked to create a new bug for it instead of
re-opening one of the previous two.
Test Case 1:
1. make the system writable
2. sudo vim.tiny /etc/system-image/channel.ini
3. Change the image number in the lower lines to be back 10 images
4. remove writable and rm .local/share/ubuntu-push-client/level.db
5. reboot
6. upgrade post upgrade check /var/log
Test Case 2:
1. Flash the latest rc-proposed to the device under test
2. run some tests
3. make the system writeable
4. add a silo
5. reflash the same image to the same device (we use bootstrap from fastboot for flashing purposes)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1451565/+subscriptions
More information about the foundations-bugs
mailing list