Bug 712055 - Crash at loading into a macbook pro 5.1
Summary: Crash at loading into a macbook pro 5.1
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: cheese
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-09 11:45 UTC by Miguel
Modified: 2011-09-29 13:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-29 13:59:51 UTC
Type: ---


Attachments (Terms of Use)

Description Miguel 2011-06-09 11:45:09 UTC
Description of problem:

cheese don't start

Version-Release number of selected component (if applicable):


How reproducible:
open cheese

Steps to Reproduce:
1. open cheese
2.
3.
  
Actual results:
cheese don't starts

Expected results:
cheese starts

Additional info:

console output 
(cheese:2803): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context

(cheese:2803): Clutter-WARNING **: Unable to create a new stage: the glx backend does not support multiple stages.

(cheese:2803): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed

(cheese:2803): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(cheese:2803): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Violación de segmento (`core' generado)

Comment 1 Hans de Goede 2011-09-29 13:36:07 UTC
(In reply to comment #0)
> Description of problem:
> 
> cheese don't start
> 
> Additional info:
> 
> console output 
> (cheese:2803): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to
> find suitable fbconfig for the GLX context

This seems to be the problem (I think). Do you have working 3d acceleration on your laptop? Cheese needs working opengl support now a days.

Comment 2 Miguel 2011-09-29 13:59:51 UTC
In new versions it's working appears that was a problem with nvidia propietary drivers


Note You need to log in before you can comment on or make changes to this bug.