Bug 692208 - Rhythmbox segfaults after updating to RHEL 6.1 Beta Workstation
Summary: Rhythmbox segfaults after updating to RHEL 6.1 Beta Workstation
Keywords:
Status: CLOSED DUPLICATE of bug 684991
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhythmbox
Version: 6.1
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-30 17:14 UTC by Kurt Bechstein
Modified: 2011-03-30 17:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-30 17:56:41 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Kurt Bechstein 2011-03-30 17:14:00 UTC 
Description of problem:
I just updated to the Beta of RHEL 6 Workstation.  Since the update rhythmbox no longer even launches.  It simply segfaults and does nothing else.

Version-Release number of selected component (if applicable):
rhythmbox-0.12.8-1.el6.i686

How reproducible:
Every time.  Doesn't matter what user I try it with.

Steps to Reproduce:
1.Run Rhythmbox from command line.
2.
3.
  
Actual results:
$ rhythmbox
Segmentation fault


Expected results:


Additional info:
Comment 2 RHEL Program Management 2011-03-30 17:37:44 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.
Comment 3 Suzanne Logcher 2011-03-30 17:56:41 UTC 

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