Bug 2268493

Summary: [abrt] evince: _gdk_wayland_cursor_get_buffer(): evince killed by SIGSEGV
Product: [Fedora] Fedora Reporter: lordmethenor
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: feborges, gnome-sig, lordmethenor, mclasen, mkasik, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cb720cb94b3e14bb9fbb52d61a788df6e63d52b
Whiteboard: abrt_hash:3196f738cb50fb5401f2d854ae2e3dbd8bad200a;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-28 11:37:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: cgroup
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: backtrace
none
File: environ none

Description lordmethenor 2024-03-07 19:34:27 UTC
Description of problem:
I had a multi-page PDF and was scrolling (two finger touchpad) down.

Version-Release number of selected component:
evince-45.0-1.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         evince killed by SIGSEGV
journald_cursor: s=f53c530a1eaf49639387fb2c09182892;i=4867e7;b=c54f946e12964bb482daf7495c664f7f;m=1d37093fa;t=613171da8e61b;x=9f983f112606074c
executable:     /usr/bin/evince
cmdline:        /usr/bin/evince /home/adonnen/Cloud/Courses/Algorithms/Notes/1-25-24.pdf
rootdir:        /
uid:            1000
kernel:         6.7.7-200.fc39.x86_64
package:        evince-45.0-1.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: _gdk_wayland_cursor_get_buffer
comment:        I had a multi-page PDF and was scrolling (two finger touchpad) down.

Truncated backtrace:
Thread no. 1 (17 frames)
 #0 _gdk_wayland_cursor_get_buffer at ../gdk/wayland/gdkcursor-wayland.c:236
 #1 gdk_wayland_device_update_window_cursor at ../gdk/wayland/gdkdevice-wayland.c:424
 #2 pointer_handle_enter at ../gdk/wayland/gdkdevice-wayland.c:1579
 #3 ffi_call_unix64 at ../src/x86/unix64.S:104
 #4 ffi_call_int at ../src/x86/ffi64.c:673
 #5 ffi_call at ../src/x86/ffi64.c:710
 #6 wl_closure_invoke at ../src/connection.c:1025
 #7 dispatch_event at ../src/wayland-client.c:1631
 #8 dispatch_queue at ../src/wayland-client.c:1777
 #9 wl_display_dispatch_queue_pending at ../src/wayland-client.c:2019
 #10 wl_display_dispatch_pending at ../src/wayland-client.c:2082
 #11 _gdk_wayland_display_queue_events at ../gdk/wayland/gdkeventsource.c:201
 #12 gdk_display_get_event at ../gdk/gdkdisplay.c:442
 #15 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
 #16 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
 #17 g_main_context_iteration at ../glib/gmain.c:4414
 #18 g_application_run at ../gio/gapplication.c:2577

Comment 1 lordmethenor 2024-03-07 19:34:31 UTC
Created attachment 2020489 [details]
File: proc_pid_status

Comment 2 lordmethenor 2024-03-07 19:34:32 UTC
Created attachment 2020490 [details]
File: maps

Comment 3 lordmethenor 2024-03-07 19:34:34 UTC
Created attachment 2020491 [details]
File: limits

Comment 4 lordmethenor 2024-03-07 19:34:35 UTC
Created attachment 2020492 [details]
File: cgroup

Comment 5 lordmethenor 2024-03-07 19:34:36 UTC
Created attachment 2020493 [details]
File: open_fds

Comment 6 lordmethenor 2024-03-07 19:34:37 UTC
Created attachment 2020494 [details]
File: mountinfo

Comment 7 lordmethenor 2024-03-07 19:34:39 UTC
Created attachment 2020495 [details]
File: os_info

Comment 8 lordmethenor 2024-03-07 19:34:40 UTC
Created attachment 2020496 [details]
File: cpuinfo

Comment 9 lordmethenor 2024-03-07 19:34:41 UTC
Created attachment 2020497 [details]
File: core_backtrace

Comment 10 lordmethenor 2024-03-07 19:34:43 UTC
Created attachment 2020498 [details]
File: exploitable

Comment 11 lordmethenor 2024-03-07 19:34:44 UTC
Created attachment 2020499 [details]
File: dso_list

Comment 12 lordmethenor 2024-03-07 19:34:46 UTC
Created attachment 2020500 [details]
File: backtrace

Comment 13 lordmethenor 2024-03-07 19:34:48 UTC
Created attachment 2020501 [details]
File: environ

Comment 14 Aoife Moloney 2024-11-13 12:11:55 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 15 Aoife Moloney 2024-11-28 11:37:13 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.