Ubuntu
cheese package

cheese crashed with SIGSEGV in g_slice_alloc()

Bug #833849 reported by Amit Rana
78
This bug affects 16 people
Affects Status Importance Assigned to Milestone
cheese (Ubuntu)
Expired
Medium
Unassigned

Bug Description

cheese crashes on start.

lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10

apt-cache policy cheese
cheese:
  Installed: 3.0.1-2ubuntu2
  Candidate: 3.0.1-2ubuntu2
  Version table:
 *** 3.0.1-2ubuntu2 0
        500 http://in.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: cheese 3.0.1-2ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 25 20:58:33 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/cheese
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Dell System XPS L702X
ProcCmdline: cheese
RelatedPackageVersions:
 cheese 3.0.1-2ubuntu2
 cheese-common 3.0.1-2ubuntu2
SegvAnalysis:
 Segfault happened at: 0x7f28255c9598 <g_slice_alloc+280>: mov 0x8(%rax),%rbx
 PC (0x7f28255c9598) ok
 source "0x8(%rax)" (0x100000007) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: cheese
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_new_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: cheese crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to oneiric on 2011-08-23 (1 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare video
dmi.bios.date: 06/01/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 0XN71K
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd06/01/2011:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L702X
dmi.sys.vendor: Dell Inc.

Revision history for this message
Amit Rana (amit-rana) wrote :
Revision history for this message
Amit Rana (amit-rana) wrote :

gdb backtrace

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x1014900) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:488
 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:795
 g_slice_alloc (mem_size=88) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:833
 g_hash_table_new_full (hash_func=0x40a300 <g_str_hash@plt>, key_equal_func=0x7f28255ce260 <g_str_equal>, key_destroy_func=0, value_destroy_func=0x7f2825f88050 <exported_object_free>) at /build/buildd/glib2.0-2.29.16/./glib/ghash.c:644
 g_dbus_connection_init (connection=0x114c810) at /build/buildd/glib2.0-2.29.16/./gio/gdbusconnection.c:926

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cheese (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Amit Rana (amit-rana)
visibility: private → public
Launchpad Janitor (janitor)
Changed in cheese (Ubuntu):
status: New → Confirmed
Revision history for this message
Kootee (kootee) wrote :

It affects also me on Ubuntu 13.10. I think it may be connected with x64 build, because I also use amd64 version of Ubuntu. In my case crash appear not on start, but after random time of using application. I haven't found any reason or reproduce, just random time of using app.

Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013 and
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

Does anyone still see a problem related to the one that was reported in a currently supported version of Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in cheese (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cheese (Ubuntu) because there has been no activity for 60 days.]

Changed in cheese (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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