GNOME Bugzilla – Bug 335262
panel doesn't detect failure to start
Last modified: 2006-03-20 20:30:42 UTC
Please describe the problem: 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. For instance, create a panel launcher for "/bin/false", and click on it. You'd expect to get some error along the lines of "the application failed to run" or something (since it returned a non-0 exit status), but it doesn't. In one case, aisleriot was exiting with an error, but the panel made it seem like it was just being really really really slow to launch. Steps to reproduce: 1. create a panel launcher for "/bin/false" 2. double-click it Actual results: Silence Expected results: An error indicating that the "app" had immediately closed with non-zero exit value. Does this happen every time? Oh, yes. Other information:
A bit related to bug 144961. So, you're example is not really good since running /bin/false actually works. And I don't believe that all programs returning a non-zero value do this because of errors...
In fact, the downstream bug Mark copied this from was basically exactly 144961. ("Make a launcher to /bin/false" was just something I suggested as an easy way to reproduce it without needing to have an app with broken rpath/ldconfig info.) *** This bug has been marked as a duplicate of 144961 ***