cheese crashed with SIGSEGV in wl_proxy_add_listener()
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
ProcVersionSign
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_
LANG=en_NZ.UTF-8
SHELL=/bin/bash
RelatedPackageV
cheese 3.26.0-0ubuntu1
cheese-common 3.26.0-0ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f8cc321577c <wl_proxy_
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_
?? () from /usr/lib/
eglSwapBuffers () from /usr/lib/
?? () from /usr/lib/
cogl_onscreen_
Title: cheese crashed with SIGSEGV in wl_proxy_
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.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.family: 0000000000
dmi.product.name: PORTEGE R500
dmi.product.
dmi.sys.vendor: TOSHIBA
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.