fullscreen crash mozilla on sunrays

RESOLVED WORKSFORME

Status

()

Core
XUL
--
critical
RESOLVED WORKSFORME
16 years ago
14 years ago

People

(Reporter: Dennis Haney, Assigned: Brian Ryner (not reading))

Tracking

({crash})

Trunk
Sun
Solaris
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
I get this error when I try to get fullscreen:
Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 6414 error_code 3 request_code 12 minor_code 0
Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 6415 error_code 3 request_code 12 minor_code 0

This is version 1.1 linux on RH7.3 displayed on a sunray.
Thus Platform/OS set to Sun/Solaris.

uname -a on the solaris server:
SunOS guldfaxe.diku.dk 5.8 Generic_108528-05 sun4u sparc SUNW,Ultra-4
isainfo -b: 64
Xsun version: 6.4.1 (I think)

Comment 1

16 years ago
-> bryner
Assignee: jaggernaut → bryner
Severity: normal → critical
Keywords: crash

Comment 2

14 years ago
Dennis, do you still get this crash?
If so, please report a Talkback ID (you said you used a linux build somehow...).

Comment 3

14 years ago
Dennis, do you still get this crash?
If so, please report a Talkback ID (you said you used a linux build somehow...).

Comment 4

14 years ago
I have tried to duplicate this problem using Mozilla 1.7.1 and Firefox 0.9.1 on
a Redhat 9 machine and display it back on Sunray's and the full screen option
works fine. I have tried this on both Sunray Server Software 1.3 and 2.0, the
servers had recent Solaris patch clusters and the Sunray software is also at the
latest patch revision.
When looking at the output from the 'uname -a' it's reporting a very old version
of the Solaris kernel which normally means the Sunray server has either never
been patched or the patches are so out of date then a lot of problems would
exist. Try the latest Recommended patch cluster from the operating system and a
recent Sunray software patch and see if that fixes the problem. I'd say it's
more likely a problem with the Xsun process rather then Mozilla itself.
I'd recommend changing the status of this bug to 'Resolved -> WORKSFORME' as
it's unlikely to be a Mozilla problem.

Comment 5

14 years ago
ok, resolving then
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.