Bug 557588 - Kaffeine error message is awful when playing file without necessary codecs installed
Summary: Kaffeine error message is awful when playing file without necessary codecs in...
Status: RESOLVED DUPLICATE of bug 549060
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: KDE4 Applications (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.2
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-22 09:14 UTC by Benjamin McCann
Modified: 2009-12-02 22:12 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Error thrown by Kaffeine (84.45 KB, image/png)
2009-11-22 09:14 UTC, Benjamin McCann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin McCann 2009-11-22 09:14:16 UTC
Created attachment 328843 [details]
Error thrown by Kaffeine

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4

Since installing openSUSE 11.2, whenever I try to open any media file I get an error from Kaffeine.  Screenshot attached.  What debug info can I provide?

Reproducible: Always

Steps to Reproduce:
1. Click on a media file (.mpg, .avi, .wmv)
Comment 1 Forgotten User --EoyBps8f 2009-12-01 12:22:34 UTC
Did you install the needed codecs for the formats you want to play? http://opensuse-community.org/Restricted_Formats/

Check that you have libxine1-codecs installed and try again with a clean user.
Comment 2 Benjamin McCann 2009-12-02 22:07:35 UTC
Thanks, I thought I had the codecs installed, but it turns out I did not.
The error message is really really bad.  It's just a big red x (see the screenshot).  I've updated this bug to reflect that the error message should be improved.
Comment 3 Benjamin McCann 2009-12-02 22:12:22 UTC
I'm marking this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 549060 ***