When opening nautilus from the download manager, a desktop is created

RESOLVED EXPIRED

Status

()

Toolkit
Downloads API
RESOLVED EXPIRED
13 years ago
10 years ago

People

(Reporter: Philip Nelson, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2)

As I understand it, firefox looks to gconf settings for the default file manager
which is nautilus 99% of the time. The problem is that nautilus is a desktop
manager as well as a file browser. For those of us running a different
environment than gnome, you need to kill nautilus manually if you know to do it
and your system is still running. Others have reported that their system becomes
unstable or that the gdm get's killed. 

Reproducible: Always

Steps to Reproduce:
1. Start an alternate window manager and desktop, say fluxbox and rox-filer
2. Open firefox
3. Open the download manager


Actual Results:  
in most cases your desktop and window manager will have been replaced

Expected Results:  
If nautilus was the file manager it should have opened with the --no-desktop
option. It should have opened in the "browser" mode used for browsing the file
system.

Talking this over with others in our users list (agnula users list) I think the
best option would be to do this:

- if you must default to nautilus, use the --no-desktop option. There are
workarounds that involve changing nautilus defaults to not manage the desktop
but this changes the default behavior of gnome.

- expose the file manager command vi about:config. Perhaps the first time it's
used, pop up a dialog informing the user of the default and giving them an
option to change it.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
(Assignee)

Updated

10 years ago
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.