The following message was generated while trying to use evolution via a remote X11 on Fedora Core 6 to a local MacOSX client (Macbook Pro/Intel with MacOSX 10.4.8. Not sure whether to call this a Macintosh OSX / X11 bug or a bug in Fedora Core 6. Error: Cairo 1.2.6 does not yet support the requested image format: Depth: 16 Alpha mask: 0x00000000 Red mask: 0x00007c00 Green mask: 0x000003e0 Blue mask: 0x0000001f Please file an enhancement request (quoting the above) at: http://bugs.freedesktop.org/enter_bug.cgi?product=cairo evolution: cairo-image-surface.c:201: _cairo_format_from_pixman_format: Assertion `NOT_REACHED' failed. Error: Cairo 1.2.6 does not yet support the requested image format: Depth: 16 Alpha mask: 0x00000000 Red mask: 0x00007c00 Green mask: 0x000003e0 Blue mask: 0x0000001f Please file an enhancement request (quoting the above) at: http://bugs.freedesktop.org/enter_bug.cgi?product=cairo
The following error is reported when trying to lauch firefox, galeon or mozilla: [jan@olympus:~$] Error: Cairo does not yet support the requested image format: Depth: 16 Alpha mask: 0x00000000 Red mask: 0x00007c00 Green mask: 0x000003e0 Blue mask: 0x0000001f Please file an enhacement request (quoting the above) at: http://bugs.freedesktop.org/enter_bug.cgi?product=cairo iceape-bin: /build/buildd/libcairo-1.2.4/src/cairo-image-surface.c:155: _cairo_format_from_pixman_format: Assertion `NOT_REACHED' failed.
Similar problem using Citrix (on windows XP machine with 16-bit color setting) to connect to a solaris 8 x-server. The error message is: Error: Cairo 1.2.6 does not yet support the requested image format: Depth: 16 Alpha mask: 0x00000000 Red mask: 0x00007c00 Green mask: 0x000003e0 Blue mask: 0x0000001f Please file an enhancement request (quoting the above) at: http://bugs.freedesktop.org/enter_bug.cgi?product=cairo xdpyinfo on the display gives: name of display: unix:11.0 version number: 11.0 vendor string: Citrix Systems Inc vendor release number: 51999 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding: 32, MSBFirst, 32 image byte order: MSBFirst number of supported pixmap formats: 2 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 keycode range: minimum 8, maximum 207 focus: window 0x3c00009, revert to PointerRoot number of extensions: 12 BIG-REQUESTS DOUBLE-BUFFER GLX MIT-SHM MIT-SUNDRY-NONSTANDARD RECORD SECURITY SGI-GLX SHAPE SYNC XC-MISC XTEST default screen number: 0 number of screens: 1 screen #0: dimensions: 1280x967 pixels (325x246 millimeters) resolution: 100x100 dots per inch depths (1): 15 root window id: 0x26 depth of root window: 15 planes number of colormaps: minimum 1, maximum 1 default colormap: 0x22 default number of colormap cells: 32 preallocated pixels: black 0, white 32767 options: backing-store YES, save-unders YES largest cursor: 32x32 current input event mask: 0x7a003f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMask EnterWindowMask LeaveWindowMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask number of visuals: 1 default visual id: 0x23 visual: visual id: 0x23 class: TrueColor depth: 15 planes available colormap entries: 32 per subfield red, green, blue masks: 0x7c00, 0x3e0, 0x1f significant bits in color specification: 8 bits Changing the Windows display setting to 32-bit color allowed citrix to select a visual that cairo supports, but will be a problem for users who can't change their color setting.
*** Bug 10461 has been marked as a duplicate of this bug. ***
*** Bug 9993 has been marked as a duplicate of this bug. ***
Retitling to make the actual issue more identifyable
A fix for this bug has now been pushed out to cairo's git repository: http://gitweb.freedesktop.org/?p=cairo;a=commitdiff;h=333b96f0e0a7d Look for the fix in an upcoming 1.5.2 development snapshot and an upcoming 1.6.0 release. Have fun with cairo! -Carl
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.