Successfully verified fixed in focal-proposed.
I did the following to test and validate, in a fully up-to-date focal amd64 VM:
- sudo apt install chromium-browser
- chromium-browser # to ensure a profile folder is created, then close chromium
- ubuntu-bug chromium-browser
# observe the traceback in the terminal, and the "HookError_chromium_browser"
section in the summary, choose to not submit the report
# add focal-proposed universe to sources.list
- sudo apt update
- sudo apt dist-upgrade # chromium-browser is updated from
1:85.0.4183.83-0ubuntu0.20.04.1 to 1:85.0.4183.83-0ubuntu0.20.04.2
- ubuntu-bug chromium-browser
# observe there is no traceback in the terminal anymore, no
"HookError_chromium_browser" section in the summary, and there are sections
with details extracted from the profile directory ("Snap.ChromiumVersion",
"Snap.ChromiumPrefs")
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1900170
Title:
apport hook looks for snap profile folder in the wrong place
Status in chromium-browser package in Ubuntu:
Fix Released
Status in chromium-browser source package in Focal:
Fix Committed
Bug description:
Since https://git.launchpad.net/~chromium-team/chromium-browser/+git
/snap-from-source/commit/?id=d7e3b7f8, the default profile directory
for the chromium snap was moved from $SNAP_USER_DATA to
$SNAP_USER_COMMON (to mitigate the effects of bug #1616650).
But the apport hook in the transitional deb package wasn't updated
accordingly.
[Impact]
Bugs filed with `ubuntu-bug chromium-browser` have incomplete data
attached. See e.g. the attachements to bug #1899356. There's a file
called HookError_chromium_browser.txt with a python traceback because
the profile directory wasn't found in the expected location.
[Test Case]
In focal, apt install chromium-browser, then run chromium at least
once to ensure there is a profile directory (under
$HOME/snap/chromium/common/chromium), then run `ubuntu-bug chromium-
browser`. Observe that there isn't a FileNotFoundError traceback in
the terminal for an unknown profile directory, and that the apport
dialog with a summary of the information to be posted doesn't contain
a "HookError_chromium_browser" entry.
[Regression Potential]
This affects only the apport hook for chromium-browser, the
application itself shouldn't be affected. The hook should be verified
to continue working by running the `ubuntu-bug chromium-browser`
command and carefully inspecting the information that would be sent to
launchpad.
[Original description]
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 16 18:40:02 2020
InstallationDate: Installed on 2020-09-16 (29 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900170/+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
