Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#22186 - [xbmc] 10.0-1 does not start due to missing dependency on package libass

Attached to Project: Community Packages
Opened by Lee (adr3nal1n) - Wednesday, 22 December 2010, 13:32 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 23 December 2010, 09:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Xbmc will not start due to a missing dependency on package libass


Additional info:
* package version(s) = 10.0-1

Upgrade from xbmc 9.11-18 on X86_64 and XBMC would not start until I installed libass using 'pacman -S libass'

'ldd /usr/lib/xbmc/xbmc.bin |grep libass' gives the following:
libass.so.4 => /usr/lib/libass.so.4 (0x00007faa03f38000)

Note also that xbmc.bin was located at /opt/xbmc/xbmc.bin before the upgrade. (from xbmc 9.11-18 to xbmc 10.0-1)

This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 23 December 2010, 09:51 GMT
Reason for closing:  Fixed
Comment by Lee (adr3nal1n) - Wednesday, 22 December 2010, 13:39 GMT
Apologies, I got the title wrong (this is my first bug report), please change title to "[xbmc] 10.0-1 does not start due to missing dependency on package libass"

Thanks very much.
Comment by Dave Reisner (falconindy) - Wednesday, 22 December 2010, 14:20 GMT
This looks like a packaging error -- xbmc should not depend on libass. The i686 package is built correctly and does not have this dependency.

Also, please note: ldd is not the proper way to determine linkage, as it acts recursively. Please use readelf with the -d flag to determine direct so depends.
Comment by kevin kim (kvn) - Thursday, 23 December 2010, 04:11 GMT
I also had this issue - appears to effect machines that have installed a previous build and have 'contaminated their installs'

I had to install libass to get it working.

https://bbs.archlinux.org/viewtopic.php?pid=868697#p868697

A forum moderator has fully explained the cause of the issue

Loading...