425325 - Fatal error: Unsupported operand types in /home/virtual/site77/fst/var/www/html/sapphire/misc/Browscap.php on line 272

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[e29290]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9

I get the error when trying to go the that site.  It does not do it with firefox or the dreaded MS exploder

Reproducible: Always

Steps to Reproduce:
1.open SeaMonkey suite
2.type in http://www.anacortesyachtclub.org/
3.hit enter
Actual Results:  
Fatal error: Unsupported operand types in /home/virtual/site77/fst/var/www/html/sapphire/misc/Browscap.php on line 272

Comment 1

[Matthias Versen [:Matti]]

Did you try a shit+reload ?
This works for me with a current Seamonkey trunk.

Comment 2

[Misak Khachatryan]

This works for me on Fedora Linux 8. Site opens correctly. Maybe temporary site problem ?

Comment 3

[lenochod]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.15pre) Gecko/20080415 SeaMonkey/1.1.10pre
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9

This bug still appear.

Comment 4

[Misak Khachatryan]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080328 Fedora/1.1.9-2.fc9 SeaMonkey/1.1.9

Still no problem here. Site opens correctly. Can you try on clean profile, disabling all extensions. Note that some of them are Global, and apply to all profiles.

Comment 5

[lenochod]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.15pre) Gecko/20080415
SeaMonkey/1.1.10pre 

It is still appear in clean profile, extensions not use.

I used 2 computers for test - Win XP SP2

Comment 6

[Misak Khachatryan]

Confirming on Windows XP. Please change platform to Windows

Comment 7

[Matthias Versen [:Matti]]

Confirming also means that you have to find a right component for this bug and bugs in "general" are not getting fixed.

The error is from the server and we can not know what's the problem on their server. 
This works for me with a current trunk Seamonkey.
marking wfm because there is nothing we can do unless we know what's wrong and we the old 1.8 branch will also get only security fixes.