After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772860 - [wayland] mutter segfaults on vt switch
[wayland] mutter segfaults on vt switch
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks: WaylandRelated
 
 
Reported: 2016-10-13 13:06 UTC by Olivier Fourdan
Modified: 2016-10-13 14:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Olivier Fourdan 2016-10-13 13:06:46 UTC 
Description:

Seems there is a (serious) regression in 3.22, gnome-shell/mutter will segfault when returning from a VT switch

Affected version:

gnome-shell-3.22.1-1.fc25
mutter-3.22.1-2.fc25

How reproducible:

Always

Steps to reproduce:

1. Run GNOME on Wayland
2. Switch to another VT
3. Switch back
4. Move the pointer over an existing window

Actual results:

gnome-shell segfaults and the entireuser session is lost

Expected results:

No crash

Additional data:

+ Trace 236740

  • #0 wl_resource_post_event
  • #1 wl_pointer_send_motion
    at /usr/include/wayland-server-protocol.h line 3423
  • #2 meta_wayland_pointer_send_motion
    at wayland/meta-wayland-pointer.c line 339
  • #3 notify_motion
    at wayland/meta-wayland-pointer.c line 558
  • #4 handle_motion_event
    at wayland/meta-wayland-pointer.c line 565
  • #5 meta_wayland_pointer_handle_event
    at wayland/meta-wayland-pointer.c line 711
  • #6 meta_wayland_seat_handle_event
    at wayland/meta-wayland-seat.c line 360
  • #7 meta_wayland_compositor_handle_event
    at wayland/meta-wayland.c line 208
  • #8 meta_display_handle_event
    at core/events.c line 386
  • #9 event_callback
    at core/events.c line 401
  • #10 _clutter_event_process_filters
    at clutter-event.c line 1913
  • #11 emit_pointer_event
    at clutter-main.c line 2011
  • #12 _clutter_process_event_details
    at clutter-main.c line 2372
  • #13 _clutter_process_event
    at clutter-main.c line 2548
  • #14 _clutter_stage_process_queued_events
    at clutter-stage.c line 1026
  • #15 master_clock_process_events
    at clutter-master-clock-default.c line 364
  • #16 clutter_clock_dispatch
    at clutter-master-clock-default.c line 561
  • #17 g_main_context_dispatch
  • #18 g_main_context_iterate.isra
  • #19 g_main_loop_run
  • #20 meta_run
    at core/main.c line 572
  • #21 main
    at main.c line 471
  • #0 wl_resource_post_event
  • #1 wl_pointer_send_motion
    at /usr/include/wayland-server-protocol.h line 3423
  • #2 meta_wayland_pointer_send_motion
    at wayland/meta-wayland-pointer.c line 339
  • #3 notify_motion
    at wayland/meta-wayland-pointer.c line 558
  • #4 handle_motion_event
    at wayland/meta-wayland-pointer.c line 565
  • #5 meta_wayland_pointer_handle_event
    at wayland/meta-wayland-pointer.c line 711
  • #6 meta_wayland_seat_handle_event
    at wayland/meta-wayland-seat.c line 360
  • #7 meta_wayland_compositor_handle_event
    at wayland/meta-wayland.c line 208
  • #8 meta_display_handle_event
    at core/events.c line 386
  • #9 event_callback
    at core/events.c line 401
  • #10 _clutter_event_process_filters
    at clutter-event.c line 1913
  • #11 emit_pointer_event
    at clutter-main.c line 2011
  • #12 _clutter_process_event_details
    at clutter-main.c line 2372
  • #13 _clutter_process_event
    at clutter-main.c line 2548
  • #14 _clutter_stage_process_queued_events
    at clutter-stage.c line 1026
  • #15 master_clock_process_events
    at clutter-master-clock-default.c line 364
  • #16 clutter_clock_dispatch
    at clutter-master-clock-default.c line 561
  • #17 g_main_context_dispatch
  • #18 g_main_context_iterate.isra
  • #19 g_main_loop_run
  • #20 meta_run
    at core/main.c line 572
  • #21 main
    at main.c line 471 






Comment 1


Jonas Ådahl





          2016-10-13 13:51:00 UTC
        



Does it reproduce on master. I VT switched back and forth a lot today and didn't get see any crash.






Comment 2


Olivier Fourdan





          2016-10-13 14:15:52 UTC
        



(In reply to Jonas Ådahl from comment #1)
> Does it reproduce on master. I VT switched back and forth a lot today and
> didn't get see any crash.

Indeed, there've been several fixes (from you!) in this area since 3.22.1 and I cannot reproduce using a current git master.

So closing for now...