gnome-web-photo crashed with SIGSEGV in _dl_close_worker()

Bug #1551242 reported by kylea on 2016-02-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-web-photo (Ubuntu)

Bug Description

Occurred on Boot

Linux kylea-Latitude-E6510 4.4.0-8-generic #23-Ubuntu SMP Wed Feb 24 20:45:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-web-photo 0.10.6-1
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Mon Feb 29 23:26:28 2016
ExecutablePath: /usr/bin/gnome-web-photo
InstallationDate: Installed on 2015-12-31 (60 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: gnome-web-photo --mode=thumbnail --timeout=16 --thumbnail-size=256 file:///etc/drirc /tmp/.gnome_desktop_thumbnail.LZQFDY
 PATH=(custom, no user)
 Segfault happened at: 0x7f82437de81d: mov 0x8(%rbx),%rdi
 PC (0x7f82437de81d) ok
 source "0x8(%rbx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-web-photo
 ?? () from /usr/lib/nvidia-340/
 ?? () from /usr/lib/nvidia-340/
 ?? () from /usr/lib/nvidia-340/
 _dl_close_worker (map=map@entry=0x23132f0) at dl-close.c:744
 _dl_close_worker (map=0x23132f0) at dl-close.c:125
Title: gnome-web-photo crashed with SIGSEGV in _dl_close_worker()
UpgradeStatus: Upgraded to xenial on 2016-02-28 (1 days ago)

kylea (kylea) wrote :
information type: Private → Public

 ?? () from /tmp/apport_sandbox_d4NDcR/usr/lib/nvidia-340/
 ?? () from /tmp/apport_sandbox_d4NDcR/usr/lib/nvidia-340/
 ?? () from /tmp/apport_sandbox_d4NDcR/usr/lib/nvidia-340/
 ?? ()
 ?? ()

Changed in gnome-web-photo (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for nvidia-340

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers