cheese crashed with SIGSEGV in start_thread()

Bug #286569 reported by Erik
70
This bug affects 13 people
Affects Status Importance Assigned to Milestone
cheese (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cheese

Using Intrepid Ibex beta, updated as of Monday 20th of October 2008.
Cam is a Logitech Quickcam Pro 9000 identified as /dev/video0 by V4L2.

Description: Ubuntu intrepid (development branch)
Release: 8.10

cheese:
  Installed: 2.24.0-0ubuntu1
  Candidate: 2.24.0-0ubuntu1
  Version table:
 *** 2.24.0-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

Tried to start cheese, no video showed up. Tried to click exit, but the program crashed instead.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/cheese
NonfreeKernelModules: nvidia
Package: cheese 2.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: cheese
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: cheese
Stacktrace:
 #0 0x0805993a in ?? ()
 #1 0x0805ce4c in ?? ()
 #2 0xb71d802f in ?? () from /usr/lib/libglib-2.0.so.0
 #3 0xb715450f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 #4 0xb70d17ee in clone () from /lib/tls/i686/cmov/libc.so.6
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: cheese crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner vboxusers video

Revision history for this message
Erik (erik-yi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in cheese:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in cheese:
status: Incomplete → Invalid
Revision history for this message
Patrick (patrick-trentin) wrote :

I would try to obtain a backtrace, if someone could gently help me how to perform the action indicated in this statement:

"First, check if there is a package with a -dbg suffix in the main Ubuntu repositories (TODO: Please edit this wiki here to describe how to do this). These are the debug symbol packages, and are equivalent to '-dbgsym' described below. You can safely use either one, but not both at once."

I've seen that in my repository 10.4 beta there is a package called "pkg-create-dbgsym" and described as "automatically build debug symbol ddeb packages". Is this connected to what you require for backtracking?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.