@ondra - can you take a look at this during the next bring up you do
(without mentioning the details here).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group
This is happening again very frequently when reflashing a phone (krillin
rc-proposed 286 in this case). I insist but it is really an annoyance to
debug any issue on the phone. when you get an issue and realize there is
no syslog, it is already too late to fix is manually.
--
You received this bug
** Changed in: livecd-rootfs (Ubuntu)
Status: Expired => Confirmed
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
[Expired for livecd-rootfs (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: livecd-rootfs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Yes, this is still happening as of tonight's latest image (arale rc-
proposed 183). The first flash works, while every subsequent flash of
the same image has the wrong permissions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Tags removed: hotfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_input) (again)
To manage notifications about this bug go to:
https://bugs
Is this still the case? I didn't reflash my phone but the group-
assignment looks fine on my device. Can anyone try to reproduce?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/lo
the /var/log directory needs to be "root:syslog" ... the syslog file
(and others) in the directory needs to be "syslog:adm"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owne
On my krillin running ota7 stable via update, syslog was assigned group
syslog not adm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_input) (aga
@John, could someone have a look again? It is still happening on OTA7
candidate even after flashing with --bootstrap. It makes bugs
investigation very difficult because most of the time you realize there
is no syslog when you need it.
--
You received this bug notification because you are a member
** Changed in: canonical-devices-system-image
Status: Confirmed => Won't Fix
** Changed in: canonical-devices-system-image
Status: Won't Fix => Incomplete
** Changed in: canonical-devices-system-image
Milestone: ww40-2015 => backlog
--
You received this bug notification becaus
** Tags added: hotfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_input) (again)
To manage notifications about this bug go to:
https://bugs.l
Just to add to the fire, we have a report from a user in India who
purchased a MX4 which has no syslog. It's running OTA6, and no other
software has been side-loaded. The phone also is having
interoperability problems with certain operators. Let's hope these
issues aren't caused by other permis
It seems possible that devices sold in India may have been re-flashed
with a new custom tarball at the factory, so the scenario posited in my
previous comment isn't as exceptional as first thought... However it's
still makes it more important that we get to the root of this, as we
really don't wa
So the double-flash at the factory is still just a theory...
What was confirmed was that the user restored the device to factory
default settings using System Settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
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
** Description changed:
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
I have seen this most frequently when doing the following steps:
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
@toykeeper: you say you 'reflash the same image'. How?
** Changed in: canonical-devices-system-image
Status: Confirmed => Incomplete
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It happened again on arale 113
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015
--
You received this bug no
@john is this yours?
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John McAleely (john.mcaleely)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log
I forgot to work around this bug today and ended up not able to get
syslog data for ~18 hours of tests. D'oh. My own fault, but I hope
we'll find a fix for this soon. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
hm, that looks very much like udev misbehaving or as if androids ueventd
tinkers with the UUIDs when the container comes up (note that we should
mount by label everywhere nowadays though)
or perhaps there is a difference in the disk related udev rules inside
the initrd vs the ones on the rootfs
-
While reviewing a silo I was investigating lp:1471338 with boiko and we
were both stymied trying to find the syslog--this fix would be really
really helpful for basic debugging. IIRC I was on arale shortly before
OTA-5.
--
You received this bug notification because you are a member of Ubuntu
Bug
** Also affects: canonical-devices-system-image
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/1451565
Title:
/var/log owned by wrong group (android_input)
Additionally, the permissions of /var/log aren't the only thing which
change when re-flashing the same image.
I collected the output of 'ls -alR /' during the first and second flash,
filtered it a bit to remove most of the noise, and diff'd the two to
look for differences. Some of the results are
FWIW, removing the UDF cache has no effect on the results for this bug.
However, changing to a different image number seems to fix the
permission issues.
So. To make the flash work correctly, make sure the new image isn't the
same number as the old image. To make the permissions break, flash the
As far as I can tell, the first time I flash an image the permissions
are correct. The second and later times I flash the same image, the
permissions are incorrect. I'm not why it matters that the image has
been flashed before.
--
You received this bug notification because you are a member of U
Scratch that. It's definitely intermittent. I reflashed 38 and now
/var/log is broken again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_inp
Image 38 seems fine. I'm not sure if it's fixed or if it's
intermittent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_input) (again)
To manag
I'm seeing the issue on arale image 32 too, flashed just a moment ago.
Krillin rtm 274 seems fine though, so today's milestone candidate isn't
affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14
hmm, i can not confirm that on either of my devices here ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451565
Title:
/var/log owned by wrong group (android_input) (again)
To manage notificatio
32 matches
Mail list logo
