Closed Bug 179651 Opened 23 years ago Closed 22 years ago

Default theme Modern, not Classic since Nov 8

Categories

(SeaMonkey :: Themes, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 180984

People

(Reporter: bzbarsky, Assigned: bryner)

Details

(Keywords: regression)

PROBLEM PRESENT IN: Linux trunk build 2002-11-08-21 and thereafter PROBLEM NOT PRESENT IN: Linux trunk build 2002-11-07-21 or before STEPS TO REPRODUCE: 1) Start browser 2) Look at the default theme being used (for the browser or profile manager) EXPECTED RESULTS: Theme is classic ACTUAL RESULTS: Theme is modern Assigning this to build config, since this is most likely caused by one of the version number update things...
> bz: How exactly does a version number update thingy trigger a change in the +default theme? <bz_sleep> cls: no clue, but the last time this bug happened there was some +sort of version mismatch somewhere that caused classic to be rejected as a +valid theme.. <bz_sleep> cls: I have no clue as to the details, unfortunately <bz_sleep> cls: perhaps ccing some people who do have such clue would be a +good idea, but I'm not even sure who those are... This is the first I've heard of this. Bouncing it over to themes.
Assignee: seawood → shliang
Component: Build Config → Themes
Keywords: regression
QA Contact: granrose → pmac
This is apparently a regression from bug 172288
Assignee: shliang → bryner
Severity: normal → major
OS: Linux → All
Hardware: PC → All
ccing author of the patch which caused this too....
mkaply talked about this in another bug, cc'ing him
I definitely verified that adding back in the forms.jar stuff to installed-chrome.txt fixes it. I've no idea why. I'll try to do some more looking.
180984 has a patch *** This bug has been marked as a duplicate of 180984 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified....
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.