Browser receives an X Window System error when loading a website
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
X.Org X server |
New
|
Undecided
|
Unassigned |
Bug Description
In order to reproduce the bug go to http://
-------
airon@airon-
error: line 3: bad flagvector
error: line 7: bad flagvector
error: line 10: bad flagvector
error: line 12: bad flagvector
error: line 14: bad flagvector
error: line 16: bad flagvector
error: line 21: bad flagvector
error: line 26: bad flagvector
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.7) (6b20-1.
OpenJDK Client VM (build 19.0-b09, mixed mode, sharing)
(midori:17570): Gtk-CRITICAL **: IA__gtk_
(midori:17570): Gtk-CRITICAL **: IA__gtk_
(midori:17570): Gtk-CRITICAL **: IA__gtk_
(midori:17570): Gtk-CRITICAL **: IA__gtk_
The program 'midori' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 47258 error_code 2 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
-------
airon@airon-
[object Object]
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.7) (6b20-1.
OpenJDK Client VM (build 19.0-b09, mixed mode, sharing)
** Message: console message: @1: Unsafe JavaScript attempt to access frame with URL http://
** Message: console message: @1: Unsafe JavaScript attempt to access frame with URL http://
The program 'epiphany' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 10383 error_code 2 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
description: | updated |
Bug reproducable also with Epiphany. So it is a Xorg bug