Closed Bug 144027 Opened 22 years ago Closed 22 years ago

New windows won't open with old files in profile's chrome directory [Third Party Theme] (chrome.rdf) (Mail/News won't start from browser)

Categories

(Core Graveyard :: Skinability, defect, P1)

Product:
Core Graveyard
Component:
Skinability
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla1.3beta

People

(Reporter: azverkan, Assigned: dbaron)

References

Details

(Keywords: regression, testcase, Whiteboard: [adt3][patch])

Attachments

(1 file)

patch
1.54 KB, patch
bugs
: review+
dveditz
: superreview+
asa
: approval1.3b+
Details | Diff | Splinter Review 
Upgrading to RC2 from RC1, I found that mozilla was taking about 5 minutes to
start, as well as any operation that opens new windows (File/New/...) would
cause the browser to "create" a new window, but never give the window a name or
un-hide the window.  The hidden windows would appear under the (Window/...)
menu's window list as windows without names.  I also reproduced this on the
20020512 trunk.

The side effect of this bug is that you could not open Mail/News if you started
with the browser or open the browser if you started with Mail/News.  Also upon
closing the last window, the mozilla process would not exit (I do not use
QuickLaunch) until you End Task on the process from the Task Manager.

I tracked the problem down to having old chrome data in my profile.  After
deleting the old chrome data, the browser started functioning normally again.

This could possibly related to Bug 72267.
-> skinability and confirming

We got many incoming bugs about this and we marked them WFM 
Mozilla sometimes fail to start completly or new windows doesn't work.

But there are too many bug reports about this and we should handle "broken" skins.
Severity: blocker → critical
Component: Browser-General → Skinability
Keywords: mozilla1.0
argh, dam enter key :-)

see also bug 143647, bug 143942, .....)
Assignee: Matti → ben
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: imajes-qa → pmac
FYI: I can't start a recent trunk build 2x if I install and use Earlyblue
This bug bit me on two computers and also got a co-worker.  It
would be very helpful if this was added as a known issue to
the release notes (It took me a while to find the same 
"delete the stale chrome" fix, which was a pre-requisite 
for even finding this bug page).

- Thanks

On my computers the problem skins were not even the
currently selected skin.  Reselecting the classic
skin does not solve the problem.  Deleting the
problem skins using the "Theme Preferences" or
(If mozilla does not start) deleting the chrome
directory does solve the problem.

In my case the symptoms were new window creation
failing, and mozilla not really going away after
you close it preventing subsequent runs of mozilla
(until one used task manager to croak the "hung"
mozilla)

If it would be helpful to have a reduced 
chrome.rdf/chromeset that gives the crash please
mail me and I will produce such a set.



Yes, I forgot to mention that as well.  I was using the default Classic skin,
not the custom skins, merely having the custom skins installed was causing problems.
I also experienced this when upgrading to RC2. I "resolved" it by deleting
chrome.rdf, but that obviously should not be necessary. 
*** Bug 143726 has been marked as a duplicate of this bug. ***
*** Bug 142661 has been marked as a duplicate of this bug. ***
attachment 82937 [details] from the last dupe conatins a "corrupt" chrome.rdf
*** Bug 143758 has been marked as a duplicate of this bug. ***
Summary: New windows wont open with old files in profile's chrome directory → New windows wont open with old files in profile's chrome directory [Third Party Theme]
*** Bug 144201 has been marked as a duplicate of this bug. ***
*** Bug 144183 has been marked as a duplicate of this bug. ***
This one bit me also on Windows 2000.  I had downloaded some themes from
http://www.xulplanet.com/.

Couldn't launch new windows.  Also a zombie mozilla process would exist after I
closed Mozilla if I had attempted to launch a new window.

Deleted everything in my user profile chrome directory and things appear to be
working right now.
Pretty sure this is the same stuff I'm seeing with resent linux cvs builds. See
bug 141837, bug 143712. Marking OS -> All, correct me if I'm wrong Matti. The
debug build said something interesting when I tried this, will investigate..
OS: Windows 2000 → All
*** Bug 143931 has been marked as a duplicate of this bug. ***
Debug output when trying to open a new window.

WEBSHELL+ = 7
WARNING: CSSLoaderImpl::LoadAgentSheet: Load of URL
'chrome://chatzilla/skin/chatzillaOverlay.css' failed.  Error code: 16389, file
nsCSSLoader.cpp, line 1651

This bug got me, too - plus when I used
Preferences|Appearance|Themes...Uninstall Theme to delete the old themes,
Mozilla crashed (feedback submitted).

On restart after the crash, all was well...
*** Bug 144415 has been marked as a duplicate of this bug. ***
alge@samsen.com: You see a different problem. 
Your problem is a bad Theme and you get this only if you have this Theme activated.
I bet you use some of KAIRO's Themes (Earlyblue...) and this Theme is broken...

*** Bug 144532 has been marked as a duplicate of this bug. ***
Matti: I know perfectly well which theme I'm using, it's Modern, the one that
comes with mozilla.
*** Bug 144398 has been marked as a duplicate of this bug. ***
littlemozilla is what did this to me. given that i've been stuck with various 
things like this i'm going to probably end up fixing it.
*** Bug 144477 has been marked as a duplicate of this bug. ***
*** Bug 144762 has been marked as a duplicate of this bug. ***
*** Bug 144690 has been marked as a duplicate of this bug. ***
Bug 138978 is a duplicate of this one (indeed, THIS one is a duplicate of that bug)
Also pay attention to bug 144836 as this may be related to the reported 5
minutes to start. Bug 144602 is also a duplicate of this.
*** Bug 144687 has been marked as a duplicate of this bug. ***
After removing the themes, as mentioned in the report, everything works fine, so
it is definetly this bug I'm seeing. Another thing: When I was seeing this bug,
there was no icon for ChatZilla in the window menu. Now that I removed the old
themes, the icon showed up. I think that's related, see comment #17 (it mentions
a chatzilla file).
*** Bug 144762 has been marked as a duplicate of this bug. ***
*** Bug 144883 has been marked as a duplicate of this bug. ***
*** Bug 145214 has been marked as a duplicate of this bug. ***
I had this problem also on Win2K.  One Mozilla window would open, but I couldn't
open any other windows after that, nor close Mozilla.

Deleting mozilla and reinstalling didn't help.  I deleted several other Mozilla
files from c:\winnt and other files recommended by others.  No help.

Deleting the chrome directory from my user preferences fixed the problem.
*** Bug 145399 has been marked as a duplicate of this bug. ***
*** Bug 145482 has been marked as a duplicate of this bug. ***
*** Bug 145515 has been marked as a duplicate of this bug. ***
I also encountered the mail won't appear--except after a fresh install--problem
on Windows 2000. I was using the Pinball theme (which is a version of modern).
After uninstalling using the mozilla preferences panel, and then restarting
mozilla I was able to start mailnews and restart it--it is working perfectly now. 
*** Bug 146140 has been marked as a duplicate of this bug. ***
*** Bug 146120 has been marked as a duplicate of this bug. ***
*** Bug 146234 has been marked as a duplicate of this bug. ***
Same problem with Win98 RC2 & RC3, using LittleMozilla skin. 
IRC chat button overlayed with about 12 icons, causing status bar to triple in
width; cursor rollover hint says IRC Chat.
Note that symptoms match "fixed" bug 99453.
There is a 5/22 little mozilla skin that fixes this.

However, there is still a total disconnect between the skin owners and the
Mozilla changes. Its a real shame that both the standard skins are big, which is
why I keep trying to use the other skins.

However, until things settle down, it is best to remove allo the files in the
skins directory and use a standard skin.
I deleted the chrome.rdf file but that didn't solve the problem.  I get this
message when opening the browser when mail is already open: Mozilla cannot use
the profile "default" because it is in use.  Please choose another profile or
create a new one.
Still busted in RC3
rhorn@thesaddlehorn.com: You get this message (unrelated to this bug !) because
you should not run 2 instances with the same profile. (bad profile corruption)
Unless as on windows you get 2 instances if you run mozilla on linux again by
running mozilla.exe.
This check was added to avoid a corrupted profile.

mps@geodesic.com: what do you mean by "busted" ? Just repair your profile and it
should work.

*** Bug 146908 has been marked as a duplicate of this bug. ***
*** Bug 147033 has been marked as a duplicate of this bug. ***
*** Bug 147102 has been marked as a duplicate of this bug. ***
*** Bug 147141 has been marked as a duplicate of this bug. ***
*** Bug 147584 has been marked as a duplicate of this bug. ***
Any ideas what is breaking?
What was changed in the skins that causes this?

I don't see anything in the release note about skin updates.

That is because no one seems to keep the skin developers in the loop about when
things change that break skins.

And changing skins does not work YET properly.
*** Bug 146021 has been marked as a duplicate of this bug. ***
Summary: New windows wont open with old files in profile's chrome directory [Third Party Theme] → New windows won't open with old files in profile's chrome directory [Third Party Theme]
*** Bug 148160 has been marked as a duplicate of this bug. ***
*** Bug 147378 has been marked as a duplicate of this bug. ***
*** Bug 148526 has been marked as a duplicate of this bug. ***
*** Bug 148586 has been marked as a duplicate of this bug. ***
I'm seeing this problem in the nightly build for solaris 2.6 as well.  Removing
the chrome.rdf file didn't help me.  Do we have to delete all of the
non-standard skins and remove chrome.rdf to fix this?  The strange thing is the
very first time I ran mozilla everything worked fine.  When I exit and restart
it, that's when I can no longer open up the email window.  Weird that it ever
works if it's a broken skin.
*** Bug 138978 has been marked as a duplicate of this bug. ***
*** Bug 141222 has been marked as a duplicate of this bug. ***
*** Bug 141368 has been marked as a duplicate of this bug. ***
*** Bug 148756 has been marked as a duplicate of this bug. ***
*** Bug 148754 has been marked as a duplicate of this bug. ***
New Window won´t open if there is any profile selected (I installed Mozilla in 
a new directory after deleting the old one. When I opened the profile Window, 
none was selected)
*** Bug 149914 has been marked as a duplicate of this bug. ***
*** Bug 151784 has been marked as a duplicate of this bug. ***
It's happening again.

I'm using the Pinball theme. Everything was working OK until I upgraded Mozilla
yesterday, clean install, keeping profile.

(I really don't know if this is actually related to themes...)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020908
Erasing the old profile and starting anew helps. But there are still "ghost"
windows from time to time. I'll take a screenshot when I get home and post the
link here.
*** Bug 167973 has been marked as a duplicate of this bug. ***
*** Bug 176141 has been marked as a duplicate of this bug. ***
*** Bug 177529 has been marked as a duplicate of this bug. ***
*** Bug 179091 has been marked as a duplicate of this bug. ***
*** Bug 179091 has been marked as a duplicate of this bug. ***
*** Bug 176158 has been marked as a duplicate of this bug. ***
*** Bug 182251 has been marked as a duplicate of this bug. ***
*** Bug 182561 has been marked as a duplicate of this bug. ***
*** Bug 183248 has been marked as a duplicate of this bug. ***
*** Bug 183272 has been marked as a duplicate of this bug. ***
*** Bug 183762 has been marked as a duplicate of this bug. ***
*** Bug 183161 has been marked as a duplicate of this bug. ***
*** Bug 184065 has been marked as a duplicate of this bug. ***
*** Bug 178639 has been marked as a duplicate of this bug. ***
This bug is very serious and should be put on the list for 1.3 in my opinion.
I count 53 duplicates.

All/all on basis of duped bug 144415.
Blocks: profile-corrupt, majorbugs
Keywords: mozilla1.0 → mozilla1.3, nsbeta1
Hardware: PC → All
*** Bug 182831 has been marked as a duplicate of this bug. ***
*** Bug 182947 has been marked as a duplicate of this bug. ***
*** Bug 183605 has been marked as a duplicate of this bug. ***
*** Bug 183297 has been marked as a duplicate of this bug. ***
*** Bug 183391 has been marked as a duplicate of this bug. ***
*** Bug 183464 has been marked as a duplicate of this bug. ***
*** Bug 183849 has been marked as a duplicate of this bug. ***
For testcase, see comment 10.
Flags: blocking1.3b?
Keywords: testcase
Summary: New windows won't open with old files in profile's chrome directory [Third Party Theme] → New windows won't open with old files in profile's chrome directory [Third Party Theme] (chrome.rdf)
This problem seems to be happening always with Pinball but I cannot be sure it
didn't happen with another theme too.  Also, to get around the problem, all I do
after the theme switch and the problem opening it is to go find a graphic file
and choose to open it with Mozilla which sets everything right.

Since this is a very popular theme, I imagine a lot of newbie users (who like
changing themes) will be S.O.L. and quite unhappy with the mysteriously broken
browser.  Absolutely a blocking bug.
We need to figure out how to deal with this before 1.3 final ships.
Flags: blocking1.3b? → blocking1.3b+
*** Bug 185579 has been marked as a duplicate of this bug. ***
In general, the issues of chages that affect themes are npt handled at all. If a
user downloads a new Mozilla that breaks old themes, in my opinion, the
installer should erase/rename the old theme directory. This makes it easier for
the user because he does not have to delete old themes (which often causes crashes).
> in my opinion, the installer should erase/rename the old theme directory.

except it can't do that, the installer has (afaik) no knowledge about where the
individual users have their profile/theme directories. And should not have to
search for users with .mozilla-directories.

I think checking theme files timestamps against a hardcoded "will not work with
themes older than XXXX" thing might work, though. If only the XUL developers
would update it. (: Or just check against timestamp of build?
*** Bug 185721 has been marked as a duplicate of this bug. ***
*** Bug 185794 has been marked as a duplicate of this bug. ***
I've been bitten by this, except for me it's something in the global chrome and
not the profile (tried creating an entirely new profile but still happens) -
cannot open any new windows, including JS debugger, bookmarks, new windows, only
preferences and new tabs work.  This is Mozilla 1.2.1 under Linux.

As commented before, it's a big problem as there's no obvious way to recover
from it (like so many chrome errors!).  Are we going to end up like MS Office,
needing to ship a Repair Utility? :-)

(Out of interest, how can I recreate the global chrome from scratch?)
> (Out of interest, how can I recreate the global chrome from scratch?)

Under the install directory, in the chrome directory, delete (or rename)
chrome.rdf and the overlayinfo subdirectory when the mozilla is not running.
Then simply restart the browser and it will be recreated.

However, this bug is specifically about a problem in the profile, so let's
not broaden the discussion further. mm-k.
Nav triage team: nsbeta1+/adt3
Assignee: ben → jaggernaut
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt3]
*** Bug 187758 has been marked as a duplicate of this bug. ***
*** Bug 187160 has been marked as a duplicate of this bug. ***
*** Bug 188516 has been marked as a duplicate of this bug. ***
*** Bug 188590 has been marked as a duplicate of this bug. ***
*** Bug 189215 has been marked as a duplicate of this bug. ***
*** Bug 182365 has been marked as a duplicate of this bug. ***
*** Bug 182280 has been marked as a duplicate of this bug. ***
*** Bug 174026 has been marked as a duplicate of this bug. ***
*** Bug 176118 has been marked as a duplicate of this bug. ***
*** Bug 176118 has been marked as a duplicate of this bug. ***
*** Bug 183728 has been marked as a duplicate of this bug. ***
*** Bug 184372 has been marked as a duplicate of this bug. ***
*** Bug 189688 has been marked as a duplicate of this bug. ***
Is this a regression?
*** Bug 190379 has been marked as a duplicate of this bug. ***
.
Assignee: jaggernaut → shliang
Summary: New windows won't open with old files in profile's chrome directory [Third Party Theme] (chrome.rdf) → New windows won't open with old files in profile's chrome directory [Third Party Theme] (chrome.rdf) (Mail/News won't start from browser)
*** Bug 188039 has been marked as a duplicate of this bug. ***
Jag, this wasn't the bug we were talking about earlier today but it's another
one in the same problematic catagory. 

shliang, have you had a chance to look at this?
The duplicate bug with the lowest number is bug 142661, opened on 6 May 2002.
There is also bug 141837, opened on 2 May 2002, which was resolved invalid.
Thus, this is probably a regression. 

There was one comment that mentioned that this problem appeared after the
introduction of XUL Fastload Code. Bug 142661 comment 10. It seems suspicious.

There were a series of Chrome Fastload checkins on May 2nd, 2002. Maybe from was
bug 112064? In particular, there was a mention of what to do if certain files
don't exist and should not exist at bug 112064 comment 46. That is reminisicient
of how this problem is caused by stray, old files in the profile's chrome
directory that do exist but should not exist.
Keywords: regression
No, those comments do not implicate fastload. This problem exists independent
of fastload.
Bah. There is an effect of fastload on this, although not for anything that 
those comments did or didn't say. I think it's how the stylesheets get loaded
depending on which code path is processing the xul documents at startup.
Attached patch patch — — Splinter Review 
This fixes the bug for me (although it may not be the ideal fix).
Taking.
Assignee: shliang → dbaron
Priority: -- → P1
Whiteboard: [adt3] → [adt3][patch]
Target Milestone: --- → mozilla1.3beta
Attachment #113498 - Flags: superreview?(ben)
Attachment #113498 - Flags: review?(jrgm)
*** Bug 175427 has been marked as a duplicate of this bug. ***
Comment on attachment 113498 [details] [diff] [review]
patch

sr=dveditz
Attachment #113498 - Flags: superreview?(ben) → superreview+
Comment on attachment 113498 [details] [diff] [review]
patch

a=asa (on behalf of drivers) for checkin to 1.3beta.
Attachment #113498 - Flags: approval1.3b? → approval1.3b+
Fix checked in to trunk, 2003-02-04 18:07 PST.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
*** Bug 188310 has been marked as a duplicate of this bug. ***
v
Status: RESOLVED → VERIFIED
If y'all could spare one moment of your time, would someone with an
understanding of this bug take a look at -

http://bugzilla.mozilla.org/show_bug.cgi?id=196231

and make a quick judgement whether it is the same thing?

Thanks
It's not the same bug.
a user of 1.3rc reported bug 196713. I see from comments that this was checked
into the trunk, but did it make it into 1.3b as well?
The 1.3 branch was cut after 1.3beta.
This has 1.3b+ flag, but i really meant to ask whether the fix is in 1.3rc
this was checked in before 1.3beta, and therefore before the 1.3 branch existed,
so it will be in the branch (including the "rc" builds) and the trunk - anything
with a build ID higher than 2003020418
*** Bug 141474 has been marked as a duplicate of this bug. ***
I see this problem with v1.8 (including 1.8a4) and old profiles. The first few
windows open, but subsequent ones do not (this usually happens when the browser
has been open for a long time). Is this a known problem? Is there any open bug
that covers it?

Prog.
comment*141: No, you don't see this bug because this is fixed a very long time.
No longer blocks: majorbugs
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: