Open Bug 172290 Opened 22 years ago Updated 2 years ago

fail gracefully when associated helper app is not executable

Categories

(Firefox :: File Handling, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: jmd, Unassigned)

References

Details

(Keywords: helpwanted)

In the top right: WATCH/LISTEN AUDIO CHOICE Statue of former President Kim Il Sung North Korea changes ways in fear of US Is a link to: http://news.bbc.co.uk/media/audio/38293000/rm/_38293903_nkorea02_grammaticas.ram I don't have Real Player installed. Clicking this link pops up a dialog saying an unknown error has occured, and to try saving the file to disk and then running it. Linux 2002100208
plugins?
reporter: you just need to install realplayer to handle the .ram file format.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
The point is, i'm getting an "unknown error", and mozilla is leaving a file around in /tmp and never cleaning it up. Both of those things are bugs, no matter what plugins I may have installed.
i see.. ok, though i cannot reproduce the problem, let's see what the file handling folks think. -> file handling
Status: RESOLVED → REOPENED
Component: Networking: HTTP → File Handling
Resolution: INVALID → ---
-> file handling
Assignee: darin → law
Status: REOPENED → NEW
QA Contact: httpqa → sairuh
I assume that you never get a filepicker, just the dialog? What is the exact text of the dialog? What are your exact http settings (pipelining, etc). Do you use a proxy? Finally, do you build? If so, I can post some changes you could apply to your tree to generate debugging output. Needless to say, I can't reproduce this myself, with the 2002-09-30-21 nightly (and I have no way of getting anything newer for a bit).
Think I figured out where this is coming from. This profile is from an older OS that had realplayer installed. There's an association in helper apps pointing to a non-existant file to run for this. Mozilla should fail more gracefully under these circumstances. An "Unknown error" is always a bug. Not sure what component to send this to.
Summary: Unknown error occurs clicking link on BBC News → fail gracefully when associated helper app is not executable
This is the right component. I'll take this, since this is linux-specific code. I've been meaning to clean up the error handling anyway....
Assignee: law → bzbarsky
Priority: -- → P2
Target Milestone: --- → mozilla1.3beta
QA Contact: sairuh → petersen
bz: is this still a problem? iirc, yesterday's helper apps checkin includes a check if the helper app is executable. (hm, maybe not if the executable flag changes during the download, though; and maybe not if the helper app dialog is set to not show)
Exactly. This bug is about the case when the helper app dialog never shows.
bz: Is fixing this as simple as adding an IsExecutable check here: http://lxr.mozilla.org/seamonkey/source/uriloader/exthandler/unix/nsOSHelperAppService.cpp#188 the calling code seems to check for error codes from this function and puts up an alert if needed
Um.. We already return an error code and it's already reported (see comment 0). So: 1) What error code is returned? (I suspect it's NS_ERROR_FILE_EXECUTION_FAILED, looking at nsProcessCommon::Run). 2) We need to handle that error code.
Not quite so simple, actually.... it looks like we trigger the: if (!application) return NS_ERROR_FAILURE; clause. We need to rework error handling for launching stuff in general.... :(
No, that check is definitely needed; we need it elsewhere (eg see GetMIMEInfoForExtensionFromOS). We should probably have some logic to either not call LaunchWithApplication with no app or to have it deal.
I have no idea when I'll get to this....
Keywords: helpwanted
Priority: P2 → --
Target Milestone: mozilla1.3beta → Future
Priority: -- → P3
Target Milestone: Future → mozilla1.7alpha
testcase seems to be: touch /tmp/myapp set /tmp/myapp as helper app for some content load such content
QA Contact: chrispetersen → file-handling
Assignee: bzbarsky → nobody
Priority: P3 → --
Target Milestone: mozilla1.7alpha → ---
Product: Core → Firefox
Version: Trunk → unspecified
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.