[Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all at 168:collect_info:process_report

[Łukasz Zemczak]

Ok, the verification looks good. As per request I will be releasing this
slightly earlier - I think 5+ days is enough of a wait anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1848064

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all at 168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which are not owned by root if /proc/sys/fs/protected_regular is set to 1. Subsequently, the crash reports are incomplete and not getting uploaded to the Error Tracker therefore Ubuntu developers may be missing out on important crash reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we should also test the case where /proc/sys/fs/protected_regular is set to 0. This can be done by manually changing the value and running through the test case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  --------------------
  The Ubuntu Error Tracker has been receiving reports about a problem regarding apport.  This problem was most recently seen with package version 2.20.11-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+subscriptions