Closed Bug 499736 Opened 16 years ago Closed 16 years ago

seamonkey crashes as soon as I try to access that page (and also some others)

Categories

(SeaMonkey :: General, defect)

SeaMonkey 1.1 Branch
x86_64
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rfhille, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; de-AT; rv:1.8.1.21) Gecko/20090410 SUSE/1.1.16-1.1.2 SeaMonkey/1.1.16 The page identified above should come up when I try to log into my internet banking. Instead Seamonkey crashes immediately. Reproducible: Always Steps to Reproduce: 1. http://www.directnet.ch 2. click <login> 3. Seamonkey crashes Actual Results: as above under "steps to reproduce". Expected Results: receive the prompt to enter my credentials I used the default theme. Java and Javascript were enabled. Accept all cookies, but only for the actual session, no blocking of pop-up windows. Mainboard: ASUS M3A78-EMH HDMI AMD Phenom(tm) 9550 Quad-Core Processor Linux 2.6.27.23-0.1-default x86_64 openSUSE 11.1 (x86_64) 4.1.3 (KDE 4.1.3) "release 4.10.4"
Can you reproduce with SeaMonkey v2.0a3 / current v2.0b1pre? (or Firefox v2.0.0.20 / v3.0.11 / v3.5(rc3) / current v3.6a1pre?)
Keywords: crash
Version: unspecified → SeaMonkey 1.1 Branch
Hardware: x86 → x86_64
Depends on: 500163
No longer depends on: 500163
This bug does not occur in Seamonkey 1.1.16 browser or email client, Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.21) Gecko/20090410 SUSE/1.1.16-1.10 SeaMonkey/1.1.16 running under Suse Linux 11.2, KDE4, milestone 2 There are also no such problems with Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 and Thunderbird Version 2.0.0.19 (20081227) under Suse 11.1 the problems with Seamonkey occurred only since one or two weeks and may be due to a faulty software update. No problems previous to this time in years of usage.
I don't understand where it actually does occur then? If it's a problem of openSUSE's update, then you need to file it in their bugzilla, I guess, we are not responsible for updates and packages provided by anyone else than Mozilla servers.
Please report this problem to the SUSE bug tracker.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.