Bug 156411 - GNOME/firefox opens ogg vorbis video files with banshee
Summary: GNOME/firefox opens ogg vorbis video files with banshee
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 7
Hardware: i386 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 11:46 UTC by Holger Hetterich
Modified: 2006-03-19 16:19 UTC (History)
1 user (show)

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

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

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Hetterich 2006-03-09 11:46:31 UTC 
Download one ogg vorbis video file, for example from en.opensuse.org/FOSDEM2006 .

Firefox opens a window in which it suggests to open the file with banshee. It also states that the file is of type "Ogg-Vorbis-Audio", which is wrong.

If I choose something else by clicking on the listbutton, nothing is in the list.

Expected behavious: 
Firefox should open totem for viewing the file.
Comment 1 Holger Hetterich 2006-03-09 11:52:11 UTC 
I am not sure if this is caused by Firefox alone, so I assigned it to gnome-maintainers, but took Wolfgang into CC.
Comment 2 Wolfgang Rosenauer 2006-03-09 12:03:18 UTC 
If the webserver doesn't provide a correct-mimetype Firefox (resp. gnome-vfs) can't differentiate between ogg audio and ogg video because it only uses the name "ogg" to find applications. A Firefox logfile can be captured by

export NSPR_LOG_MODULES=HelperAppService:5
export NSPR_LOG_FILE=/tmp/firefox.log
# start firefox and download the file (it's enough to the get through until the dialog box appears)

That will show where the banshee entry comes from.
Comment 3 JP Rosevear 2006-03-09 13:12:22 UTC 
This is related to bug 156210, but I'm not sure that will solve it either exactly since FF asks the user what to open with before the file is downloaded so no sniffing can occur.
Comment 4 Stanislav Brabec 2006-03-09 14:24:41 UTC 
If it is a http, it is a problem of http server, which provides MIME type on its own. If it is an FTP, I am not sure, but I guess that MIME type is guessed from suffix. For local files it can be a duplicate.
Comment 5 JP Rosevear 2006-03-09 20:47:05 UTC 
The local mime type is fixed.
Comment 6 JP Rosevear 2006-03-19 16:19:12 UTC 
Since the local type is fixed, this is probably as good as we can get if the server is providing the wrong type.