283485 - Acrobat Reader 5.0.10 + Firefox 1.0 : segfault when downloading.

Status: RESOLVED EXPIRED

(Toolkit :: Downloads API, defect)

Description

[João]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When Firefox is invoked from a link in a PDF file (Acrobat Reader 5.0.10 in SuSE
8.2), it crashes (segmentation fault) when attempting to download a file. 

- Acroread was set-up to use Firefox as browser.
- No Firefox instance was running at the time it was invoked from within the PDF
file.
- The link within the PDF file points to a public FTP directory. This directory
is correctly seen in Firefox, as far as I can tell.
- The segmentation fault does not seem to occur in the middle of the download.
No file actually shows up.
- Although it does not seem relevant, the donwloadable file has the same name as
the file opened in Acroread.


Reproducible: Always

Steps to Reproduce:
1. Open a PDF file in Acrobat Reader.

2. Click on a WWW link within the PDF file pointing to a web page (FTP protocol). 

3. Right-click a file in the opened public FTP directory, and select "Save Link
As...".

4. As soon as the download begins, Firefox crashes (Segmentation fault).


Actual Results:  
Output from Xterm:

user@linux:~> acroread lshort.pdf
/local/firefox-1.0/run-mozilla.sh: line 451:  4650 Segmentation fault     
"$prog" ${1+"$@"}




Expected Results:  
Start download manager and download the selected file.


- Linux distro: SuSE 8.2 Professional.
- Acrobat Reader version 5.0.10 (SuSE RPM).

NOTE: This issue seems to be related to Bug 280037.

Comment 1

[João]

I've attempted to generate a stack trace (by invoking firefox -g within
Acroread, more precisely editing the firefox shell script to add the -g switch).

GDB starts, I run the program with the URL as argument.

Acroread fires up (again) in a browser-embedded window and the file is displayed
correctly. No segmentation fault occurs.

Comment 2

[Matthias Versen [:Matti]]

Please use a talkback enabled build and send a Talkback crash report. After you
did that post the Talkback ID for that crash

Comment 3

[João]

Attachment: Talkback report of SEGFAULT from bug 283845.

Comment 4

[Matthias Versen [:Matti]]

We need only the ID. Run Talback manually to get it...

Comment 5

[Rob Jaworski]

In case it's relevant, there does seem to be a beta of Adobe Reader 7 for linux
available.  Here's the ./ article:
http://linux.slashdot.org/article.pl?sid=05/03/25/0149218&tid=163&tid=185&tid=106&tid=218

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.