Ubuntu
cheese package

cheese crashed with signal 5 in _XError()

Bug #605818 reported by Jan on 2010-07-15

This bug report is a duplicate of: Bug #594699: Cheese crashes soon after start - gtk-csd. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cheese (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: cheese

Cheese starts and closes after about 2-3 seconds.
This also happened on Lucid before I upgraded to the development release.

Running cheese from terminal puts:
progname=cheese; RGBA=on

Gdk-ERROR **: The program 'cheese' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 28 error_code 8 request_code 139 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Trace/breakpoint trap (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: cheese 2.30.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-7.12-server 2.6.35-rc4
Uname: Linux 2.6.35-7-server x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 15 11:33:39 2010
ExecutablePath: /usr/bin/cheese
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Zepto Nox
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-7-server root=UUID=00aff323-5cbe-412c-b54c-768bcbdf1330 ro quiet splash
ProcCmdline: cheese
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
Signal: 5
SourcePackage: cheese
StacktraceTop:
?? () from /usr/lib/libgdk-x11-2.0.so.0
_XError () from /usr/lib/libX11.so.6
?? () from /usr/lib/libX11.so.6
_XReply () from /usr/lib/libX11.so.6
XSync () from /usr/lib/libX11.so.6
Title: cheese crashed with signal 5 in _XError()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/08/2008
dmi.bios.version: A15H
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Zepto
dmi.board.vendor: Zepto
dmi.board.version: AURA_V0.27-EC23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Zepto
dmi.chassis.version: Zepto
dmi.modalias: dmi:bvn:bvrA15H:bd07/08/2008:svnZepto:pnNox:pvrA15H:rvnZepto:rnZepto:rvrAURA_V0.27-EC23:cvnZepto:ct1:cvrZepto:
dmi.product.name: Nox
dmi.product.version: A15H
dmi.sys.vendor: Zepto

See original description

Tags:

Revision history for this message

Jan (jancborchardt-deactivatedaccount) wrote on 2010-07-15:

BootDmesg.txt Edit (60.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (5.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (910 bytes, text/plain; charset="utf-8")
GstreamerVersions.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (793 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (55.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (792 bytes, text/plain; charset="utf-8")
Registers.txt Edit (741 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (12.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (120.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (259.9 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (15.0 MiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (24.8 KiB, text/plain; charset="utf-8")

description:

updated

Revision history for this message

Vish (vish) wrote on 2010-07-16:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 594699, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.