Open
Bug 239356
Opened 21 years ago
Updated 3 years ago
mozcontainer.c does not work on not default screen
Categories
(Core :: XUL, defect)
Tracking
()
NEW
People
(Reporter: mpgritti, Unassigned)
Details
Attachments
(1 file)
928 bytes,
patch
|
Details | Diff | Splinter Review |
To reproduce:
apply the patch I'm going to attach
Xnest -ac -scrns 2 :1
Run test_container in the screen 0.
(I did gnome-terminal --display=:1 and then run it from there)
You will get an X error:
The program 'test_container' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 112 error_code 8 request_code 1 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.)
The trace looks like:
#0 gdk_x_error (display=0x9669828, error=0xfef14ae0) at gdkmain-x11.c:503
#1 0x005f68a4 in _XError () from /usr/X11R6/lib/libX11.so.6
#2 0x005f4e03 in _XReply () from /usr/X11R6/lib/libX11.so.6
#3 0x005f0064 in XSync () from /usr/X11R6/lib/libX11.so.6
#4 0x005f0125 in XSync () from /usr/X11R6/lib/libX11.so.6
#5 0x005f260b in XCreateWindow () from /usr/X11R6/lib/libX11.so.6
#6 0x00fd21a1 in gdk_window_new (parent=0x9686728, attributes=0xfef14d10,
attributes_mask=108) at gdkwindow-x11.c:692
#7 0x0804a412 in moz_container_realize ()
Reporter | ||
Comment 1•21 years ago
|
||
Comment 2•21 years ago
|
||
http://lxr.mozilla.org/seamonkey/source/widget/src/gtk2/mozcontainer.c#228 :
225 /* Mozilla uses the the gdbrgb colormap and visual throughout the
226 backend so for widgets we just use that colormap instead of the
227 default one. */
228 gtk_widget_set_colormap(GTK_WIDGET(container), gdk_rgb_get_colormap());
When I remove the gtk_widget_set_colormap() call, the crash doesn't happen.
Reporter | ||
Comment 3•21 years ago
|
||
Yeah, I think the problem is that gdk_rgb_get_colormap() use gdk_screen_get_default.
Reporter | ||
Comment 4•21 years ago
|
||
Figured out that this is just one of the problem occurences. The gfx code is
using gdk_rgb_get_colormap heavily.
Comment 5•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: blizzard → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•