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 788971 - gnome-shell crashed in meta_display_get_current_time_roundtrip on resume from suspend
gnome-shell crashed in meta_display_get_current_time_roundtrip on resume from...
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: wayland
3.26.x
Other Linux
: Normal major
: ---
Assigned To: mutter-maint
mutter-maint
: 789095 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-10-14 00:02 UTC by Marco Trevisan (Treviño)
Modified: 2021-06-18 16:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
display: trap X errors in get_current_time_roundtrip (1.63 KB, patch)
2017-10-14 00:09 UTC, Marco Trevisan (Treviño)
none Details | Review

Description Marco Trevisan (Treviño) 2017-10-14 00:02:54 UTC
As per ubuntu bug https://pad.lv/1723048:

Test Case
1. Attach an external monitor to a laptop and set the output to external display only
2. Suspend the laptop
3. Detach the external monitor
4. Resume the laptop

Actual Result
The system didn't resume and this crash was notified.

Backtrace

  • #0 _g_log_abort
    at ../../../../glib/gmessages.c line 554
  • #1 g_log_default_handler
    at ../../../../glib/gmessages.c line 3051
  • #2 default_log_handler
    at ../src/main.c line 311
  • #3 g_logv
    at ../../../../glib/gmessages.c line 1341
  • #4 g_log
    at ../../../../glib/gmessages.c line 1403
  • #5 x_io_error
    at wayland/meta-xwayland.c line 411
  • #6 _XIOError
    at ../../src/XlibInt.c line 1469
  • #7 _XReadEvents
    at ../../src/xcb_io.c line 400
  • #8 XIfEvent
    at ../../src/IfEvent.c line 68
  • #9 meta_display_get_current_time_roundtrip
    at core/display.c line 1332
  • #10 meta_wayland_surface_destroy_window
    at wayland/meta-wayland-surface.c line 423
  • #11 wl_surface_destructor
    at wayland/meta-wayland-surface.c line 1304
  • #12 destroy_resource
    at ../src/wayland-server.c line 675
  • #13 for_each_helper
    at ../src/wayland-util.c line 374
  • #14 wl_map_for_each
    at ../src/wayland-util.c line 387
  • #15 wl_client_destroy
    at ../src/wayland-server.c line 832
  • #16 wl_client_connection_data
    at ../src/wayland-server.c line 318
  • #17 wl_event_loop_dispatch
    at ../src/event-loop.c line 423
  • #18 wayland_event_source_dispatch
    at wayland/meta-wayland.c line 84
  • #19 g_main_dispatch
    at ../../../../glib/gmain.c line 3148
  • #20 g_main_context_dispatch
    at ../../../../glib/gmain.c line 3813
  • #21 g_main_context_iterate
    at ../../../../glib/gmain.c line 3886
  • #22 g_main_loop_run
    at ../../../../glib/gmain.c line 4082
  • #23 meta_run
    at core/main.c line 648
  • #24 main
    at ../src/main.c line 462

Comment 1 Marco Trevisan (Treviño) 2017-10-14 00:09:43 UTC
Created attachment 361564 [details] [review]
display: trap X errors in get_current_time_roundtrip

Only return the actual timestamp if we get one.
Comment 2 Jonas Ådahl 2017-10-16 04:06:18 UTC
Why do we even get an error? I don't see why this would ever happen, unless Xwayland has crashed and this is one of those errors.
Comment 3 Florian Müllner 2017-10-17 13:17:41 UTC
*** Bug 789095 has been marked as a duplicate of this bug. ***
Comment 4 Rui Matos 2017-12-07 15:06:57 UTC
I saw this trace in a case where xwayland seemed to be crashing due to bug 789070. Can you try the patch there and report back if it improves things for you?
Comment 5 André Klapper 2021-06-18 16:01:03 UTC
Closing this bug report as no further information has been provided. Please feel free to report this at https://gitlab.gnome.org if you can provide the information that was asked for in a previous comment and if this still happens in a recent and supported version. Thanks!