Public bug reported: ## FFE ## For the Questing release, we are starting to move from Ubuntu Report to Ubuntu Insights, a modernized and ground-up rearchitecture for consensual non-PII telemetry and system information reporting. This FFe is for integration of Ubuntu Insights with gnome-initial-setup, replacing integration with Ubuntu Report via `libsysmetrics` with integration with Ubuntu Insights via `libinsights`.
More specifically, instead of generating reports through Ubuntu Report with extra information from the provisioner and uploading them to Canonical servers based on the consent of the user, we now generate reports with extra information from the provisioner via Ubuntu Insights, save it to disk, and write the relevant consent files to disk based on user choices. If the user returns to the system info page, reports and consent files are overwritten. Uploading is now handled by the `ubuntu- insights` package itself separately, which we expect to be seeded. Should the `ubuntu-insights` package not be present on the system or be non-functional, then the generated files will just live on disk harmlessly. From a user flow perspective, there is no noticeable difference at all besides the presence of generated files in `~/.local/ubuntu-insights/` and `~/.config/ubuntu-insights`, as well as a different “Show the First Report” output. The code changes are relatively minimal, with the UI staying the same. The impact of a regression anywhere in the chain is relatively minimal, as it won’t prevent the user from completing setup. At worst, the user may see a dismissible error pop-up, the same as if an error occurred before with Ubuntu Report/`libsysmetrics`. Please see this pending patch (CI builds are also present): https://salsa.debian.org/gnome-team/gnome-initial- setup/-/merge_requests/65 ### Extra context ### Main inclusion (and seeding) of `ubuntu-insights` is not yet completed at the time of writing, but it has been approved. `ubuntu-insights` MIR: Bug 2118794 FFe for `ubuntu-insights` seeding: Bug 2121164 ### Testing Done ### The test plan used is as follows on a Questing system/VM: 1. Navigate to the telemetry page. 2. Ensure that "Show the First Report" displays a report with source metrics filled in. Take note of the `collectionTime` field. 3. Click next 4. Ensure that three consent files (`consent.toml`, `linux-consent.toml`, `ubuntu_desktop_provision-consent.toml`) were written to `~/.config/ubuntu-insights` and that they each have the contents `consent_state = true`. 5. Ensure that a report was written to `~/.cache/ubuntu-insights/ubuntu_desktop_provision/local/` that matches the one shown in "Show the First Report" (check the `collectionTime` field). 6. Go back to the telemetry page. 7. Select "No, don't share system data". 8. Click next 9. Ensure that the three consent files were overwritten with the content `consent_state = false`. 10. Ensure that the report on disk was overwritten was a report containing just `{"OptOut":true}` ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-initial-setup (Ubuntu) Milestone: None => ubuntu-25.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2121242 Title: [FFE] Integrate Ubuntu Insights Status in gnome-initial-setup package in Ubuntu: New Bug description: ## FFE ## For the Questing release, we are starting to move from Ubuntu Report to Ubuntu Insights, a modernized and ground-up rearchitecture for consensual non-PII telemetry and system information reporting. This FFe is for integration of Ubuntu Insights with gnome-initial-setup, replacing integration with Ubuntu Report via `libsysmetrics` with integration with Ubuntu Insights via `libinsights`. More specifically, instead of generating reports through Ubuntu Report with extra information from the provisioner and uploading them to Canonical servers based on the consent of the user, we now generate reports with extra information from the provisioner via Ubuntu Insights, save it to disk, and write the relevant consent files to disk based on user choices. If the user returns to the system info page, reports and consent files are overwritten. Uploading is now handled by the `ubuntu-insights` package itself separately, which we expect to be seeded. Should the `ubuntu-insights` package not be present on the system or be non-functional, then the generated files will just live on disk harmlessly. From a user flow perspective, there is no noticeable difference at all besides the presence of generated files in `~/.local/ubuntu-insights/` and `~/.config/ubuntu-insights`, as well as a different “Show the First Report” output. The code changes are relatively minimal, with the UI staying the same. The impact of a regression anywhere in the chain is relatively minimal, as it won’t prevent the user from completing setup. At worst, the user may see a dismissible error pop- up, the same as if an error occurred before with Ubuntu Report/`libsysmetrics`. Please see this pending patch (CI builds are also present): https://salsa.debian.org/gnome-team/gnome-initial- setup/-/merge_requests/65 ### Extra context ### Main inclusion (and seeding) of `ubuntu-insights` is not yet completed at the time of writing, but it has been approved. `ubuntu-insights` MIR: Bug 2118794 FFe for `ubuntu-insights` seeding: Bug 2121164 ### Testing Done ### The test plan used is as follows on a Questing system/VM: 1. Navigate to the telemetry page. 2. Ensure that "Show the First Report" displays a report with source metrics filled in. Take note of the `collectionTime` field. 3. Click next 4. Ensure that three consent files (`consent.toml`, `linux-consent.toml`, `ubuntu_desktop_provision-consent.toml`) were written to `~/.config/ubuntu-insights` and that they each have the contents `consent_state = true`. 5. Ensure that a report was written to `~/.cache/ubuntu-insights/ubuntu_desktop_provision/local/` that matches the one shown in "Show the First Report" (check the `collectionTime` field). 6. Go back to the telemetry page. 7. Select "No, don't share system data". 8. Click next 9. Ensure that the three consent files were overwritten with the content `consent_state = false`. 10. Ensure that the report on disk was overwritten was a report containing just `{"OptOut":true}` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2121242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
