Ubuntu
cheese package

cheese crashed with SIGSEGV

Bug #554922 reported by ChoiceForGrowth20 on 2010-04-04

This bug report is a duplicate of: Bug #543758: cheese crashed with SIGSEGV when webcam is already in use. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cheese (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: cheese

I attempted to use run cheese while skype was using video cam.

Hope this helps! Perhaps I shouldn't try to have two things access my webcam.

~Alex

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: cheese 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 3 20:35:02 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/cheese
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: cheese
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: cheese
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/libgstbase-0.10.so.0
?? () from /usr/lib/libgstbase-0.10.so.0
?? () from /usr/lib/libgstreamer-0.10.so.0
Title: cheese crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

ChoiceForGrowth20 (alex-murphy) wrote on 2010-04-04:

Dependencies.txt Edit (5.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (52.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (796 bytes, text/plain; charset="utf-8")
Registers.txt Edit (800 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (913 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.8 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (709 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2010-04-04:

StacktraceTop:
?? ()
gst_v4l2src_create (src=0x7f2ccc008350,
gst_base_src_get_range (src=0x7f2ccc008350,
gst_base_src_loop (pad=0x7f2ccc00a340)
gst_task_func (task=0x10a2390) at gsttask.c:238

Revision history for this message

Apport retracing service (apport) wrote on 2010-04-04: Stacktrace.txt

Stacktrace.txt Edit (1.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-04-04: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (6.7 KiB, text/plain)

Changed in cheese (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Vish (vish) wrote on 2010-05-10:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in cheese (Ubuntu):
status:	New → Incomplete

Revision history for this message

ChoiceForGrowth20 (alex-murphy) wrote on 2010-05-10: Re: [Bug 554922] Re: cheese crashed with SIGSEGV

Hmm possibly.

On Mon, May 10, 2010 at 11:26 AM, Vish <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. Please answer these questions:
> 1. Is this reproducible?
> 2. If so, what specific steps should we take to recreate this bug? Be as
> detailed as possible.
>
> Please try to obtain a backtrace following the instructions at
> http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
> (as an attachment) to the bug report. This will greatly help us in
> tracking down your problem.
>
> ** Changed in: cheese (Ubuntu)
> Status: New => Incomplete
>
> --
> cheese crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/554922
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “cheese” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: cheese
>
> I attempted to use run cheese while skype was using video cam.
>
> Hope this helps! Perhaps I shouldn't try to have two things access my
> webcam.
>
> ~Alex
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.04
> Package: cheese 2.30.0-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
> Uname: Linux 2.6.32-19-generic x86_64
> Architecture: amd64
> CrashCounter: 1
> Date: Sat Apr 3 20:35:02 2010
> Disassembly: => 0x0: Cannot access memory at address 0x0
> ExecutablePath: /usr/bin/cheese
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
> ProcCmdline: cheese
> ProcEnviron:
> LANG=en_US.utf8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x0: Cannot access memory at address 0x0
> PC (0x00000000) not located in a known VMA region (needed executable
> region)!
> SegvReason: executing NULL VMA
> Signal: 11
> SourcePackage: cheese
> StacktraceTop:
> ?? ()
> ?? ()
> ?? () from /usr/lib/libgstbase-0.10.so.0
> ?? () from /usr/lib/libgstbase-0.10.so.0
> ?? () from /usr/lib/libgstreamer-0.10.so.0
> Title: cheese crashed with SIGSEGV
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/554922/+subscribe
>

Hmm possibly.

On Mon, May 10, 2010 at 11:26 AM, Vish <drkvi-a@yahoo.com> wrote:

> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. Please answer these questions:
> 1. Is this reproducible?
> 2. If so, what specific steps should we take to recreate this bug? Be as
> detailed as possible.
>
> Please try to obtain a backtrace following the instructions at
> http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
> (as an attachment) to the bug report. This will greatly help us in
> tracking down your problem.
>
> ** Changed in: cheese (Ubuntu)
>       Status: New => Incomplete
>
> --
> cheese crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/554922
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “cheese” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: cheese
>
> I attempted to use run cheese  while skype was using video cam.
>
> Hope this helps!  Perhaps I shouldn't try to have two things access my
> webcam.
>
> ~Alex
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.04
> Package: cheese 2.30.0-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
> Uname: Linux 2.6.32-19-generic x86_64
> Architecture: amd64
> CrashCounter: 1
> Date: Sat Apr  3 20:35:02 2010
> Disassembly: => 0x0:    Cannot access memory at address 0x0
> ExecutablePath: /usr/bin/cheese
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
> ProcCmdline: cheese
> ProcEnviron:
>  LANG=en_US.utf8
>  SHELL=/bin/bash
> SegvAnalysis:
>  Segfault happened at: 0x0:     Cannot access memory at address 0x0
>  PC (0x00000000) not located in a known VMA region (needed executable
> region)!
> SegvReason: executing NULL VMA
> Signal: 11
> SourcePackage: cheese
> StacktraceTop:
>  ?? ()
>  ?? ()
>  ?? () from /usr/lib/libgstbase-0.10.so.0
>  ?? () from /usr/lib/libgstbase-0.10.so.0
>  ?? () from /usr/lib/libgstreamer-0.10.so.0
> Title: cheese crashed with SIGSEGV
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/554922/+subscribe
>

Revision history for this message

Vish (vish) wrote on 2010-06-20:

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 543758, 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.

Revision history for this message

ChoiceForGrowth20 (alex-murphy) wrote on 2011-05-31: hey Bug

Hello Bug I quit my job lol http://g.msn.com.br/BR9/1369.0?http://cnbc7.com/news