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 771212 - crash when disconnecting monitor.
crash when disconnecting monitor.
Status: RESOLVED DUPLICATE of bug 730551
Product: mutter
Classification: Core
Component: general
3.21.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2016-09-10 20:57 UTC by Hussam Al-Tayeb
Modified: 2016-09-10 21:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hussam Al-Tayeb 2016-09-10 20:57:23 UTC
There is a larger problem with a test case is:
xrandr --nograb --output HDMI-0 --off ; xrandr --output HDMI-0 --preferred 
This occasionally crashes gnome-shell on my computer after causing some lag.

backtrace.

Reading symbols from /usr/bin/gnome-shell...done.
[New LWP 12357]
[New LWP 22734]
[New LWP 22735]
[New LWP 22737]
[New LWP 22740]
[New LWP 22741]
[New LWP 22742]

warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
  • #0 meta_workspace_get_onmonitor_region
    at core/workspace.c line 1054
  • #0 meta_workspace_get_onmonitor_region
    at core/workspace.c line 1054
  • #1 setup_constraint_info
  • #2 meta_window_constrain
  • #3 meta_window_move_resize_internal
  • #4 meta_window_move_resize_frame
    at core/window.c line 3825
  • #5 g_slist_foreach
    at gslist.c line 878
  • #6 meta_screen_foreach_window
  • #7 on_monitors_changed
    at core/screen.c line 2404
  • #8 ffi_call_unix64
    from /usr/lib/libffi.so.6
  • #9 ffi_call
    from /usr/lib/libffi.so.6
  • #10 g_cclosure_marshal_generic
    at gclosure.c line 1490
  • #11 g_closure_invoke
    at gclosure.c line 804
  • #12 signal_emit_unlocked_R
    at gsignal.c line 3635
  • #13 g_signal_emit_valist
    at gsignal.c line 3391
  • #14 g_signal_emit_by_name
    at gsignal.c line 3487
  • #15 meta_monitor_manager_rebuild_derived
    at backends/meta-monitor-manager.c line 1418
  • #16 meta_monitor_manager_xrandr_handle_xevent
    at backends/x11/meta-monitor-manager-xrandr.c line 1508
  • #17 handle_host_xevent
    at backends/x11/meta-backend-x11.c line 331
  • #18 x_event_source_dispatch
    at backends/x11/meta-backend-x11.c line 391
  • #19 g_main_dispatch
    at gmain.c line 3201
  • #20 g_main_context_dispatch
    at gmain.c line 3854
  • #21 g_main_context_iterate
    at gmain.c line 3927
  • #22 g_main_loop_run
    at gmain.c line 4123
  • #23 meta_run
    at core/main.c line 572
  • #24 main
    at main.c line 471

Comment 1 Florian Müllner 2016-09-10 21:03:10 UTC
Do you have multiple monitors, or are you disconnecting the only connected monitor?
Comment 2 Hussam Al-Tayeb 2016-09-10 21:15:20 UTC
(In reply to Florian Müllner from comment #1)
> Do you have multiple monitors, or are you disconnecting the only connected
> monitor?

I was disconnecting the only connected monitor.
Comment 3 Florian Müllner 2016-09-10 21:43:47 UTC
OK, then this is a known issue - we currently don't support running with no monitors connected. You'll get different backtraces depending on which version you use, whether you start with no monitors or disconnect it later, or whether there are open windows at the time or not, but it all boils down to that underlying issue. It's tracked in bug 730551, though I'm afraid the bug has been stalling for quite some time :-(

*** This bug has been marked as a duplicate of bug 730551 ***