After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 144961 - Panel does not detect if application started from launcher quits unexpectedly.
Panel does not detect if application started from launcher quits unexpectedly.
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: panel
2.17.x
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 323715 335262 438070 578917 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-06-25 07:14 UTC by Sagar Rastogi
Modified: 2020-11-06 20:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
Test program (321 bytes, text/plain)
2005-01-03 18:48 UTC, Vincent Untz 		Details

Description Sagar Rastogi 2004-06-25 07:14:41 UTC 
Currently If you launch something from the panel but it exits with an error the
panel doesn't tell you this. In fact, it eventually gives you a watch cursor to
make you think it's still loading. 
      An example might be a binary with bad rpath/ldconfig information. If you
start it from the panel, the binary will immediately exit with an ld.so error.
There is no way the application could pop up an error message, because it exits
before any of the application's own code is run.
       We would not want the panel to wait on the exit status forever. It would
just be making sure that the app didn't exit "immediately".
Comment 1 Vincent Untz 2004-12-23 09:36:51 UTC 
Sorry for the spam. Confirming some bugs.
 Filter on "VINCENT CONFIRMS" to ignore.
Comment 2 Vincent Untz 2005-01-03 18:47:29 UTC 
I can't think of a good way to do this.

What's happening here is that we call execv() with the path to the executable in
a fork. execv() succeeds even if the path/ldconfig information is not correct.
So I'm not sure we're able to know that it doesn't work.

See the test I'm attaching, and run it with an executable that has such a
problem as parameter.
Comment 3 Vincent Untz 2005-01-03 18:48:19 UTC 
Created attachment 35397 [details]
Test program
Comment 4 Vincent Untz 2005-12-14 22:17:13 UTC 
*** Bug 323715 has been marked as a duplicate of this bug. ***
Comment 5 Sebastien Bacher 2005-12-14 23:26:28 UTC 
Marking the bug as NEW, the panel should notify the user if an application
startup is not correct (some extra keywords for next time :p)
Comment 6 Dan Winship 2006-03-20 20:30:42 UTC 
*** Bug 335262 has been marked as a duplicate of this bug. ***
Comment 7 Vincent Untz 2007-05-13 08:58:14 UTC 
*** Bug 438070 has been marked as a duplicate of this bug. ***
Comment 8 Vincent Untz 2009-04-14 16:39:39 UTC 
*** Bug 578917 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2020-11-06 20:24:18 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.