evince crashed with SIGSEGV

Bug #1725316 reported by Marc Langer on 2017-10-20

This bug report will be marked for expiration in 37 days if no further activity occurs. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)

Bug Description

Virtual keyboard was closed, in the same moment evince crashed. Just upgraded from 17.04 to 17.10.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
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: Fri Oct 20 16:01:40 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2014-09-09 (1136 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=fe9caf9e-acd4-41ab-84d3-ff3a285fa314 ro quiet splash vt.handoff=7
 PATH=(custom, no user)
 Segfault happened at: 0x7f6357758c9a: testb $0x1,0x24(%rsi)
 PC (0x7f6357758c9a) ok
 source "$0x1" ok
 destination "0x24(%rsi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evince
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
 () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
Title: evince crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

Marc Langer (marc-marclanger) wrote :

 touch_handle_motion (data=0x55c52c992030, wl_touch=<optimized out>, time=6672261, id=<optimized out>, x=431651, y=141008) at ././gdk/wayland/gdkdevice-wayland.c:2480
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffc500c3080, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffc500c3150) at ../src/x86/ffi64.c:525
 wl_closure_invoke (closure=closure@entry=0x55c52c9b4f00, flags=flags@entry=1, target=<optimized out>, target@entry=0x55c52c9c1390, opcode=opcode@entry=2, data=<optimized out>) at ../src/connection.c:935
 dispatch_event (display=display@entry=0x55c52c96d810, queue=<optimized out>) at ../src/wayland-client.c:1310

Changed in evince (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

information type: Private → Public
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 17.10 (artful) reached end-of-life on July 19, 2018.

Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do 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 evince (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers