FS#55932 - [mutter] Crash trying to turn off monitor using xrandr
Attached to Project:
Arch Linux
Opened by Geronimo Bareiro (gerito) - Monday, 09 October 2017, 13:50 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 07 January 2020, 12:03 GMT
Opened by Geronimo Bareiro (gerito) - Monday, 09 October 2017, 13:50 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 07 January 2020, 12:03 GMT
|
Details
Description:
I have a dual monitor setup in my laptop with integrated graphic Intel HD. It supports the internal display (the laptop screen) eDP1, and two outputs HDMI1 and the vga DP1. When I try to turn off a monitor mutter crashes. Also working with multiple monitors seems to be a little unstable. For example windows go unresponsive (the program works fine, but the windows doesn't interact with keyboard mouse). Additional info: * mutter 3.26.1 * Maybe related I'm using lxde gtk+-3 as DE without openbox, instead I use mutter as my window manager lxdm-gtk3-0.5.3-4-x86_64.pkg.tar.xz lxhotkey-gtk3-0.1.0-1-x86_64.pkg.tar.xz lxinput-gtk3-0.3.5-1-x86_64.pkg.tar.xz lxmenu-data-0.1.5-1-any.pkg.tar.xz lxpanel-gtk3-0.9.3-1-x86_64.pkg.tar.xz lxrandr-gtk3-0.3.1-1-x86_64.pkg.tar.xz lxsession-gtk3-1:0.5.3-1-x86_64.pkg.tar.xz lxtask-gtk3-0.1.8-1-x86_64.pkg.tar.xz lxterminal-gtk3-0.3.0-2-x86_64.pkg.tar.xz Steps to reproduce: 1. Have a multiple monitor setup. 2. Deactivate one monitor when using mutter >= 3.26.1 ie: $ xrandr --output eDP1 --off --output HDMI1 --auto 3. Mutter crashes immediately Mutter seems to work fine in version 3.24.4-1 |
This task depends upon
Also, backtraces would be nice.
I want to clarify that "Unresponsive windows" seem to be windows that went out of "focus", and that I cannot select (or interact) no matter what.
Edit: Also I discovered that moving windows from one Virtual Desktop (I don't know the proper term in English, in Spanish it is called Area de Trabajo/Working Area) to other also make windows go unresponsive.
Mutter 3.24 works fine.
gdb backtrace (3.26.1+7+g41f7a5fdf-1)
(gdb)
#0 0x00007ffff7ac6330 in meta_monitor_mode_get_resolution () at /usr/lib/libmutter-1.so.0
#1 0x00007ffff7ac63bb in meta_monitor_calculate_mode_scale () at /usr/lib/libmutter-1.so.0
#2 0x00007ffff7ac9405 in meta_monitor_manager_update_logical_state_derived () at /usr/lib/libmutter-1.so.0
#3 0x00007ffff7ac94d0 in meta_monitor_manager_rebuild_derived () at /usr/lib/libmutter-1.so.0
#4 0x00007ffff7ad6680 in meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/libmutter-1.so.0
#5 0x00007ffff7acf267 in () at /usr/lib/libmutter-1.so.0
#6 0x00007ffff77b0270 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#7 0x00007ffff77b1f69 in () at /usr/lib/libglib-2.0.so.0
#8 0x00007ffff77b2f42 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#9 0x00007ffff7afdb00 in meta_run () at /usr/lib/libmutter-1.so.0
#10 0x0000555555554acd in ()
#11 0x00007ffff7190f6a in __libc_start_main () at /usr/lib/libc.so.6
#12 0x0000555555554b3a in ()
(gdb)
There's a patch to fix this crash, but it's not complete as the review says (attachment 359500).