Closed
Bug 60063
Opened 24 years ago
Closed 23 years ago
Plugin Donwload file always seem to be saved in /tmp when PATH specified has no write permission.
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0.1
People
(Reporter: rpallath, Assigned: yiming.chung)
References
()
Details
(Whiteboard: suntrak-n6)
Attachments
(2 files)
Invoke Browser
Visit www.comdex.com
It will invoke a "Plugin Downloader" box.
Click on "Ok" button
It will invoke a new windows pointing to macromedia site.
Cancel the "Plugin Downloader" dialog box.
Click on the "Download" icon on the macromedia site (for dowloading Shockwave
Plugin).
It will invoke a popup prompting for "Save or Open" of Plugin
Choose Save
Click "OK"
This will invoke a File choose dialog box.
Save it.
Check the dir. where it should have saved the file. You wont find it
Go to /tmp and you will find the file there.
Looks like it saves in '/tmp' dir. regardless of the path specified.
Tried it on Solaris 2.7 (sparc).
The following was used for this build:
1106 Commercial Build
[tag: -r Netscape_20000922_BRANCH -D "10/26/2000 10:00:00"
mozilla source patch: 57725.diffs
PSM: 1.3 & NSS 3.1 (NSS_3_1_RTM tag)
PSM jedimind trick: libpsmshim.so
Cool/AIM: sparc drop 08282000 ,intel drop 10092000
ns source patch for run-mozilla.sh ]
1106 Commercial Blackwood Build
[tag: -r JAVADEV_PR3_20001002 ]
1024 Commercial Build gtk libs
Java Plugin 1.3.0_01 FCS bits
If you try to point ot a dir. which does not have permissions to write, then it
saves into /tmp.
Comment 3•24 years ago
|
||
This bug occurs only when the user does not have write permissions on the
directory he/she is trying to save (like /opt). This works ok when the write
permissions exist(like in /home/<user>). I'm updating bug summary with this info..
-raghu
Summary: Plugin Donwload file always seem to be saved in /tmp regardless of PATH specified. → Plugin Donwload file always seem to be saved in /tmp when PATH specified has no write permission.
Comment 4•24 years ago
|
||
Reassigning to drapeau and moving to m1.0.
Assignee: av → drapeau
Target Milestone: --- → mozilla1.0
raju: what should the expected behavior be, please? Should the attempted save
simply fail, for example?
yes, it should fail,as user is not prompted with any message indicating
the destination dir. did not have permissions and
also has no indication saying that the
file got saved in /tmp.
but the file saved in /tmp is not with its actual name, but with a temporary
name.
So say you were saving file flash_solaris.tar.gz in adir /opt/test which has
no write permissions.
It would actually save the file as <some temporary name>.gz in your /tmp dir.
This should not have happened.
If it was temporarily done , then it should have been removed, if permissions
were denied on the destination dir.
Comment 7•24 years ago
|
||
Reproduced with 04/06/2001 nigthly under RH Linux 6.2 .
Comment 8•24 years ago
|
||
Updating the bug OS to Linux based on comments from Alexei.
OS: Solaris → Linux
Assignee | ||
Comment 9•24 years ago
|
||
add ychung to cc list
Comment 10•24 years ago
|
||
Per Yiming's request, assign this bugg to herself!
Assignee: drapeau → yiming.chung
Assignee | ||
Comment 12•23 years ago
|
||
Assignee | ||
Comment 13•23 years ago
|
||
Andrew/Peter, could you please review the patch? Thanks.
Comment 14•23 years ago
|
||
I don't see any immediate problems with the patch, but how this bug ended up
with the Plugins component? XP Toolkit maybe?
Assignee | ||
Comment 15•23 years ago
|
||
from the problem description, it appears to be related to plugins, but the fix
is on XPToolkid. Should I also ask Peter Trudelle to review the patch for me?
Comment 16•23 years ago
|
||
I think he is the right person. Adding.
Assignee | ||
Comment 17•23 years ago
|
||
It looks like it is closer to XPApps domain after second thought. cc to Don and
Steve.
Don/Steve, I add an error dialog when users have no write permission to save a
plugin download file. Could you please review the code for me? Thanks.
Assignee | ||
Comment 18•23 years ago
|
||
Comment 19•23 years ago
|
||
Don and Steve are long gone, and I'm not the right person to review this, but
bryner probably is, cc'ing him.
Comment 20•23 years ago
|
||
see also bug 27609
Comment 21•23 years ago
|
||
*** Bug 93653 has been marked as a duplicate of this bug. ***
Comment 22•23 years ago
|
||
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1
(you can query for this string to delete spam or retrieve the list of bugs I've
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 23•23 years ago
|
||
bryner: Can you review this (old) patch ?
Comment 24•23 years ago
|
||
Code to fix this issue was checked in as part of the fix for bug 114399
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•