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 91362 - Visual feedback needed for application launch
Visual feedback needed for application launch
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
2.11.x
Other other
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 312444 477898 578943 590292 660577 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-08-21 23:17 UTC by Matt Lavin
Modified: 2018-05-22 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Matt Lavin 2002-08-21 23:20:23 UTC
Package: nautilus
Severity: normal
Version: 2.0.4
Synopsis: No visible clue for failed application launch
Bugzilla-Product: nautilus
Bugzilla-Component: general

Description:
Description of Problem:
I tried to run an application from nautilus by double clicking on it and
nothing happened. It turns out that the application was missing a
library dependency but failed to start.  I didn't realize this untill I
went to a terminal window and launched the application by hand

Steps to reproduce the problem:
1. Find a program fails to launch ( like one that depends on gtk 1.2 and
don't have gtk 1.2 installed )
2. Try to launch the application through nautilus
3. Notice no clue about failure

Actual Results:
Nothing happens

Expected Results:
A dialog should appear telling me that the application failed to start
and give me some way to find the console output if there is any.

How often does this happen?
Every time




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-08-21 19:20 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2002-11-16 20:54:03 UTC
This is fairly easy to duplicate.  Here's what I did:
   1) ldd `where gnome-terminal` | grep "\(vte\|zvt\)"
   2) I got back libvte.so.2, so I ran
        locate libvte.so.2
   3) I saw /usr/lib/libvte.so.2.6.0 (which /usr/lib/libvte.so.2 was
      a symlink to).  So, as root, I ran
        chmod go-rx /usr/lib/libvte.so.2
   4) In nautilus, go to the directory where gnome-terminal is
      located and double click on it.

It silently fails.  Trying to run gnome-terminal from a terminal that
was already up before the permissions where changed on libvte produces
the following error:
  gnome-terminal: error while loading shared libraries: libvte.so.2: 
  cannot open shared object file: Permission denied

I'm using Redhat 8.0, which has nautilus v2.0.6 (I can also duplicate
this under Mandrake 9.0 although it's a libzvt that I have to remove
permissions from).  I disagree with enhancement level of severity, so
I'm marking it up.  Also, I'm setting GNOMEVER2.0 keyword and marking
as new.

I think this is probably an easy-fix, so that keyword might be able to
be added as well?
Comment 2 Luis Villa 2002-11-19 16:50:20 UTC
This is one of those ones that is borderline enhancement/serious
problem. 'major' is certainly reasonable; leaving it that way.
Comment 3 Christian Kellner 2003-03-27 16:38:10 UTC
This bug seems to be still valid in nautilus 2.2.2.
I am changing the GNOMEVER keyword to "GNOMEVER2.2".
Comment 4 Sebastien Bacher 2005-01-22 22:10:52 UTC
still an issue with nautilus 2.9.2
Comment 5 Sebastien Bacher 2005-08-03 09:44:37 UTC
*** Bug 312444 has been marked as a duplicate of this bug. ***
Comment 6 Cosimo Cecchi 2008-03-23 15:12:12 UTC
*** Bug 477898 has been marked as a duplicate of this bug. ***
Comment 7 Marcus Carlson 2010-07-07 06:14:33 UTC
Looks like Bug 578943 is a dup of this.
Comment 8 Cosimo Cecchi 2010-07-07 12:53:20 UTC
*** Bug 578943 has been marked as a duplicate of this bug. ***
Comment 9 Marcus Carlson 2010-07-09 19:32:57 UTC
From doc of g_app_info_launch_uris () [1] that nautilus is using to start applications:

"Note that even if the launch is successful the application launched can fail to start if it runs into problems during startup. There is no way to detect this. "

Cosimoc, should we still see this as a nautilus bug? 

Also, doesn't nautilus handles the control of the started application to gnome-session so even if nautilus would die, the started applications aren't killed? If so I'll suggest that gnome-session should handle all types of application failures as well.

[1] http://library.gnome.org/devel/gio/stable/GAppInfo.html#g-app-info-launch-uris
Comment 10 Stefano Teso 2011-02-23 15:23:06 UTC
*** Bug 590292 has been marked as a duplicate of this bug. ***
Comment 11 William Jon McCann 2012-08-24 21:04:49 UTC
*** Bug 660577 has been marked as a duplicate of this bug. ***
Comment 12 sajolida 2018-03-08 09:10:24 UTC
A variant of this issue is frequently experienced by users of Tails (https://tails.boum.org/). When a user clicks on a desktop launcher, it might take several seconds until the application is actually open (let's say Tor Browser). During these few seconds there is no visual feedback whatsoever that the desktop launcher was actually clicked.

https://tails.boum.org/install/inc/screenshots/desktop.png

Unexperienced users, like journalists using Tails only from time to time, often click again several times on the desktop launcher after nothing happens the first time leading to several instances of Tor Browser being launched.

Bug #477898 has been marked as a duplicate of this one while I think they are orthogonal:

- #477898 is about providing immediate visual feedback even when everything goes well (for example changing the cursor into a spinner), which is the problem we have in Tails.
- While #91362 is about being more helpful when something goes wrong (for example providing an error message if the launch fails).

There is no visual feedback when clicking on desktop launchers but also when starting an application from the Applications menu or from the activities overview. So I think that this bug is not specific to Nautilus and should maybe reported to another component. I looked for a similar bug on GNOME Shell but couldn't find any.

Should I report it there as well?

Should we reassign this bug to GNOME Shell?

I'm too new to bugzilla to be sure about what to do :)
Comment 13 sajolida 2018-05-05 16:01:22 UTC
While doing some user testing for Tails this week, I repeatedly saw people hitting this bug (4 participants out of 5). 3 of them had GNOME on their regular operating system.

My conclusion is that this issue does not only affect people who are new to GNOME but long-term users as well.
Comment 14 Carlos Soriano 2018-05-05 16:16:32 UTC
This is something interesting and that we probably want, but this is up to the window manager. See Endless OS for an implementation of it.
Comment 15 Carlos Soriano 2018-05-05 16:17:15 UTC
in case is wanted, it must be filed against mutter or gnome-shell in GitLab. Closing here.
Comment 16 sajolida 2018-05-22 10:51:32 UTC
Thanks for the guidance Carlos!

See you on https://gitlab.gnome.org/GNOME/mutter/issues/166.