[Bug 948656] Re: mistakenly running `apport-kde core` crashes

[Launchpad Bug Tracker]

[Expired for apport (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apport (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  mistakenly running `apport-kde core` crashes

Status in apport package in Ubuntu:
  Expired

Bug description:
  I'm running Kubuntu 12.04 alpha2 amd64 with all the daily System
  Updates, and apport-kde version 1.94-0ubuntu1

  I was trying to reproduce an apport-kde bug , so I ran
    apport-kde core
  in a directory that had a core file in it

  Bad idea.  I get a "Collecting problem Information" dialog, then an alert
    Invalid problem report
    Package core does not exist
  and when I OK the dialog, I get KDE's Crash Handler:
    We are sorry, Apport KDE closed unexpectedly
    ...
    Details:
    Executable: python2.7 PID: 15862 Signal: Segmentation fault (11)

  Expected results:
  I typed the wrong thing, but the crash reporter shouldn't itself crash :-)

  This happens every time on two core files I have lying around,
  ("/home/skierpage/core: ELF 64-bit LSB core file x86-64, version 1
  (SYSV), SVR4-style, from '/usr/lib/libreoffice/program/soffice.bin
  /tmp/foo.pps --splas'" and "core: ELF 64-bit LSB core file x86-64,
  version 1 (SYSV), SVR4-style, from './crasher'"). The stack trace is
  attached, it's always the same, QWidget::~QWidget called from
  sipQtGuipart9.cpp etc.

  If I click [Report Bug] in the KDE Crash Handler then I'm in another
  maze of woe because the KDE Crash Reporting Assistant endlessly
  invites me to Install Debug Symbols yet still says "The generated
  crash information is probably not useful"..., but I think drkonqi s a
  different package.

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