cheese crashed with SIGSEGV in wl_proxy_add_listener()

Bug #1751412 reported by Chris Burton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Cheese won't start in Ubuntu 17.10

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: cheese 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 15:28:13 2018
ExecutablePath: /usr/bin/cheese
InstallationDate: Installed on 2016-10-29 (482 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA PORTEGE R500
ProcCmdline: cheese
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 cheese 3.26.0-0ubuntu1
 cheese-common 3.26.0-0ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f8cc321577c <wl_proxy_add_listener+12>: testb $0x4,0x28(%rdi)
 PC (0x7f8cc321577c) ok
 source "$0x4" ok
 destination "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: linux
StacktraceTop:
 wl_proxy_add_listener () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
Title: cheese crashed with SIGSEGV in wl_proxy_add_listener()
UpgradeStatus: Upgraded to artful on 2018-02-24 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/15/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.20
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.20:bd06/15/2007:svnTOSHIBA:pnPORTEGER500:pvrPPR50A-02T01X:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.family: 0000000000
dmi.product.name: PORTEGE R500
dmi.product.version: PPR50A-02T01X
dmi.sys.vendor: TOSHIBA

Revision history for this message
Chris Burton (looigi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1723426, so 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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.