This bug was fixed in the package ubiquity - 18.04.14.2
---
ubiquity (18.04.14.2) bionic; urgency=medium
* Switch to use uptime instead of time.time() which is sensitive to
BIOS time reset after NTP sync, leading to negative values.
(LP: #1771966)
* Don't record telemetry
SRU verification for Bionic:
I have reproduced the problem with ubiquity 18.04.14.1 in bionic-updates and
have verified that the version of ubiquity 18.04.14.2 in -proposed fixes the
issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-bionic
** Tags
Hello Adam, or anyone else affected,
Accepted ubiquity into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/18.04.14.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package ubiquity - 18.10.3
---
ubiquity (18.10.3) cosmic; urgency=medium
* Don't record telemetry data when doing stage 2 (user mode) as it keeps an
unused /target directory (LP: #1773321) Also, record OEM types
(LP: #1765693)
* Switch to use
** Description changed:
- Experimenting with an oem install, after the user setup and the
- installation is complete there is a /target/var/log/installer/telemetry
- file. This file location seems to be hard coded into ubiquity, but
- there is no /target at the oem user setup stage.
+ [Impact]
+
** Merge proposal linked:
https://code.launchpad.net/~didrocks/ubiquity/+git/ubiquity/+merge/347043
** Merge proposal linked:
https://code.launchpad.net/~didrocks/ubiquity/+git/ubiquity/+merge/347044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks to both of you! That's clear, and I never checked/noticed the
second one. I'll have a look at how to differentiate it (probably
tomorrow). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@didrocks, put differently after the end user setup there are 2
telemetry files: /target/var/log/installer/telemetry and
/var/log/installer/telemetry
The former must not be created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see now my initial description was probably not the clearest since
there is an OEM user account. What I was referring to was the end user
setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There are two stages to an OEM install; preparing the image for shipping
and the user first boot.
Preparing for shipping is fine, but when ubiquity runs on the user first
boot there is no /target as far as I'm aware. This is when ubiquity
creates a /target folder with the telemetry file in it.
I tried both on Bionic and Cosmic desktop 20180528 and I can't reproduce the
option, choosing the "OEM" option at startup. Note that this is what I tested
before mergintg the changes.
Both have /target/var/log/…
This is indeed hardcoded alongside other paths in ubiquity which have /target
Thanks for your report.
Confirmed with Ubuntu Cosmic desktop 20180528
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
**
12 matches
Mail list logo
