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 578917 - Apps that fail to launch trough a .desktop file (due to a missing lib for ex) just fail silently
Apps that fail to launch trough a .desktop file (due to a missing lib for ex)...
Status: RESOLVED DUPLICATE of bug 144961
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks: 578943
 
 
Reported: 2009-04-14 10:19 UTC by Simon Strandman
Modified: 2009-04-14 16:39 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Simon Strandman 2009-04-14 10:19:27 UTC
If you install an app that's missing some lib, segmentation faults, clashes with SELinux etc. and launch it from the desktop or panel the app will just silently fail. You wont know if it's just taking long to start or if it has crashed and for what reason. To actually see that you have to launch the app from a terminal and look at the output.

I think gnome should display an error message when an app fails to launch with the output from the app. Something like:

"Application X failed to launch. This is the output from the application:

/usr/bin/someapp: error while loading shared libraries: somelib.so.4: cannot open shared object file: No such file or directory"

The output might be confusing for a novice user so perhaps it could be hidden behind a button "Click here for more information" or something, but the important thing is that an error message is displayed so that the app isn't just silently failing leaving the user to wonder what has happened.
Comment 1 Federico Mena Quintero 2009-04-14 16:11:14 UTC
It would be a good idea to set a watch for the child process, save its stdout/stderr, and present that output if the child exits with a non-zero status.
Comment 2 Vincent Untz 2009-04-14 16:39:39 UTC
This is bug 144961.

*** This bug has been marked as a duplicate of 144961 ***