The errors are intercepted correctly when using the "Continue" button.
But when using "Show details", the exceptions flow a different way.

** Description changed:

- no se que paso despues de actualizar pasa esto
+ TEST CASE:
+ - Produce a crash report: sh -c 'kill -SEGV $$'; close the Apport popup 
window.
+ - Edit /var/crash/_bin_dash.1000.crash; remove a few characters at the end of 
the CoreDump field (at the very end of the file)
+ - Apport pops up again; click on "Show Details...", analysis will start, and 
hang forever
+ - Apport should pop up a second time, for apport-gtk itself.
+ 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportLog:
-  
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 19 20:56:48 2014
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2013-12-16 (65 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
-  SHELL=/bin/bash
-  LANG=es_CO.UTF-8
-  LANGUAGE=es_CO:es
-  PATH=(custom, no user)
+  SHELL=/bin/bash
+  LANG=es_CO.UTF-8
+  LANGUAGE=es_CO:es
+  PATH=(custom, no user)
  PythonArgs: ['/usr/share/apport/apport-gtk']
  SourcePackage: apport
  Title: apport-gtk crashed with EOFError in _read_exact(): Compressed file 
ended before the end-of-stream marker was reached
  UpgradeStatus: Upgraded to trusty on 2013-12-18 (64 days ago)
  UserGroups:

** Summary changed:

- apport-gtk crashed with EOFError in _read_exact(): Compressed file ended 
before the end-of-stream marker was reached
+ Crashes on invalid/broken core dumps when using "Show details..."

** Changed in: apport (Ubuntu Untitled)
   Importance: Undecided => High

** No longer affects: python

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

Title:
  Crashes on invalid/broken core dumps when using "Show details..."

Status in “apport” package in Ubuntu:
  Triaged
Status in “apport” source package in Trusty:
  Triaged
Status in “apport” source package in u-series:
  In Progress

Bug description:
  TEST CASE:
  - Produce a crash report: sh -c 'kill -SEGV $$'; close the Apport popup 
window.
  - Edit /var/crash/_bin_dash.1000.crash; remove a few characters at the end of 
the CoreDump field (at the very end of the file)
  - Apport pops up again; click on "Show Details...", analysis will start, and 
hang forever
  - Apport should pop up a second time, for apport-gtk itself.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportLog:
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 19 20:56:48 2014
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2013-12-16 (65 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   SHELL=/bin/bash
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
  PythonArgs: ['/usr/share/apport/apport-gtk']
  SourcePackage: apport
  Title: apport-gtk crashed with EOFError in _read_exact(): Compressed file 
ended before the end-of-stream marker was reached
  UpgradeStatus: Upgraded to trusty on 2013-12-18 (64 days ago)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to