39249 - looking for non-existing user.css

Status: VERIFIED DUPLICATE of bug 39170

(Core Graveyard :: Tracking, defect, P3)

Description

[Christos Cheretakis]

New nightly build (sorry, cannot tell number, it does not start! downloaded some
minutes ago, must be from 2000-05-14) searches for a file
~/.mozilla/default/chrome/user.css on startup and  exits with error 16389.
Previous nightly build was removed with rm -rf and new one tar xczf'd in old
directory

Comment 1

[Stephen Rasku]

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

Comment 2

[John Morrison]

I expect that this is the same reason as mentioned on bug #39170 (the fact that
it stops after looking for user.css is red herring):
"We've rearranged the 
chrome into a hierarchy in which the application can't find files without hints 
from the installer. The build system fakes some hints, but the installer folks 
haven't had a chance to catch up. So builds will work fine, but pre-packaged 
installer builds will choke on their own chrome.
  Relenting from our rudeness, we've since patched the default chrome location 
code so it won't require installer hints. The pressure's off the installer guys. 
Tonight's nightly builds should be fixed." 

Marking duplicate, and we'll see what tomorrow's builds bring.

*** This bug has been marked as a duplicate of 39170 ***

Comment 3

[Christos Cheretakis]

There's also another file, user.js, mozilla is looking for although it is not
installed. I touch'ed those two files but it still won't start

Comment 4

[Tracy Walker [:tracy]]

- Per last comments, age of bug, and no reopen - Marking Verified/Duplicate.  
- duplicate bug 39170 was marked verified fixed