themed dialogue box crashes mozilla



15 years ago
10 years ago


(Reporter: dave, Assigned: shliang)


Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Linux; en-US; rv:1.4) Gecko/20030707

When mozilla opens a dialogue box with the SkyPilot theme under linux, 98% of
the time the result is a crash. This can be seen if you enter an invalid url,
for isntance. The SkyPilot theme works brilliantly under the windows version
(the installer located at:
I thought it was something to do with the url bar, but i notice the same thing
happens with any dialogue box spawned. Also, mozilla refuses after one or two
attempts to open the preferences dialogue

Reproducible: Always

Steps to Reproduce:
1. use skypilot theme under linux
2. enter invalid url
3. watch as mozilla disappears before your very eyes!

Actual Results:  
Mozilla crashed out. No warning, nothing; the browser just dies.

Expected Results:  
shown me the dialogue / preferences dialogue

This bug occurs with the skypilot theme under linux (i run debian linux, sid,
synchronised nearly nightly). The crash leaves no trace of the problem, so i
unfortunately can't give any module information. The bug is not repeeateable
with the same theme and release build under windows 2000 sp4

Comment 1

15 years ago
Well, not a mozilla bug as far as I see.

Look at this page :

It seems only to work with Mozilla 1.3, 1.4alpha or beta and 1.5alpha (current

No 1.4 final listed in it.

Is this bug invalid ?

Comment 2

15 years ago
I would say that it is a mozilla issue, if it works fine under the win32 version
but not the linux version. If the theme were no good for the 1.4 final release,
then the win32 version shoudl crash as well, as themes are not making OS calls
or anything.

Comment 3

13 years ago
Theme listed as working with versions up to 1.8
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.