evince crashed with SIGSEGV in gdk_window_get_root_coords()

Bug #1823686 reported by Don Le
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Expired
Low
Unassigned

Bug Description

evince crashed with SIGSEGV in gdk_window_get_root_coords()

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: evince 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr 8 16:45:19 2019
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2019-03-17 (22 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=UUID=214f3b1c-6c77-4ce6-a3d7-1cda16b41c97 ro quiet splash resume=UUID=0e88596d-7ca9-407b-8da4-af600e024f01 vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f02e9654000 <gdk_window_get_root_coords+32>: mov (%rbx),%rdx
 PC (0x7f02e9654000) ok
 source "(%rbx)" (0x3ff0000000000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 gdk_window_get_root_coords () from /lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
 ffi_call_unix64 () from /lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.6
Title: evince crashed with SIGSEGV in gdk_window_get_root_coords()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
separator:

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

StacktraceTop:
 gdk_window_get_root_coords (window=0x3ff0000000000000, x=0, y=-13312, root_x=0x7ffd5b723430, root_y=0x7ffd5b723434) at ../../../../gdk/gdkwindow.c:6848
 notify_cursor_location (context=context@entry=0x55e0a6fd6c70) at ../../../../../modules/input/imwayland.c:360
 enable (context_wayland=0x55e0a6fd6c70) at ../../../../../modules/input/imwayland.c:618
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffd5b7235b0, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffd5b723680) at ../src/x86/ffi64.c:525

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evince (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in evince (Ubuntu):
importance: Medium → Low
status: New → Incomplete
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

(the issue seems to be in the wayland im code)

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in evince (Ubuntu):
status: Incomplete → Expired
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.