Bug 590315 - [abrt] crash in telepathy-haze-0.3.1-4.fc12: haze_close_account_request: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
[abrt] crash in telepathy-haze-0.3.1-4.fc12: haze_close_account_request: Proc...
Status: CLOSED DUPLICATE of bug 556162
Product: Fedora
Classification: Fedora
Component: telepathy-haze (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Peter Gordon
Fedora Extras Quality Assurance
abrt_hash:c498e87073fb7eed6e32c435fe8...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-08 15:31 EDT by __UNIX_hokum
Modified: 2010-05-25 05:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 05:50:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (17.98 KB, text/plain)
2010-05-08 15:31 EDT, __UNIX_hokum
no flags Details

  None (edit)
Description __UNIX_hokum 2010-05-08 15:31:24 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-haze
component: telepathy-haze
crash_function: haze_close_account_request
executable: /usr/libexec/telepathy-haze
global_uuid: c498e87073fb7eed6e32c435fe8ae372ee67440f
kernel: 2.6.32.11-99.fc12.i686.PAE
package: telepathy-haze-0.3.1-4.fc12
rating: 4
reason: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 __UNIX_hokum 2010-05-08 15:31:27 EDT
Created attachment 412562 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:50:38 EDT

*** This bug has been marked as a duplicate of bug 556162 ***
Comment 3 Karel Klíč 2010-05-25 05:50:38 EDT
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #556162.

Sorry for the inconvenience.

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