This bug was fixed in the package apport - 2.20.7-0ubuntu3.8

apport (2.20.7-0ubuntu3.8) artful; urgency=medium

  * data/general-hooks/ Only include JournalErrors for apport-crash
    reports which are private by default. (LP: #1738581)

 -- Brian Murray <>  Fri, 30 Mar 2018 09:43:05 -0700

** Changed in: apport (Ubuntu Artful)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  apport attachment JounralErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Artful:
  Fix Released

Bug description:
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report
  created with ubuntu-bug.

  Original Description

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to