Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

Bug #1445543 reported by Daniel van Vugt
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GTK+
New
Undecided
Unassigned
Mir
Won't Fix
High
Unassigned
gtk+3.0 (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly.

Example:

$ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

Show the "Scores" - you can switch focus between this and the main window with Alt+` but doesn't respond to input.

Other dialogs (e.g. "About") work fine. From the Mir side there's no obvious difference between these windows.

In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input events being correctly received on the client side. That shows most of the Mir stack is working correctly.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It's possible this is not an input or focus issue at all. It's possible GTK is failing to notify Mir of some window redraws in multi-window apps so some windows (sometimes) appear to freeze.

summary: - GTK apps on Mir: Input focus is unreliable and sporadic. Background
- windows ignore input and/or focus switches apparently randomly.
+ Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze
tags: added: gtk-mir
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gtk+3.0 (Ubuntu):
status: New → Confirmed
Changed in mir:
importance: Undecided → High
Changed in gtk+3.0 (Ubuntu):
importance: Undecided → High
Changed in mir:
status: New → In Progress
assignee: nobody → Alan Griffiths (alan-griffiths)
status: In Progress → New
assignee: Alan Griffiths (alan-griffiths) → nobody
description: updated
William Hua (attente)
Changed in gtk+3.0 (Ubuntu):
assignee: nobody → William Hua (attente)
Revision history for this message
Emanuele Antonio Faraone (emanueleant03) wrote :

+1

Revision history for this message
Will Cooke (willcooke) wrote : Automatically added comment
tags: added: desktop-trello-import
tags: removed: desktop-trello-import
Changed in gtk+3.0 (Ubuntu):
assignee: William Hua (attente) → Andreas Pokorny (andreas-pokorny)
status: Confirmed → In Progress
Changed in gtk:
assignee: nobody → Andreas Pokorny (andreas-pokorny)
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Seems to be working with gtk 3 on zesty - so not Mir.

Changed in mir:
status: New → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Incomplete. I can still reproduce a freeze using the instructions in the description but it also looks like those instructions are wrong. Because if you do the same in X you will fine the Scores dialog is modal and is meant to make the main window unresponsive to input.

That said, I also remember anpok saying he found and fixed a reason for bugs like this in GTK.

affects: gtk+3.0 (Ubuntu) → ubuntu
Changed in ubuntu:
status: In Progress → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

*you will find*

Revision history for this message
Andreas Pokorny (andreas-pokorny) wrote :
Changed in ubuntu:
status: Incomplete → Confirmed
Revision history for this message
Andreas Pokorny (andreas-pokorny) wrote :

Ok this needs clarification - the dialogs we are talking about are not frozen in the current state of gdkmir, but not behaving correctly - they should be modal but are not.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Does Mir have the required client API functions for those yet?

affects: ubuntu → gtk+3.0 (Ubuntu)
Changed in mir:
status: Invalid → Incomplete
Changed in mir:
status: Incomplete → Won't Fix
Changed in gtk+3.0 (Ubuntu):
status: Confirmed → Won't Fix
Changed in gtk:
assignee: Andreas Pokorny (andreas-pokorny) → nobody
Changed in gtk+3.0 (Ubuntu):
assignee: Andreas Pokorny (andreas-pokorny) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.