230558 - chrome.rdf inside the profile will not be reconstructed after deleting it manually

Status: VERIFIED FIXED

(Firefox :: General, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

After creating a new profile I deleted the chrome.rdf there. Now I can't start
Firebird anymore untill I copy another chrome.rdf inside the chrome directory.
It happens with a recent build and for regression I tested till "Mozilla/5.0
(Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031216 Firebird/0.7+". With
this build I can also confirm it. Same happens for Firebird under Linux.

Deleting the chrome.rdf under application folder and restarting Firebird will
reconstruct it correctly. So only the chrome.rdf inside the profile is affected.
Tests with Seamonkey don't show this bug so it's Firebird only.

Comment 1

[Simon Paquet [:sipaq]]

Very strange. Everything works fine when I delete the chrome.rdf in my existing
default profile which is three days old.

But if I create a new profile - I named it Test - and delete the chrome.rdf from
this profile, firebird will not start when I choose this profile.

So confirming with a 2004-01-09 trunk build on W2K.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Could it be a side effect of bug 230569?

Comment 3

[Simon Paquet [:sipaq]]

*** Bug 230569 has been marked as a duplicate of this bug. ***

Comment 4

[Simon Paquet [:sipaq]]

Yes, I think it is a side-effect of bug 230569. I created a new profile, started
Firebird, closed it, and then deleted everything from the chrome.rdf in the
profile except for this part:

<?xml version="1.0"?>
<RDF:RDF xmlns:c="http://www.mozilla.org/rdf/chrome#"
         xmlns:NC="http://home.netscape.com/NC-rdf#"
         xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
  <RDF:Description about="urn:mozilla:package:browser-region">
    <c:selectedLocale resource="urn:mozilla:locale:US:browser-region"/>
  </RDF:Description>
</RDF:RDF>

With this information, Firebird starts up fine.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Starting FB without the "browser-region" entry is working now (bug 230569). But
a new one isn't created. So some features (e.g. "Searchbar | Add Engines") are
still broken again.

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040120
Firebird/0.8.0+

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Like comment 5 I tried a 0.8 branch build (Mozilla/5.0 (Windows; U; Windows NT
5.0; en-US; rv:1.6) Gecko/20040115 Firebird/0.7+ (MozJF) and Firebird doesn't
start when "browser-region" is missing. It seams to be fixed only on trunk.

We should fix it for 0.8 release because deleting the chrome.rdf will cause a
broken profile. 

Comment 7

[Pierre Chanial]

Not a blocker. For now, the user modifies his profile at his own risk and we
still recommend to create a new profile before installing. This bug may have
been present for a long time, otherwise when did it regress?

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Regression is somewhere between the releases Firebird/0.6.1 and Firebird/0.7.

Looking into Bonsai shows following suspicious bug 215496. Could it happen
because the fork?

Comment 9

[PikeUK]

One strange thing (well strange if like me, you don't have a clue how the code
works) is that if you delete chrome.rdf itself then start the browser it is not
properly recreated (missing browser-region). However if you delete the file
registry.dat in the Phoenix folder, chrome.rdf is correctly rebuilt including
the previously missing browser-region package.

p.s. Sorry if this is useless/obvious information.

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+1]]

To comment 9: It's not useless. Now we have the knowledge why the chrome.rdf
within a new profile is created correctly and broken in existing ones.

Comment 11

[Tim Martin]

I have this exact problem, but in the mozilla 1.6final (Windows; U; Windows NT
5.1; en-US; rv:1.6) Gecko/20040113.  And I just read a post on
netscape.public.dev.xul of someone having this problem with both a recent
mozilla nightly as well as thunderbird.

Comment 12

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Seamonkey doesn't use "browser-region" instead "communicator-region". This bug
is for the toolkit only. Checking with Thunderbird and confirmed with Mozilla
Thunderbird 0.5a (20040128) for Win 5.1

We have to expand this bug to the whole toolkit. How to do?

Comment 13

[Simon Paquet [:sipaq]]

Henrik, why are you so sure, that this is Toolit-only? Have you tested this in
seamonkey?

Comment 14

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Uhm, this was fixed a long time ago by bug 278534.