<something> is not responding window is constantly showing when debugging a program

Bug #1740869 reported by Vaclav Cermak on 2018-01-02
This bug affects 24 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Marco Trevisan (Treviño)
Marco Trevisan (Treviño)
Marco Trevisan (Treviño)

Bug Description

Mentioned window about no responding program is showing and stealing focus when I try to debug a Java program in Eclipse. When I click on Wait, it disappears for a moment and opens again.

This renders Ubuntu 17.10 with Gnome 3 nearly useless for program debugging.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: mutter 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 2 14:22:56 2018
InstallationDate: Installed on 2017-12-04 (28 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Vaclav Cermak (disnel) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in mutter (Ubuntu):
status: New → Confirmed
Alessandro Muntoni (alemuntoni) wrote :

It also affects me when I'm debugging with QtCreator using Ubuntu 18.04, this is very annoying.
When the window appears, it is not possible to click anywhere except that window (also if it is in background), and it is not possible to disable or increase the timer for non responding applications, as pointed here: https://askubuntu.com/questions/412917/how-to-increase-waiting-time-for-non-responding-programs

marun_cz (marun1) wrote :

same problem here Ubuntu 18.04 QtCreator 4.6.1

it looks like it steals mouse clicks, because keyboard still works

marun_cz (marun1) wrote :

same problem here
ubuntu 18.04 qtcreator 4.6.1
it looks like it steals mouse clicks because keyboard shortcuts still work

gnome on wayland works fine, that 'not responding" window is still there but i can use qtcreator just fine

Phil Wolff (adiabat) wrote :

It appears that the dialog is system-wide modal. Is that really necessary? If so, it should also appear on top of *every* window stack in the system, not just the stack containing the offender.

Bill Robinson (airbaggins) wrote :

I'm getting the same problem debugging Unity Editor. It is unusable. As I start going through breakpoints in Rider, I have to continually switch back to the Unity editor window to say keep waiting. Is there really no other workaround than to recompile the window manager?!

Joan (jmigual) wrote :

When working with Qt Creator 4.6.2 it happens too and it just makes debugging unusable.

Bill Robinson (airbaggins) wrote :

To update my own workaround, I have switched to LXDE for now (installed lubuntu-desktop). It's pretty drastic, but it completely sidesteps mutter.

Adam Divak (adam.divak) wrote :

The same bug affects me on Ubuntu 18.04 LTS when debugging C++ applications using CLion. The fact that the popup can remain hidden in the background but it blocks mouse clicks against all applications (including the foreground ones) is a huge issue, and there is no known workaround for the problem. How do core devs use their own system for application development?

Strangely the timeout between two popups is not constant, sometimes it happens every 5 seconds and sometimes the application being debugged can stay in the background for longer periods without causing this issue.

A similar issue has been reported against Fedora a long time ago and it did not get any attention there either: https://bugzilla.redhat.com/show_bug.cgi?id=981149

Please put this on high priority.

tags: added: bionic
Dmitry T. (over-9000) wrote :

Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority.

Eneko Castresana (ecv80) wrote :

Same case: 18.04 debugging Unity3D on VSCode. Really annoying, renders debugger almost useless. I suggest making at the very least PING_TIMEOUT_DELAY (as reported here: https://askubuntu.com/a/701991 ) user configurable through a text file, and preferably add the possibility of configuring it on a per-process name basis. We can't just be switching WM in order to debug. This is ridiculous.

Eneko Castresana (ecv80) on 2018-08-27
summary: - <something> is not respoding window is constantly showing when debugging
- a program in Eclipse
+ <something> is not responding window is constantly showing when
+ debugging a program in several IDEs
summary: <something> is not responding window is constantly showing when
- debugging a program in several IDEs
+ debugging a program
Jeromy Stroh (jeromyu) wrote :

Still running into this. It's impossible to debug. Ubuntu gdb debugging large application.

Marwen Azouzi (marwen-azouzi) wrote :

Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority.

ali ghazi (alighazi) wrote :

Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority.

karthikjain (karthikjain) wrote :

Same issue while debugging C++ application. Ubuntu 18.04.01 + gcc 8.2.0 + Qt creator 4.5.2.
Please increase the priority

Sebastien Bacher (seb128) wrote :

Would be worth reporting upstream on gitlab.gnome.org if that hasn't been done yet

Changed in mutter (Ubuntu):
importance: Undecided → High
tags: added: rls-bb-incoming rls-dd-incoming
Will Cooke (willcooke) wrote :

Marking as not fixing for release. That doesn't mean this won't be fixed, just that we won't block release on waiting for it to get fixed. This will be picked up in the 19.10 cycle for fixing.

tags: added: desktop-trello-import rls-dd-notfixing
removed: rls-dd-incoming
Changed in mutter (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Will Cooke (willcooke) on 2019-03-26
tags: added: rls-bb-notfixing
removed: rls-bb-incoming
Andrea Azzarone (azzar1) wrote :

This has already been fixed both in Disco and Cosmic. The commit to be SRUed in Bionic is this one: https://gitlab.gnome.org/GNOME/gnome-shell/commit/b3045cb964459d050c280a4a4958131cfa24ebfb

@3v1n0 Do you want to take care of it or should I do that?

affects: mutter (Ubuntu) → gnome-shell (Ubuntu)
tags: added: fixed-3.32 fixed-upstream

Andrea, if you want to prepare a merge proposal against bionic we can merge it in the VCS for now and then when I prepare the new SRU for bionic with other fixes land it... As you wish

Upstream fix was released in 3.30.1


Changed in gnome-shell (Ubuntu Bionic):
status: New → Triaged
Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
Changed in gnome-shell (Ubuntu Bionic):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
importance: Undecided → Medium
Changed in gnome-shell (Ubuntu Cosmic):
status: New → Fix Released
tags: removed: artful rls-dd-notfixing
Amr Ibrahim (amribrahim1987) wrote :

Three commits got backported upstream to gnome-shell-3.28 related to the close dialog, but after the git snapshot that is being SRUed now to Bionic. The fix to this bug is there.

Changed in gnome-shell (Ubuntu Bionic):
status: Triaged → In Progress

Hello Vaclav, or anyone else affected,

Accepted gnome-shell into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell/3.28.4-0ubuntu18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in gnome-shell (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Changed in gnome-shell (Ubuntu Cosmic):
importance: Undecided → High

$ apt-cache policy gnome-shell
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato: 3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100

I confirm the fix works.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1

gnome-shell (3.28.4-0ubuntu18.04.1) bionic; urgency=medium

  * New upstream stable release
    - Fix ellipsization in dialog subtitles/bodies (LP: #1809788)
    - dnd: Only handle touch events in wayland (LP: #1817020)
    - windowManager: listen actively to windows being destroyed during WS switch
      (LP: #1812527)
    - Fix unresponsive-app dialog blocking input in other windows (LP: #1740869)
    - Fix regression on missing spread animation (LP: #1827284)
  * d/p/js-fix-invalid-access-errors.patch,
    - Refreshed
  * d/p/switchMonitor-switch-to-next-config-upon-initial-keypress.patch
    - Ensure switch display mode is cyclic (LP: #1772811)
  * debian/control:
    - Depends on mutter 3.28.4-0ubuntu18.04.1
  * d/p/st-widget-Add-missing-g_return_val_if_fail.patch:
    - st-widget: Protect from NULL obj in get_theme_node (LP: #1796606)

 -- Marco Trevisan (Treviño) <email address hidden> Fri, 10 May 2019 11:43:10 +0100

Changed in gnome-shell (Ubuntu Bionic):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Daniel van Vugt (vanvugt) wrote :

Now tracking in bug 1832426 :(

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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