We've agreed with Benjamin that the current fix is probably the way to
go for the SRU, while we work on the overall design to make this less
fragile (which would probably be way too much invasive for an SRU).
** Description changed:
- From what I can tell when I click the send button to send a crash report
- to the Error Tracker the crash doesn't actually get sent. My testing
- process follows:
+ [ Impact ]
+
+ Crash reports aren't sent in when going through the UI, unless the user
+ looks at the crash details.
+
+ [ Test Plan ]
+
+ 0) Make sure that error reporting is set to manual in the system settings (in
Privacy screen)
+ 1) Launch xeyes
+ 2) pkill -11 xeyes
+ 3) Click send in the apport dialog. DO NOT look at the details of the report.
+ 4) ls -lh /var/crash/*xeyes*
+
+ There should be 3 files:
+
+ -rw-r----- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash
+ -rw-rw-r-- 1 bdmurray bdmurray 0 Oct 6 11:53
_usr_bin_xeyes.1000.upload
+ -rw------- 1 whoopsie whoopsie 37 Oct 6 11:53
_usr_bin_xeyes.1000.uploaded
+
+ [ Where problems could occur ]
+
+ If the patch is wrong, we actually see similar bugs for other UI paths,
+ e.g. ticking the "Remember this" box, etc. I tried to cover them during
+ manual testing but I might have missed some.
+
+ [ Other Info ]
+
+ If possible I'd like for us not to wait too long for this to mature in
-proposed, as this would affect crashes during the upgrade.
+
+ [ Original report ]
+ From what I can tell when I click the send button to send a crash report to
the Error Tracker the crash doesn't actually get sent. My testing process
follows:
1) Launch xeyes
2) pkill -11 xeyes
3) Click send in the apport dialog
4) ls -lh /var/crash
I would expect there to be three files in /var/crash:
-rw-r----- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash
-rw-rw-r-- 1 bdmurray bdmurray 0 Oct 6 11:53
_usr_bin_xeyes.1000.upload
-rw------- 1 whoopsie whoopsie 37 Oct 6 11:53
_usr_bin_xeyes.1000.uploaded
However, after step #4 I'm only seeing the .crash file and not a .upload
or .uploaded. I was able to get the .upload and .uploaded files created
if I chose to "View Report" and then click "Send".
It's worth noting though that I did notice the size of the .crash file
increase after clicking "Send" so some post-processing was done.
- ProblemType: Bug
- DistroRelease: Ubuntu 23.10
+ ProblemType: BugDistroRelease: Ubuntu 23.10
Package: apport 2.27.0-0ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 6 12:12:46 2023
InstallationDate: Installed on 2022-01-07 (637 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
- PackageArchitecture: all
- SourcePackage: apport
+ PackageArchitecture: allSourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: apport (Ubuntu Lunar)
Assignee: Benjamin Drung (bdrung) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2038650
Title:
crash reports not sent to the Error Tracker
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Lunar:
Confirmed
Status in apport source package in Mantic:
Fix Released
Bug description:
[ Impact ]
Crash reports aren't sent in when going through the UI, unless the
user looks at the crash details.
[ Test Plan ]
0) Make sure that error reporting is set to manual in the system settings (in
Privacy screen)
1) Launch xeyes
2) pkill -11 xeyes
3) Click send in the apport dialog. DO NOT look at the details of the report.
4) ls -lh /var/crash/*xeyes*
There should be 3 files:
-rw-r----- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash
-rw-rw-r-- 1 bdmurray bdmurray 0 Oct 6 11:53
_usr_bin_xeyes.1000.upload
-rw------- 1 whoopsie whoopsie 37 Oct 6 11:53
_usr_bin_xeyes.1000.uploaded
[ Where problems could occur ]
If the patch is wrong, we actually see similar bugs for other UI
paths, e.g. ticking the "Remember this" box, etc. I tried to cover
them during manual testing but I might have missed some.
[ Other Info ]
If possible I'd like for us not to wait too long for this to mature in
-proposed, as this would affect crashes during the upgrade.
[ Original report ]
From what I can tell when I click the send button to send a crash report to
the Error Tracker the crash doesn't actually get sent. My testing process
follows:
1) Launch xeyes
2) pkill -11 xeyes
3) Click send in the apport dialog
4) ls -lh /var/crash
I would expect there to be three files in /var/crash:
-rw-r----- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash
-rw-rw-r-- 1 bdmurray bdmurray 0 Oct 6 11:53
_usr_bin_xeyes.1000.upload
-rw------- 1 whoopsie whoopsie 37 Oct 6 11:53
_usr_bin_xeyes.1000.uploaded
However, after step #4 I'm only seeing the .crash file and not a
.upload or .uploaded. I was able to get the .upload and .uploaded
files created if I chose to "View Report" and then click "Send".
It's worth noting though that I did notice the size of the .crash file
increase after clicking "Send" so some post-processing was done.
ProblemType: BugDistroRelease: Ubuntu 23.10
Package: apport 2.27.0-0ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 6 12:12:46 2023
InstallationDate: Installed on 2022-01-07 (637 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: allSourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
