ubuntu / ubuntu/Tiling-Assistant

GNOME Shell crashes with "assertion failed: (logical_monitor)" when displays are off

Open
#416 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
1.3k
Forks
78
Avg merge
2m
Merged PRs (30d)
6

Description

Description

GNOME Shell crashes consistently when displays are turned off (DPMS off), causing the session to logout and return to the login screen.

Environment
  • GNOME Shell: 46.0
  • Tiling Assistant: v46 (Ubuntu package) and v48 (user-installed)
  • OS: Ubuntu 24.04
  • Kernel: 6.8.0-85-generic
  • GPU: NVIDIA (using proprietary drivers)
  • Display setup:
    • Primary: 3840x2160 (DP-0.8)
    • Secondary: 1440x2560 rotated right (DP-0.1.1)
Steps to Reproduce
  1. Have dual monitor setup with tiling-assistant enabled
  2. Turn off displays (DPMS) for several hours (e.g., overnight)
  3. System crashes and returns to login screen
Crash Pattern
  • Crashes occur consistently during periods when displays are off
  • Always occurs at similar times (between 02:00-05:00 and 15:00)
  • Has occurred 7 times in the past week
Error Details
libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
GNOME Shell crashed with signal 6

Stack trace (from user-installed v48):

#0 tilingWindowManager.js:138
#1 tilingWindowManager.js:1365
#2 tilingWindowManager.js:471

Stack trace (from Ubuntu v46):

#0 tilingWindowManager.js:99
#1 tilingWindowManager.js:1303
#2 tilingWindowManager.js:437
Related Issues

Possibly related to #323 and #406 regarding display state changes.

Additional Notes

The crash happens with both the user-installed version and the Ubuntu-packaged version, suggesting this is a core issue with how the extension handles monitor state changes when displays are powered off.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with tilingWindowManager.js at the reported stack-trace locations, including lines 138/1365/471 and 99/1303/437, and review related issues #323 and #406 for display-state changes. Reproduce the dual-monitor DPMS-off scenario and trace the path leading to the logical_monitor assertion; done means displays can remain off without GNOME Shell crashing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.