Bug 595324 - [abrt] crash in gstreamer-0.10.29-1.fc12: raise: Process /usr/bin/gst-launch-0.10 was killed by signal 6 (SIGABRT)
[abrt] crash in gstreamer-0.10.29-1.fc12: raise: Process /usr/bin/gst-launch-...
Status: CLOSED DUPLICATE of bug 593351
Product: Fedora
Classification: Fedora
Component: gstreamer (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
abrt_hash:bbeea7ed489b2e73883e9b2a08d...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-24 07:36 EDT by Kazimieras Vaina
Modified: 2010-05-26 03:36 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-26 03:36:07 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 (18.01 KB, text/plain)
2010-05-24 07:36 EDT, Kazimieras Vaina
no flags Details

  None (edit)
Description Kazimieras Vaina 2010-05-24 07:36:24 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gst-launch-0.10 filesrc location=/usr/share/mail-notification/new-mail.wav ! decodebin ! audioconvert ! gconfaudiosink
comment: No user action was in progress. Evolution does check for new email every 5 minutes.
component: gstreamer
crash_function: raise
executable: /usr/bin/gst-launch-0.10
global_uuid: bbeea7ed489b2e73883e9b2a08d83fb0c66980e5
kernel: 2.6.32.12-115.fc12.i686.PAE
package: gstreamer-0.10.29-1.fc12
rating: 4
reason: Process /usr/bin/gst-launch-0.10 was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Have evolution and mail-notifications installed.
2.Receive a new email in Evolution.
Comment 1 Kazimieras Vaina 2010-05-24 07:36:27 EDT
Created attachment 416094 [details]
File: backtrace
Comment 2 Benjamin Otte 2010-05-26 03:36:07 EDT

*** This bug has been marked as a duplicate of bug 593351 ***

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