Bug 574500
Summary: | BadMatch from XCreateWindow (different color depths) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | chuck elliot <chuck.elliot> | ||||
Component: | desktop-effects | Assignee: | Owen Taylor <otaylor> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 12 | CC: | adel.gadllah, didierg-divers, eddie, gabriel, jlaska, loverboy76, maycon.franca, moose, odeys87, otaylor, rianby64, sghosh, stuart, vmattaur, xseanxbutlerx, yuseffathi | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:24fc7c778c10fc51d2e444793d550cbaf331a9a3 | ||||||
Fixed In Version: | desktop-effects-0.8.7-2.fc13 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-07-07 17:48:30 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
chuck elliot
2010-03-17 16:58:42 UTC
Created attachment 400829 [details]
File: backtrace
How to reproduce ----- 1.Power on Fedora12 2.Login to default non root account 3.Tried to open System-> Desktop Effects and it crashed without opening Comment ----- Could not open desktop effects, for some reason it is not opening at all.I am running Fedora12 on a virtual machine VMWare. odeys87 *** Bug 583870 has been marked as a duplicate of this bug. *** *** Bug 588208 has been marked as a duplicate of this bug. *** *** Bug 588607 has been marked as a duplicate of this bug. *** *** Bug 593582 has been marked as a duplicate of this bug. *** Error event: xerror = {type = 0, display = 0x9169600, resourceid = 231, serial = 129, error_code = 8 '\b', request_code = 1 '\001', minor_code = 0 '\000'} request code 1 is CreateWindow. *** Bug 590943 has been marked as a duplicate of this bug. *** *** Bug 596596 has been marked as a duplicate of this bug. *** *** Bug 583311 has been marked as a duplicate of this bug. *** *** Bug 589460 has been marked as a duplicate of this bug. *** *** Bug 592715 has been marked as a duplicate of this bug. *** *** Bug 597530 has been marked as a duplicate of this bug. *** There are at least several references to this being triggered by a 16bpp color dpth - in particular this was tracked down by Stuart Gathman in bug 583311; and in bug 597530 Andres Rios says "Cambiar la resolucion de pantalla de millones de colores a miles de colores" as a reproduction step. The explanation, I think, of this bug can be seen in the X server code: if (((vmask & (CWBorderPixmap | CWBorderPixel)) == 0) && (class != InputOnly) && (depth != pParent->drawable.depth)) { *error = BadMatch; return NullWindow; } So if you don't provide a BorderPixmap or a BorderPixel (meaning that the border color is inherited from the parent), then you have to match the color depth of the parent. We can see a difference between the desktop-effects code: cwa.colormap = XCreateColormap(xdisplay, RootWindow (xdisplay, xscreen), visual->visual, AllocNone); window = XCreateWindow(xdisplay, RootWindow (xdisplay, xscreen), 0, 0, 1, 1, 0, visual->depth, InputOutput, visual->visual, CWColormap, &cwa); And the glxinfo code: attr.background_pixel = 0; attr.border_pixel = 0; attr.colormap = XCreateColormap(dpy, root, visinfo->visual, AllocNone); attr.event_mask = StructureNotifyMask | ExposureMask; mask = CWBackPixel | CWBorderPixel | CWColormap | CWEventMask; win = XCreateWindow(dpy, root, 0, 0, width, height, 0, visinfo->depth, InputOutput, visinfo->visual, mask, &attr); Looking at the X server code, I can't see the reason for setting the BackPixel and the EventMask, though I think it's probably good to set the BackPixel just to be safe. *** Bug 541985 has been marked as a duplicate of this bug. *** *** Bug 550983 has been marked as a duplicate of this bug. *** desktop-effects-0.8.7-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/desktop-effects-0.8.7-2.fc13 desktop-effects-0.8.7-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update desktop-effects'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/desktop-effects-0.8.7-2.fc13 Karel: Are you able to confirm this problem is fixed using the update posted in comment#18? Please feel free to add feedback either here in bugzilla, or at http://admin.fedoraproject.org/updates/desktop-effects-0.8.7-2.fc13 Thanks! Seems to be fixed in desktop-effects-0.8.7-2.fc13.x86_64 However, there is no third option 'GNOME3 preview' in the dialogue as described in rpm -qi Description : desktop-effects provides a preference dialog to allow switching the GNOME desktop between three different window managers: Metacity (the standard GNOME 2 window manager), Compiz (offering 3D acceleration and special effects), and GNOME Shell, which offers a preview of the GNOME 3 user experience. thanks & best wishes, CE (In reply to comment #20) > Seems to be fixed in desktop-effects-0.8.7-2.fc13.x86_64 > > However, there is no third option 'GNOME3 preview' in the dialogue > as described in rpm -qi > > Description : > desktop-effects provides a preference dialog to allow switching the GNOME > desktop between three different window managers: Metacity (the standard > GNOME 2 window manager), Compiz (offering 3D acceleration and special > effects), and GNOME Shell, which offers a preview of the GNOME 3 user > experience. You need to install the gnome-shell package in order to get this third option. desktop-effects-0.8.7-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |