Arch Linux

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#12038 - Unable to launch quodlibet

Attached to Project: Arch Linux
Opened by max-k (max-k) - Saturday, 08 November 2008, 09:51 GMT
Last edited by Allan McRae (Allan) - Sunday, 09 November 2008, 19:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since update to python 2.6 (i think), i can't launch quodlibet.
When i try to launch it (on command line), it says "Initializing audio backend (gstbe)" and then "The audio backend 'gstbe' is not installed".
If i click OK, it says :
Traceback (most recent call last):
File "/usr/bin/quodlibet", line 274, in <module>
main()
File "/usr/bin/quodlibet", line 43, in main
gtk.main()
KeyboardInterrupt


Additional info:
* package version(s)
archlinux x86_64
quodlibet 2.0.3
python 2.6-2
gstreamer 0.10.21-1
gstreamer-python 0.10.13-2

If y try `locate gstbe`, i get this :
/usr/lib/python2.6/site-packages/quodlibet/player/gstbe.py
/usr/lib/python2.6/site-packages/quodlibet/player/gstbe.pyc

* config and/or log files etc.

Steps to reproduce:
Try to launch quodlibet.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 09 November 2008, 19:09 GMT
Reason for closing:  Fixed
Comment by Allan McRae (Allan) - Saturday, 08 November 2008, 15:52 GMT
This is fine for me (i686) so it may be x86_64 specific. One possible fix is to check it the file pygst.pyc still exist under /usr/lib/python2.5/site-packages/. If it does, check no package owns it then delete it.
Comment by Victor Quinault (sylis) - Saturday, 08 November 2008, 20:25 GMT
I am running arch under i686 and I had the same problem.
the pysgt.pyc did not belong to anyone, and the problem was solved by deleting it.

Thanks Allan
Comment by max-k (max-k) - Sunday, 09 November 2008, 19:08 GMT
Than you Allan.
I've deleted this file and it's OK now.

Loading...