Bug 1392628

Created attachment 1218273 [details]
File: backtrace

Created attachment 1218274 [details]
File: cgroup

Created attachment 1218275 [details]
File: core_backtrace

Created attachment 1218276 [details]
File: dso_list

Created attachment 1218277 [details]
File: environ

Created attachment 1218278 [details]
File: exploitable

Created attachment 1218279 [details]
File: limits

Created attachment 1218280 [details]
File: maps

Created attachment 1218281 [details]
File: mountinfo

Created attachment 1218282 [details]
File: namespaces

Created attachment 1218283 [details]
File: open_fds

Similar problem has been detected:

The  computer tried to resume from "rest".

reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _clutter_input_device_reset_scroll_info
executable:     /usr/bin/gnome-shell
global_pid:     2779
kernel:         4.9.5-100.fc24.x86_64
package:        gnome-shell-3.20.4-3.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Hello.
had the same problem with core file created. Below is the stack trace.

(gdb) bt
#0  _clutter_input_device_reset_scroll_info (device=device@entry=0x0)
    at ./clutter-input-device.c:1742
#1  0x00007fa75973a4eb in clutter_device_manager_xi2_translate_event (
    translator=<optimized out>, native=<optimized out>, event=0x3a543a0)
    at x11/clutter-device-manager-xi2.c:1318
#2  0x00007fa75975c6ac in clutter_backend_real_translate_event (backend=<optimized out>,
    native=0x7ffe89fa8590, event=0x3a543a0) at ./clutter-backend.c:629
#3  0x00007fa7597351e2 in clutter_x11_handle_event (xevent=xevent@entry=0x7ffe89fa8590)
    at x11/clutter-event-x11.c:200
#4  0x00007fa75a3425dd in handle_host_xevent (event=0x7ffe89fa8590, backend=0xae82d0)
    at backends/x11/meta-backend-x11.c:219
#5  x_event_source_dispatch (source=<optimized out>, callback=<optimized out>,
    user_data=<optimized out>) at backends/x11/meta-backend-x11.c:272
#6  0x00007fa755f4f79a in g_main_dispatch (context=0xae0340) at gmain.c:3109
#7  g_main_context_dispatch (context=context@entry=0xae0340) at gmain.c:3708
#8  0x00007fa755f4fae8 in g_main_context_iterate (context=0xae0340, block=block@entry=1,
    dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3779
#9  0x00007fa755f4fdba in g_main_loop_run (loop=0xae96e0) at gmain.c:3973
#10 0x00007fa75a369f38 in meta_run () at core/main.c:473
#11 0x0000000000402455 in main (argc=1, argv=0x7ffe89fa8948) at main.c:471

(gdb) frame 1
#1  0x00007fa75973a4eb in clutter_device_manager_xi2_translate_event (
    translator=<optimized out>, native=<optimized out>, event=0x3a543a0)
    at x11/clutter-device-manager-xi2.c:1318
1318    x11/clutter-device-manager-xi2.c: No such file or directory.
(gdb) p/x device
$1 = 0xc581c0
(gdb) p/x source_device 
$2 = 0x0

(gdb) p/x xi_event
$3 = 0x109b8d0
(gdb) p/x xi_event->evtype
$4 = 0x7 //  == XI_Enter


The code is here:
1270     case XI_Enter:
1271     case XI_Leave:
1272       {
1273         XIEnterEvent *xev = (XIEnterEvent *) xi_event;
1274 
1275         device = g_hash_table_lookup (manager_xi2->devices_by_id,
1276                                       GINT_TO_POINTER (xev->deviceid));
1277 
1278         source_device = g_hash_table_lookup (manager_xi2->devices_by_id,
1279                                              GINT_TO_POINTER (xev->sourceid));
1280 
...
1317 
1318         _clutter_input_device_reset_scroll_info (source_device); // HERE we pass NULL
1319 
1320         clutter_event_set_device (event, device);
1321         clutter_event_set_source_device (event, source_device);
1322 
1323         retval = CLUTTER_TRANSLATE_QUEUE;
1324       }
1325       break;


Clearly source_device was null and the code isn't protected against that.
Why the source dev is not found in the hash table is another question.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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