Description of problem: I think the problem occurred when I changed the monitor setting from 200% to 300%. Applications using GTK have stopped working. I used a script I found on the web to change the .config/monitors.xml But I'm not sure this bug is related ---------------------------- #!/usr/bin/python3 # https://dbus.freedesktop.org/doc/dbus-python/tutorial.html # https://github.com/GNOME/mutter/blob/b5f99bd12ebc483e682e39c8126a1b51772bc67d/data/dbus-interfaces/org.gnome.Mutter.DisplayConfig.xml # https://ask.fedoraproject.org/t/change-scaling-resolution-of-primary-monitor-from-bash-terminal/19892 import dbus bus = dbus.SessionBus() display_config_well_known_name = "org.gnome.Mutter.DisplayConfig" display_config_object_path = "/org/gnome/Mutter/DisplayConfig" display_config_proxy = bus.get_object(display_config_well_known_name, display_config_object_path) display_config_interface = dbus.Interface(display_config_proxy, dbus_interface=display_config_well_known_name) serial, physical_monitors, logical_monitors, properties = display_config_interface.GetCurrentState() updated_logical_monitors=[] for x, y, scale, transform, primary, linked_monitors_info, props in logical_monitors: if primary == 1: scale = 2.0 if (scale == 1.0) else 1.0 # toggle scaling between 1.0 and 2.0 for the primary monitor physical_monitors_config = [] for linked_monitor_connector, linked_monitor_vendor, linked_monitor_product, linked_monitor_serial in linked_monitors_info: for monitor_info, monitor_modes, monitor_properties in physical_monitors: monitor_connector, monitor_vendor, monitor_product, monitor_serial = monitor_info if linked_monitor_connector == monitor_connector: for mode_id, mode_width, mode_height, mode_refresh, mode_preferred_scale, mode_supported_scales, mode_properties in monitor_modes: if mode_properties.get("is-current", False): # ( mode_properties provides is-current, is-preferred, is-interlaced, and more) physical_monitors_config.append(dbus.Struct([monitor_connector, mode_id, {}])) if scale not in mode_supported_scales: print("Error: " + monitor_properties.get("display-name") + " doesn't support that scaling value! (" + str(scale) + ")") else: print("Setting scaling of: " + monitor_properties.get("display-name") + " to " + str(scale) + "!") updated_logical_monitor_struct = dbus.Struct([dbus.Int32(x), dbus.Int32(y), dbus.Double(scale), dbus.UInt32(transform), dbus.Boolean(primary), physical_monitors_config]) updated_logical_monitors.append(updated_logical_monitor_struct) properties_to_apply = { "layout_mode": properties.get("layout-mode")} method = 2 # 2 means show a prompt before applying settings; 1 means instantly apply settings without prompt display_config_interface.ApplyMonitorsConfig(dbus.UInt32(serial), dbus.UInt32(method), updated_logical_monitors, properties_to_apply) Version-Release number of selected component: gnome-shell-42.0-2.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: meta_window_update_for_monitors_changed dso_list: /usr/bin/gnome-shell gnome-shell-42.0-2.fc36.x86_64 (Fedora Project) 1649806737 executable: /usr/bin/gnome-shell journald_cursor: s=18cf4d651a464ab4845e278bfd45bfe2;i=1cf3e;b=e6e54cbb5daa46efb60c8e3dbffaaee5;m=e707489;t=5dca6137e849d;x=49d31d90ff112c34 kernel: 5.17.2-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1872760 [details] File: backtrace
Created attachment 1872761 [details] File: core_backtrace
Created attachment 1872762 [details] File: cpuinfo
Created attachment 1872763 [details] File: environ
Created attachment 1872764 [details] File: limits
Created attachment 1872765 [details] File: maps
Created attachment 1872766 [details] File: mountinfo
Created attachment 1872767 [details] File: open_fds
Created attachment 1872768 [details] File: proc_pid_status
Created attachment 1872769 [details] File: var_log_messages
Similar problem has been detected: Not sure what happened. Everything froze. I closed my laptop until it went to sleep. Opened it up. Switched to a TTY, then tried to switch back. Logged in, saw the crash report. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Nautilus-0.scope cmdline: /usr/bin/gnome-shell crash_function: meta_window_update_for_monitors_changed executable: /usr/bin/gnome-shell journald_cursor: s=550cc457842d4a58bedd3e0cb8a55326;i=1cd7aa;b=dd4fe3befc5544e9af511e44559fafb5;m=1534ffecd2;t=5dd0c8193893d;x=3f8ae9d48cb2a889 kernel: 5.17.3-300.fc36.x86_64 package: gnome-shell-42.0-2.fc36 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2095327 has been marked as a duplicate of this bug. ***
*** Bug 2098431 has been marked as a duplicate of this bug. ***
*** Bug 2105760 has been marked as a duplicate of this bug. ***
*** Bug 2106920 has been marked as a duplicate of this bug. ***
*** Bug 2108471 has been marked as a duplicate of this bug. ***
*** Bug 2114965 has been marked as a duplicate of this bug. ***
*** Bug 2112479 has been marked as a duplicate of this bug. ***
Managed to produce a test case and a fix for this issue, see the linked merge request.
*** Bug 2115260 has been marked as a duplicate of this bug. ***
*** Bug 2117281 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I logged in to the Gnome Desktop (standard Wayland) and it crashed a few seconds after loading the desktop. I had started to open some programs (Firefox, Slack) but unsure if those were a trigger. I then tried to login a second time and it crashed again. I had to reboot after which I could login without a crash. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: meta_window_update_for_monitors_changed dso_list: /usr/bin/gnome-shell gnome-shell-42.3.1-1.fc36.x86_64 (Fedora Project) 1657245305 executable: /usr/bin/gnome-shell journald_cursor: s=4846340df7434787b384184541722fbb;i=10f704;b=d41ae0e7dd4d449bbc0516440b7511f8;m=4b2edc7;t=5e5fea0b649f3;x=b62988a81a3b448b kernel: 5.18.16-200.fc36.x86_64 package: gnome-shell-42.3.1-1.fc36 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.