Closed Bug 274039 Opened 20 years ago Closed 19 years ago

upon startup, nothing appears in either the mail or browser windows

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: Bil.Kleb, Unassigned)

Details

(Keywords: hang)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041122
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041122

I am running Fedora Core 3.  To get some updated junk mail filtering, I
installed 1.8a5.  If I start it from a launcher in the panel (running Gnome), I
get blank windows.  If I start it from the command line, I usually get normal
behavior.  Lately, however, I have to start up the old 1.7.3 version, shut it
down, and then start up 1.8a5 to get normal behavior.

Reproducible: Sometimes
Steps to Reproduce:
Don't have it down to a science yet.  See "Details" above.

Actual Results:  
Browser and mail windows come up blank.

Expected Results:  
Browser and mail windows come up normally.
what preferences do you have set (the "Navigator" panel in preferences)
Do you see the same behavior with a clean profile?

If it works fine from the commandline, but not from gnome panel, then the
startup command from the gnome panel is probably inappropriate.
Severity: critical → major
I haven't had any problems along these lines since
upgrading to xorg 6.8.1-12.FC3.21
1.8a5 came up with blank screens again this morning (by using the panel
launcher).  I can move them around but they do not refresh and cannot be killed
by the window manageer.

I killed them from the command line, tried again, killed those, started 1.7.3,
quit, and sucessfully started 1.8a5 from the command line to enter this.
Version: unspecified → Trunk
BIl: is this still a problem, perhaps with 1.8b1 or a recent nightly build?
Severity: major → critical
Keywords: hang
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
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.