Hello Olivier, or anyone else affected, Accepted chromium-browser into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chromium- browser/1:85.0.4183.83-0ubuntu2.22.10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: chromium-browser (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic ** Changed in: chromium-browser (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1993191 Title: apport hook that collects snap's information is outdated Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Fix Committed Status in chromium-browser source package in Jammy: Fix Committed Status in chromium-browser source package in Kinetic: Fix Committed Bug description: Impact ------ The Apport hook of the Chromium browser is outdated. It collects information about core18, but the snap uses core20. Moreover, it does not collect information about other interface providers. Test plan --------- 1. Install the current chromium-browser. 2. Generate a report with apport-bug --save /tmp/c1 chromium-browser 3. Install chromium-browser from proposed. 4. Generate another report with apport-bug --save /tmp/c2 chromium-browser Note: If the package was built and generated locally, you will need APPORT_DISABLE_DISTRO_CHECK=1 in the environment. 5. Compare the files. The meaningful differences should be in the Snap.Info.xxxx sections, namely: - Snap.Info.core18 -> Snap.Info.core20 - {None} -> Snap.Info.cups - {None} -> Snap.Info.gnome-3-38-2004 Differences should not be observed in Snap.Info.{chromium,core,gtk- common-themes}. Regression potential -------------------- Being Apport a bug reporting program, an incorrect parsing of the SNAP_META file could lead to insertion of unwanted information in the report or to suppress the insertion of information about the relevant interfaces. Original report --------------- See https://bazaar.launchpad.net/~chromium-team/chromium- browser/groovy-stable/view/head:/debian/apport/chromium- browser.py#L59. It collects information about core18, but the chromium snap was rebased on core20 almost a year ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
