Closed Bug 78029 Opened 23 years ago Closed 23 years ago

Media Player and other helper not launched (before ver 7.1)

Categories

(Core Graveyard :: Java: OJI, defect, P3)

PowerPC
Mac System 9.x

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: tarahim, Assigned: beard)

References

()

Details

2001042714 Mtrunk No plugins besides default. Goto URL. Click "Listen Online" which has a link href="http://live.wbur.org/wrni_live/westwind/wrni.asx" Result:Nothing happens except brief movement of the throbber. Expected result: A save file dialog should appear and make it possible to open the file with WMP. This is pretty serious. Real Player files seems to work. This bug occurs in www.npr.org web site, too.
Plugins --> av.
Assignee: harishd → av
Do we have Windows Media Player on Mac? Anyways, if there are no plugins installed, why should we expect plugin module get in action? Probably helper apps? cc'ing mscott.
Trying to DL .asx files causes a crash in 0507 build with the stacktrace same as bug 79163, which is covered by 79018. So, in this bug, Mozilla is canceling DL without starting DL dialog. Indeed, there is a salted .asx file in the default DL folder after crash. Modifying Summary. I have seen some other file type failing to launch downloading dialog:.lzh file for ex.
Summary: Windows Media Player does not launch → Windows Media Player files fails to launch download dialog.
The link in the original URL; http://www.wrni.org/ now launches somewhat complex windows, but it fails to launch Win MP anyways. As a simpler link, I tested the link at www.npr.org and saw the followings. In 2001050714 build, which has a fix for bug 79018, I got downloading dialog up, but it displayed: ... file of type: "#1" [#2] from #3. None of the radio buttons on the dialog was selected, and "set default" button was unresponsive. When I chose Use different action radio button and chose Win MP to open the file and hit OK, it failed to launch Win MP. I confirmed that there was an .asx file in the default dl folder. Modifying summary again.
Summary: Windows Media Player files fails to launch download dialog. → Windows Media Player file fails to launch Media Player
In recent builds, Acrobat is not launched after .pdf files are downloaded. The path of Acrobat is visible in the downloading dialog.
Definitely a must for 0.9.2. Both Acrobat and Win MP do not work regardless of the presence of plugins.
Keywords: mozilla0.9.2
What's the status of this with a more recent build? Windows probably won't work due to the absense of the JRI, but Mac should work, if not, it's a regression.
I get a java exception on mac ( arrayindex out of bounds ). qa: junruh. Media player does launch up on today's trunk on mac. This link does not work but other media player links work fine.
QA Contact: bsharma → junruh
Summary: Windows Media Player file fails to launch Media Player → java exception when trying to play audio
Assignee: av → beard
Component: Parser → OJI
component :oji, reassign : beard ?
I have no idea what you guys are talking about by JAVA exception. The origninal URL, www.wrni.org, should not involve JAVA. In 2001060114 trunk, the result is the same: www.npr.org does not launch WMP. The dialog shows the same "...file of type: "#1" [#2] from #3.", without showing the application in the window. Set Default button is unresponsive. If I select the WMP from Open with Application, it still does not launch WMP. I have changed the URL above to www.npr.org because it does not require JS. Also, since Acrobat is not launched either, modified the summary.
Summary: java exception when trying to play audio → Media Player and other helper not launched
Could be dependent on bug 79837. We'll see.
WFM in 2001062914 trunk.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Nope. WMP does not launch, though RealPlayer does. It is still "... file of type: "#1" [#2] from #3" and Choosing WMP does nothing. Reopening. 2001062914 trunk
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
This works for me using a windows release build from 07/02/01. Windows media player comes up pre-filled in the helper app dialog. I click okay and it launches media player and I can listen to NPR. We recently re-wrote the helper app dialog, I'd suggest trying a more recent mozilla build (7/2 or later).
I appreciate you test with the OS that is specified for this bug before you close it. 2001070310 trunk still shows this problem.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
In 2001071608 trunk, www.npr.org still fails to launch WinMP even if the plugin is installed. However, http://www64.tcup.com/6405/kotabeyuki.html where there are four embedded WinMP links (.asf files), successfully launches WinMediaPlayer plugin. After visiting this URL and the WinMP is launched, the link at http://www.npr.org works. Does this mean it works with .asf but not with .asx?
Setting milestone to future.
Priority: -- → P3
Target Milestone: --- → Future
The links at www.npr.org returns the header like this: HTTP/1.1 200 OK Date: Mon, 30 Jul 2001 08:40:53 GMT Server: Apache/1.3.6 (Unix) Last-Modified: Tue, 25 Jul 2000 16:20:16 GMT ETag: "2641e65-30-397dbe40" Accept-Ranges: bytes Content-Length: 48 Connection: close Content-Type: video/x-ms-asf The MIME type "video/x-ms-asf" is clearly listed if you do about:plugins, yet you need to manually specify the helper app in preferences to make it work. Is this a prblem with plug-in initialization? As might be causally related, about:plugin shows the column for suffixes is blank for Win MP plugin.
The recently released Win MP 7.1 for Mac has a new plugin, and after installing it, about:plugins displays the suffixes all right. The URL works after the installation. Marking this as FIXED.
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
Summary: Media Player and other helper not launched → Media Player and other helper not launched (before ver 7.1)
Verified on Mac 9.1
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.