[Bug 605818] Re: cheese crashed with signal 5 in _XError()

2010-07-16 Thread Vish
*** This bug is a duplicate of bug 594699 ***
https://bugs.launchpad.net/bugs/594699

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.

** This bug has been marked a duplicate of bug 594699
   Cheese crashes soon after start - gtk-csd

-- 
cheese crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/605818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 605818] Re: cheese crashed with signal 5 in _XError()

2010-07-15 Thread Jan-Christoph Borchardt

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/51971976/BootDmesg.txt

** Attachment added: CurrentDmesg.txt
   http://launchpadlibrarian.net/51971977/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/51971978/Dependencies.txt

** Attachment added: Disassembly.txt
   http://launchpadlibrarian.net/51971979/Disassembly.txt

** Attachment added: GstreamerVersions.txt
   http://launchpadlibrarian.net/51971980/GstreamerVersions.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/51971981/Lspci.txt

** Attachment added: Lsusb.txt
   http://launchpadlibrarian.net/51971982/Lsusb.txt

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/51971983/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/51971984/ProcInterrupts.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/51971985/ProcMaps.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/51971986/ProcModules.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/51971987/ProcStatus.txt

** Attachment added: Registers.txt
   http://launchpadlibrarian.net/51971988/Registers.txt

** Attachment added: Stacktrace.txt
   http://launchpadlibrarian.net/51971989/Stacktrace.txt

** Attachment added: ThreadStacktrace.txt
   http://launchpadlibrarian.net/51971990/ThreadStacktrace.txt

** Attachment added: UdevDb.txt
   http://launchpadlibrarian.net/51971991/UdevDb.txt

** Attachment added: UdevLog.txt
   http://launchpadlibrarian.net/51971992/UdevLog.txt

** Attachment added: XorgLog.txt
   http://launchpadlibrarian.net/51971993/XorgLog.txt

** Attachment added: XsessionErrors.txt
   http://launchpadlibrarian.net/51971994/XsessionErrors.txt

** Description changed:

  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.)
+   (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
+  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
+  ?? () 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

-- 
cheese crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/605818
You received this bug notification because you are a member of Ubuntu
Bugs, which is