Bug 696869 - [abrt] cheese-3.0.0-2.fc15: Process /usr/bin/cheese was killed by signal 11 (SIGSEGV)
Summary: [abrt] cheese-3.0.0-2.fc15: Process /usr/bin/cheese was killed by signal 11 (...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cheese
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fddb6c7edf4174977fa48273fca...
: 699110 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 04:37 UTC by Zach Lute
Modified: 2011-09-29 18:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-29 18:04:09 UTC
Type: ---


Attachments (Terms of Use)
File: smaps (153.24 KB, text/plain)
2011-04-15 04:37 UTC, Zach Lute
no flags Details
File: maps (32.73 KB, text/plain)
2011-04-15 04:37 UTC, Zach Lute
no flags Details
File: dsos (24.60 KB, text/plain)
2011-04-15 04:37 UTC, Zach Lute
no flags Details
File: backtrace (28.81 KB, text/plain)
2011-04-15 04:37 UTC, Zach Lute
no flags Details

Description Zach Lute 2011-04-15 04:37:35 UTC
abrt version: 2.0.0
comment: Tried to run Cheese on my Macbook Air using nvidia drivers from rpmfusion (because nouveau driver doesn't work). Cheese crashes immediately on startup.
executable: /usr/bin/cheese
cmdline: cheese
component: cheese
package: cheese-3.0.0-2.fc15
kernel: 2.6.38.2-9.fc15.x86_64
reason: Process /usr/bin/cheese was killed by signal 11 (SIGSEGV)
uid: 500
architecture: x86_64
username: zach
os_release: Fedora release 15 (Lovelock)
time: 1302842072
rating: 4

Text file: smaps, 156914 bytes
Binary file: coredump, 42000384 bytes
Text file: maps, 33518 bytes
Text file: dsos, 25191 bytes
Text file: backtrace, 29502 bytes

event_log
-----
2011-04-14-23:35:27> (exited with 0)
2011-04-14-23:35:27> Analyzing coredump '/home/zach/.abrt/spool/ccpp-2011-04-14-23:34:32-2196/coredump'
2011-04-14-23:35:27  All 94 debuginfo files are available
2011-04-14-23:35:28> Backtrace is generated and saved, 29502 bytes
2011-04-14-23:35:28> (exited with 0)

Comment 1 Zach Lute 2011-04-15 04:37:41 UTC
Created attachment 492275 [details]
File: smaps

Comment 2 Zach Lute 2011-04-15 04:37:43 UTC
Created attachment 492276 [details]
File: maps

Comment 3 Zach Lute 2011-04-15 04:37:45 UTC
Created attachment 492277 [details]
File: dsos

Comment 4 Zach Lute 2011-04-15 04:37:47 UTC
Created attachment 492278 [details]
File: backtrace

Comment 5 Paul W. Frields 2011-04-23 17:26:27 UTC
*** Bug 699110 has been marked as a duplicate of this bug. ***

Comment 6 Jonas Wielicki 2011-05-01 15:29:29 UTC
Package: cheese-3.0.1-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Attempted to start cheese.

Comment 7 Nicolas R. 2011-05-04 12:03:29 UTC
Package: cheese-3.0.1-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
just launching cheese

Comment 8 Gabriel Speckhahn 2011-05-04 14:59:20 UTC
Package: cheese-3.0.1-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Opening Cheese

Comment 9 Hans de Goede 2011-09-29 18:04:09 UTC
Unfortunately cheese in F-15 <= 3.0.1 has several known issues which causes it to crash in various ways. Upstream has recently released 3.0.2 which fixes these known issues, and we've prepared an update for F-15 for this.

Unfortunately due to the issues with the earlier release we've quite a few open (abrt) crash bugs against cheese for F-15. Too many to go through them one by one and verify that they are actually a variant of one of the known and fixed issues. Therefore we are closing all the F-15 cheese crash bugs.

You can upgrade to the 3.0.2 update by running the following command from a terminal:
su -c 'yum update --enablerepo=updates-testing cheese'

If you still experience the same crash as before (or a new one), please do file a bug and we will try to investigate!


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