[linux] [orbit themes] Mozilla hangs up when switching to / using one of the orbit themes

RESOLVED EXPIRED

Status

Core Graveyard
Skinability
--
critical
RESOLVED EXPIRED
15 years ago
9 years ago

People

(Reporter: Martin Heitzer, Assigned: andreww)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i586; de-AT; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla 1.4 beta (en-us)

Using one of the Orbit themes, Mozilla 1.4 beta does not display the button bars
correctly in Browser / Mail and hangs up after a short period of time. This only
happens with Linux.

OS: SuSE 8.2, KDE 3.1.2


Reproducible: Always

Steps to Reproduce:
1. Install theme Orbit 3+1 or Orbit Retro from mozdev.org (I downloaded the*.xpi
files and installed them as root later)
2. Start Mozilla 1.4 beta.

Actual Results:  
Browser hangs up / does not show up correctly.

Expected Results:  
Browser should have switched to Orbit 3+1 / Orbit Retro theme.

Comment 1

15 years ago
This is not a mozilla bug, because it is not an official mozilla theme. Is there
any compatible Orbit theme for your mozilla release ?
(Reporter)

Comment 2

15 years ago
Sorry, I really did not know that, but I really don't think there is any
"compatible" Orbit theme.
Official mozilla themes are only Classic and Modern, right?

Comment 3

15 years ago
Yes, the only official themes are classic and modern.

I think there will be soon a 1.4 compatible orbit theme :-}

Comment 4

14 years ago
Reporter, is this still happening?  The problem you are reporting may well have
been fixed already.  Please download a a recent nightly build of mozilla and see
if it can be reproduced again.

Also, if it is still reproducable, you may want to file a bug at mozdev.org's
bugzilla.  This could be a bug steaming from the Orbit theme.
(Reporter)

Comment 5

14 years ago
I'll do as told by Alistair Y. Lewars the following weekend, as I hope 1.5 final
is recent enough ;-)
(Reporter)

Comment 6

14 years ago
This seems to be a compatibility problem affecting 1.4 alpha and up. At least
actually there is no version available for Mozilla 1.5.

On mozdev.org, various other reporters confirm this bug, see

--> http://themes.mozdev.org/themes/retro.html
--> http://themes.mozdev.org/themes/orbit.html

 

Comment 7

14 years ago
Martin, it seem that there is a 1.5/1.6b compatible Orbit 3+1 theme that is
available.  You may want to try it out and see if it's working now for you.  It
is working for me.  Using:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031125

Thanks.
(Reporter)

Comment 8

14 years ago
I downloaded and installed this theme yesterday, works fine.
I would say this one is fixed.

Browser: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.5) Gecko/20031007

Thanks to Alistair, too. ;-)
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/
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
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.