Bug 613289 - [abrt] crash in berusky-1.1-13.fc13: raise: Process /usr/bin/berusky was killed by signal 6 (SIGABRT)
[abrt] crash in berusky-1.1-13.fc13: raise: Process /usr/bin/berusky was kill...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: berusky (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Martin Stransky
Fedora Extras Quality Assurance
abrt_hash:214d11a9afc3b97e89fb7d22d21...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-10 09:42 EDT by fanbt
Modified: 2011-01-15 14:23 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-15 14:23:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description fanbt 2010-07-10 09:42:37 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: berusky
component: berusky
crash_function: raise
executable: /usr/bin/berusky
global_uuid: 214d11a9afc3b97e89fb7d22d211d141383dd819
kernel: 2.6.33.6-147.fc13.x86_64
package: berusky-1.1-13.fc13
rating: 4
reason: Process /usr/bin/berusky was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Martin Stransky 2011-01-15 14:23:35 EST
Hm, unfortunately the backtrace is missing. Can you please file it again when you manage to get one?

Note You need to log in before you can comment on or make changes to this bug.