I'm also affected by this same bug mentioned by ekso in unreal with
rider using other distributions that are based off of ubuntu, like for
example pop-os (with gnome-shell installed, not the cosmic DE).
I've created a forum post on the epicgames community forum about this issue as
well here:
I also have this problem when hitting a breakpoint in Unreal 5.1 from
JetBrains Rider 2022.3.1 while in vanilla Ubuntu 22.04. When the window
shows it actually makes the mouse pointer disappear and I have to rely
on the keyboard to "Force Quit" to get the pointer back.
The "Disable Force Quit or
Forgive me if I missed something in reading but is there a link to a bug
on the Gnome side? This seems absolutely _constant_ in 22.04, and
interrupts many games and programs. It seems like a really bad idea
given that many programmers are relying on async tasks/callbacks/etc.
these days. Impetus
** Changed in: gnome-shell (Ubuntu)
Status: Expired => Confirmed
** Tags added: kinetic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not
I'm experiencing this issue in ubuntu 22.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in gdb
To manage
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I would also like to know if this is fixed in 20.04. I would want to upgrade if
so.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not
Is this still an issue in Ubuntu 20.04?
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Tags removed: disco
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in gdb
To manage notifications about this bug
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in gdb
To manage notifications about this bug go
I am also affected in Ubuntu 19.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in gdb
To manage notifications
I am also affected by this bug, currently using Ubuntu 19.10, and
previously I had 19.04, both have the issue. It is really annoying
because the window system becomes temporarily completely unresponsive
and I am not even able to click on anything.
--
You received this bug notification because
No, the kernel sets it when a program being debugged is stopped in the
debugger. If you see "S (sleeping)" then that implies you haven't yet
stopped the program being debugged.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
OK, Daniel, thank You, now it clear. I've found this file.
State: S (sleeping)
So the appearing of popup message is correct, because not correct state of
process. What process must set this state for debugging application? Same
debugger?
--
You received this bug notification because you are
It is in the file /proc/PID/status or /proc/PID/stat for each PID.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in
Hello, Daniel. Please tell me where (how) I can see this state. I've
looking for this in gnome-system-monitor, the state of debugging
application is "Waiting". I've looking foe this in "top" - column "S" is
"S" value, not "t".
--
You received this bug notification because you are a member of
I think this is fixable per comment #4.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in gdb
To manage
Hello to all. Ubuntu 18.04.2 LTS. Eclipse based application. Upgrading
gnome-shell up to 3.28.4 was useless. The annoying popup message during
debugging application is still appearing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Bug #1740869 was another issue and about the fact that the dialog would
lead input to stop working, the bug here is about the fact that those
dialogs are an annoyance and should be avoided for debuggers
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in:
The same problem.
Ubuntu 18.04
QT Creator (gdb 8.2)
gnome-shell 3.28.4
Repeatedly warning "MyApp is not responding" under debugging
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I think gnome-shell could do better at ignoring programs being debugged.
It appears you can detect this by looking at the process state like in
/proc/PID/status. It will show:
State: t (tracing stop)
Or easier to parse: Look at /proc/PID/stat and the third field will be a
lowercase 't'.
This
Hi Marco,
No, the warning/dialog shows repeatedly.
I think if I'm debugging a program, ubuntu and gnome-shell should never
tell me the window is not responding. I might focus the window to use
it, or to set it above all others so I can watch it.
Thanks
--
You received this bug notification
Mh, if the warning is just showing once and when you unfocus such dialog
you don't get any problem, I don't think this is an issue.
Maybe the fix would be to delay the presentation of such dialog until
the hanging window is focused?
--
You received this bug notification because you are a member
** Description changed:
- I believe this is a regression for
- #1740869 is not responding window is constantly showing when
debugging a program
+ I believe this is a regression for bug 1740869:
+ is not responding window is constantly showing when debugging a
program
I'm
24 matches
Mail list logo
