Bug 688515 - [abrt] gnome-media-2.29.91-6.el6: g_assertion_message: Process /usr/bin/gnome-volume-control was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-media-2.29.91-6.el6: g_assertion_message: Process /usr/bin/gnome...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-media
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 09:42 UTC by prashant ingale
Modified: 2018-11-26 19:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 20:06:43 UTC
Target Upstream Version:


Attachments (Terms of Use)
backtrace (7.84 KB, application/octet-stream)
2011-03-17 09:42 UTC, prashant ingale
no flags Details

Description prashant ingale 2011-03-17 09:42:25 UTC
Created attachment 485964 [details]
backtrace

Description of problem:

gnome-volume-control was killed by signal 6.
reason: Process /usr/bin/gnome-volume-control was killed by signal 6 (SIGABRT).

Version-Release number of selected component (if applicable):

release: Red Hat Enterprise Linux Server release 6.0 (Santiago).      architecture: x86_64.
executable: /usr/bin/gnome-volume-control.
package: gnome-media-2.29.91-6.el6.

How reproducible:
randomly 
  
Actual results:
gnome-media crashed.

Expected results:

gnome-media should not crash.

Comment 3 RHEL Program Management 2011-07-06 00:29:04 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.


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