Closed Bug 321770 Opened 19 years ago Closed 19 years ago

"Set as Wallpaper" overwrites the wallpaper of other users

Categories

(Firefox :: Shell Integration, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 260437

People

(Reporter: shaitand, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

I have seen this with several builds from Firefox 1.0 up to current on NT-Based systems with multiple users. Individual users will use the "set as wallpaper" or "set as desktop background" function. When they do so a file that is stored in a system-wide location is overwritten and this causes all users who have previously set a background in firefox to adopt the new wallpaper.

Reproducible: Always

Steps to Reproduce:
1. Create two (full admin?) users on a Windows XP or 2000 computer.
2. Install Firefox under each user account.
3. Set a wallpaper under user account A via Firefox.
4. Set a Wallpaper under user account B via Firefox.

Actual Results:  
User A's wallpaper is overwritten by that of user b.

Expected Results:  
That the wallpaper would be stored as an individual user preference and both could have an independant wallpaper setting.

The wallpaper function is a rather fundemental issue and important on that basis. But this bug also allows data to be overwritten. Depending on the user the data in question may be considered important or insignificant.
Are you certain that you've seen it in 1.5? It should have been fixed by bug 260437, and neither that bug nor the equivalent bug for the Suite show any signs of anyone else having it fail for them.
Blocks: 260437
Severity: critical → normal
Please reopen bug 260437 or this bug if reproducible.

*** This bug has been marked as a duplicate of 260437 ***
No longer blocks: 260437
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1)
> Are you certain that you've seen it in 1.5? It should have been fixed by bug
> 260437, and neither that bug nor the equivalent bug for the Suite show any
> signs of anyone else having it fail for them.
> 

No. I encountered this last over the phone and having read that a patch was put in for this in 1.5 walked them through a version check. They had fibbed about updating.

I just tested this and everything does work correctly in 1.5.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.