Bug 690753 - Rhythmbox looks for inexistent libcairo.so
Summary: Rhythmbox looks for inexistent libcairo.so
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 10:20 UTC by Naresh V.
Modified: 2011-04-15 05:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-15 05:34:33 UTC
Type: ---


Attachments (Terms of Use)
Start rhythmbox in gnome-terminal (2.53 KB, text/plain)
2011-03-25 10:20 UTC, Naresh V.
no flags Details
Start rhythmbox in gnome-terminal after creating symlinks (457 bytes, text/plain)
2011-03-25 10:21 UTC, Naresh V.
no flags Details

Description Naresh V. 2011-03-25 10:20:32 UTC
Created attachment 487514 [details]
Start rhythmbox in gnome-terminal

Description of problem:
rhythmbox looks for an inexistant libcairo.so and is unable to activate certain plugin(s)

Version-Release number of selected component (if applicable):
[naresh@section9 ~]$  rpm -qa rhythmbox
rhythmbox-2.90.1-5.git20110316.fc15.x86_64


How reproducible:
everytime.

Steps to Reproduce:
1. run rhythmbox from console (to spot error messages)
  
Actual results:
errors and a pop-up that says "was unable to activate 'Cover Art'" plugin
(see 'rhythmbox-startup-libcairo.txt')

Expected results:
no errors.
(see 'rhythmbox-startup-post-symlinking-libcairo.txt')

Additional info:
Symlinking as follows:
[naresh@section9 ~]$ sudo ln -s  /usr/lib/libcairo.so.2 /usr/lib/libcairo.so
[naresh@section9 ~]$ sudo ln -s  /usr/lib64/libcairo.so.2 /usr/lib64/libcairo.so

fixed the problem.

Comment 1 Naresh V. 2011-03-25 10:21:13 UTC
Created attachment 487515 [details]
Start rhythmbox in gnome-terminal after creating symlinks

Comment 2 Matthias Clasen 2011-04-15 05:34:33 UTC
This should be fixed in the current gobject-introspection build


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