Bug 10904 - Crash on starting jamin on Kubuntu feisty
Summary: Crash on starting jamin on Kubuntu feisty
Status: RESOLVED FIXED
Alias: None
Product: cairo
Classification: Unclassified
Component: image backend (show other bugs)
Version: 1.4.2
Hardware: x86 (IA32) All
: medium normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-10 03:18 UTC by Amit Shah
Modified: 2008-04-11 07:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Amit Shah 2007-05-10 03:18:51 UTC
I'm on Kubuntu Feisty. This is what I get:
$ jamin
 jamin 0.95.0
 (C) 2003-2005 J. Depner, S. Harris, J. O'Quin, R. Parker and P. Shirkey
 This is free software, and you are welcome to redistribute it
 under certain conditions; see the file COPYING for details.
 /home/amit/.jamin/ does not exist, creating it...
 jackd 0.102.20
 Copyright 2001-2005 Paul Davis and others.
 jackd comes with ABSOLUTELY NO WARRANTY
 This is free software, and you are welcome to redistribute it
 under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
 loading driver ..
 apparent rate = 44100
 creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
 control device hw:0
 jamin: JACK server started
 configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
 ALSA: final selected sample format for capture: 16bit little-endian
 ALSA: use 2 periods for capture
 ALSA: final selected sample format for playback: 32bit little-endian
 ALSA: use 2 periods for playback
 Xlib: extension "XInputExtension" missing on display ":1.0".
 Failed to get list of devices
 Error: Cairo 1.4.2 does not yet support the requested image format:
         Depth: 32
         Alpha mask: 0x00000000
         Red mask: 0x000007ff
         Green mask: 0x003ff800
         Blue mask: 0xffc00000
 Please file an enhancement request (quoting the above) at:
 http://bugs.freedesktop.org/enter_bug.cgi?product=cairo
 jamin: /build/buildd/libcairo-1.4.2/src/cairo-image-surface.c:199: _cairo_format_from_pixman_format: Assertion `NOT_REACHED' failed.
 Aborted (core dumped)
Comment 1 Amit Shah 2007-05-19 04:27:37 UTC
I got a similar error for gimp as well. As a result, gimp too doesn't start.

Error: Cairo 1.4.2 does not yet support the requested image format:
        Depth: 32
        Alpha mask: 0x00000000
        Red   mask: 0x000007ff
        Green mask: 0x003ff800
        Blue  mask: 0xffc00000
Comment 2 Owen Taylor 2007-05-19 07:24:24 UTC
This error message indicates running in an unusual high-precision 
display mode with 10-bits for the Red and Blue channels and 12 bits
for the Green channel. (Compared to the normal 24-bit 8,8,8)

This display mode will be slower than a normal mode, and almost all
applications on a desktop will not take advantage of it, because the
images and graphics they display only have 8 bits per channel to 
start with.

Unless you are running specialized medical imaging or photography 
applications that you know take advantage of such a display mode, 
you  probably just want to reconfigure your display to a more normal
mode for better compatibility and performance.

If you are running such applications, you'll still have to reconfigure 
your display to run cairo-based applications for the moment, but it's
certainly on the list of things we'd like to fix. For the forseeable
future such a fix would just use 8 bits of every channel - that
would still be useful if cairo is only used in the user interface or
in a desktop component.

(Quick synopsis of the above: if you are offered a choice between 
"32 bit color" and "24 bit color" when configuring your display, pick 
"24 bit color" unless you know exactly why want 32 bit color :-)
Comment 3 Chris Wilson 2008-04-11 07:24:59 UTC
Mass closing of 8-/15-/16-/32-bit unsupported image formats as these should now all work in 1.6.0. Please test and reopen if you have any issues.


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.