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

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

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

Hi
same problem here Ubuntu 18.04 QtCreator 4.6.1

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

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

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.

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?!

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

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

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.

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

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.

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

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

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

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

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

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.

Added to Trello: https://trello.com/c/42jbJczE/286-bug1740869-something-is-not-responding-window-is-constantly-showing-when-debugging-a-program

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?

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

https://gitlab.gnome.org/GNOME/gnome-shell/issues/273

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.
https://gitlab.gnome.org/GNOME/gnome-shell/commits/gnome-3-28

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.

$ apt-cache policy gnome-shell
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.

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,
    d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.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

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.

Now tracking in bug 1832426 :(

I am very grateful to whoever fixed this. Thank you. Really appreciated. 👍