Closed Bug 164578 Opened 23 years ago Closed 23 years ago

Mozilla won't start

Categories

(SeaMonkey :: General, defect)

Sun
Solaris
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 164581

People

(Reporter: Rene.barbier, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1a+) Gecko/20020624 Build Identifier: http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-sparc-sun-solaris2.6.tar.gz I downloaded the latest Solaris build on Aug 26 2002 (so that would be build 2002082522 I guess). My OS is Solaris 2.6. When I try to launche the browser, I always get : Gtk-CRITICAL **: file gtkwidget.c: line 3246 (gtk_widget_set_state): assertion ` widget != NULL' failed. X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 70 (X_PolyFillRectangle) Serial number of failed request: 1317 Current serial number in output stream: 1658 I didn't get errors with the build from one week ago. Reproducible: Always Steps to Reproduce: 1.Launch Mozilla 2. 3. Actual Results: It exits with the following error message Gtk-CRITICAL **: file gtkwidget.c: line 3246 (gtk_widget_set_state): assertion ` widget != NULL' failed. X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 70 (X_PolyFillRectangle) Serial number of failed request: 1317 Current serial number in output stream: 1658 Expected Results: It should continue running! Solaris 2.6, Gtk-CRITICAL **: file gtkwidget.c: line 3246 (gtk_widget_set_state): assertion ` widget != NULL' failed. X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 70 (X_PolyFillRectangle) Serial number of failed request: 1317 Current serial number in output stream: 1658
Other bug has keywords, prio, sev. Duping. *** This bug has been marked as a duplicate of 164581 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.