[Bug 128493] Re: sudo nautilus -> open file with ... firefox wipes/overwrites profile content - data loss

[Alexander Sack]

On Mon, Jul 30, 2007 at 01:15:03PM -0000, kornelix wrote:
> You asked for a simple step-by-step instruction how to reproduce.
> What part of the original post needs more explanation?
> 
> Here is a more elaborate version:

Thanks ...

 - Alexander


** Description changed:

- Binary package hint: firefox
  
- 1.  $ sudo nautilus
- 2.  find a .html file with browser and click on it
- 3.  firefox starts up and displays the .html file
+ TESTCASE:
+ 1. if you are using a fresh install, start firefox and create a bookmark
+ 2. from a terminal window: $ sudo nautilus (i.e. start nautilus as root user)
+ 3. using the nautilus browser, find a .html file and open it with the mouse
+ (e.g. file: /usr/share/gtk-doc/html/evince/index.html)
+ (this starts firefox as root user)
+ 4. firefox should start and display the html file
+ (if not, right click the file and in the "open with" dialog, select firefox)
+ 5. exit firefox
+ 6. open firefox again
+ 7. check the bookmark created in step 1 - it is now gone
  
- User files at ~./mozilla/firefox/* are now in an initial condition, as
- found after first startup of firefox after a new Ubuntu installation.
- Owner of files is user, not root. Prior user files are gone without a
- trace.
+ In fact, all user files in the firefox profile have now been replaced with initial versions.
+ The owner of these files is the user, not root.
  
- The following command works without risk: 
-   $ sudo firefox
- Firefox gives a warning and executes with an automatic -H option. 
- There is no loss of user files.
- 
- I believe the behavior with nautilus should work the same way, or at
- least Firefox should not initialize the user files without warning.
+ If firefox is started as root user using $ sudo firefox, the problem
+ does not occur.

-- 
sudo nautilus -> open file with ... firefox wipes/overwrites profile content - data loss
https://bugs.launchpad.net/bugs/128493
You received this bug notification because you are a member of Mozilla
Bugs, which is a bug assignee.