[Bug 1733567] [NEW] apport fails to send crash reports

Tue Nov 21 11:28:24 UTC 2017

Public bug reported:

There's an ongoing issue with gnome-shell crashing during or on exit
from screen lock. I am no longer able to report when this happens
because apport silently refuses to send the bug report.

If the automatic whoopsie dialog opens at all (it doesn't, often), and I
click to send the report, the window closes, and that's it. If I try to
use apport-cli to send a specific .crash file, it shows me the menu, I
type S to send the report, and apport-cli exits immediately, and again
there's no further action.

The crashes may be similar to those posted before, although this being
an ongoing and unfixed issue (eg: bug #1723620, bug #1723615), one would
expect to be able to send updated bug reports at least to show that, eg:
a newer version of the affected packages didn't fix it, or to add a new
observation (in this case that despite the crash my login session was
not ended by it, which is new). At the very least one would expect to
see either the list of possible duplicates, or at very *very* least, a
message saying that it's been submitted alreadyk or that my version of
the affected package is obsolete (it isn't, although I see apport itself
is getting an upgrade, but this problem has already persisted through a
few apport upgrades). But there's nothing, no feedback at all, it just
exits.

I wonder also if what's failed here is the ability to open a new browser
window, but if so it affects both google chrome and firefox, when each
is set to be the default browser. Also, *this* bug, initiated by typing
"ubuntu-bug apport", was submitted just fine, but this bug is not the
result of an actual *crash* (ie: resulting in a .crash file).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.4
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportLog:
 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: called for pid 24462, signal 11, core limit 0, dump mode 1
 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: debug: session gdbus call: (true,)

 ERROR: apport (pid 7178) Tue Nov 21 11:06:06 2017: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 21 11:15:54 2017
InstallationDate: Installed on 2017-07-30 (113 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to artful on 2017-08-22 (90 days ago)

** Affects: apport (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-bug artful

-- 
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/1733567

Title:
  apport fails to send crash reports

Status in apport package in Ubuntu:
  New

Bug description:
  There's an ongoing issue with gnome-shell crashing during or on exit
  from screen lock. I am no longer able to report when this happens
  because apport silently refuses to send the bug report.

  If the automatic whoopsie dialog opens at all (it doesn't, often), and
  I click to send the report, the window closes, and that's it. If I try
  to use apport-cli to send a specific .crash file, it shows me the
  menu, I type S to send the report, and apport-cli exits immediately,
  and again there's no further action.

  The crashes may be similar to those posted before, although this being
  an ongoing and unfixed issue (eg: bug #1723620, bug #1723615), one
  would expect to be able to send updated bug reports at least to show
  that, eg: a newer version of the affected packages didn't fix it, or
  to add a new observation (in this case that despite the crash my login
  session was not ended by it, which is new). At the very least one
  would expect to see either the list of possible duplicates, or at very
  *very* least, a message saying that it's been submitted alreadyk or
  that my version of the affected package is obsolete (it isn't,
  although I see apport itself is getting an upgrade, but this problem
  has already persisted through a few apport upgrades). But there's
  nothing, no feedback at all, it just exits.

  I wonder also if what's failed here is the ability to open a new
  browser window, but if so it affects both google chrome and firefox,
  when each is set to be the default browser. Also, *this* bug,
  initiated by typing "ubuntu-bug apport", was submitted just fine, but
  this bug is not the result of an actual *crash* (ie: resulting in a
  .crash file).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: called for pid 24462, signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: debug: session gdbus call: (true,)

   ERROR: apport (pid 7178) Tue Nov 21 11:06:06 2017: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 21 11:15:54 2017
  InstallationDate: Installed on 2017-07-30 (113 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-08-22 (90 days ago)

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