Closed
Bug 260103
Opened 21 years ago
Closed 20 years ago
Firefox does not read the default browser setting correctly on GNOME
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: cefrodrigues, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10
Firefox 1.0PR1 seems to be too picky about the default browser setting on GNOME.
After letting Firefox set itself as the default browser, it never complains
again unless I go to the "Preferred Applications" control panel. I don't even
need to touch anything there, just by opening it the next time Firefox starts it
complains about not being the default browser.
Reproducible: Always
Steps to Reproduce:
1. Open Firefox on GNOME (with another browser as the default)
2. Let Firefox set itself as the default browser on the dialog that pops up
3. Close Firefox
4. Go to "Start Here -> Preferences -> Preferred Applications"
5. Close the Preferred Applications control panel
6. Start Firefox again
Actual Results:
Firefox says it isn't the default browser (although it is).
Expected Results:
Nothing changed in Preferred Applications so Firefox should have known it is
still the default.
I'm running Fedora Core 2 (GNOME 2.6).
Reporter | ||
Comment 1•21 years ago
|
||
Still an issue with 1.0rc2.
Comment 2•20 years ago
|
||
I can confirm that this bug exists also on KDE. Even though
my /etc/alternatives/x-www-browser points to konqueror, thunderbird seems to
ignore it and runs Firefox instead.
How can I make Thunderbird use Konqueror instead please?
Comment 3•20 years ago
|
||
Oh, I'm using version 1.0.2 (on Ubuntu).
Comment 4•20 years ago
|
||
Yeah, Thunderbird doesn't use the KDE mimeservice, it uses the GNOME one.
That's a thunderbird bug.
Is this still happening on GNOME 2.6? GNOME 2.8 does things differently.
Comment 5•20 years ago
|
||
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 6•20 years ago
|
||
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
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•