Bug 717209 - [abrt] spice-client-0.8.0-2.el6: __cxa_call_terminate: Process /usr/bin/spicec was killed by signal 6 (SIGABRT)
Summary: [abrt] spice-client-0.8.0-2.el6: __cxa_call_terminate: Process /usr/bin/spice...
Keywords:
Status: CLOSED DUPLICATE of bug 692833
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-client
Version: 6.1
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:ca71a9653bb9f023e132541af6d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-28 11:30 UTC by David Jaša
Modified: 2011-07-11 12:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-11 12:30:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
File: backtrace (20.00 KB, text/plain)
2011-06-28 11:30 UTC, David Jaša 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2011-06-28 11:30:21 UTC 
abrt version: 1.1.16
architecture: x86_64
Attached file: backtrace, 20478 bytes
cmdline: /usr/libexec/spicec --controller
comment: not really reproducible
component: spice-client
Attached file: coredump, 98070528 bytes
crash_function: __cxa_call_terminate
executable: /usr/bin/spicec
kernel: 2.6.32-160.el6.x86_64
package: spice-client-0.8.0-2.el6
rating: 4
reason: Process /usr/bin/spicec was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux Workstation release 6.1 (Santiago)
Attached file: sosreport.tar.xz, 1225408 bytes
time: 1309259218
uid: 501

How to reproduce
-----
1. I run spice client from 3.0 user portal
2. I have run another client
3. first client crashed
Comment 1 David Jaša 2011-06-28 11:30:24 UTC 
Created attachment 510258 [details]
File: backtrace
Comment 3 David Jaša 2011-07-11 12:30:57 UTC 
All symptoms suggest that this is special case of bug 692833. Marking as a duplicate of it

*** This bug has been marked as a duplicate of bug 692833 ***
Note You need to log in before you can comment on or make changes to this bug.