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 599680 - Shortcuts often don't work for the first time
Shortcuts often don't work for the first time
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 137455 606619 623249 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-26 17:31 UTC by Kamil Páral
Modified: 2010-07-29 07:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (format-patch output) (866 bytes, patch)
2010-06-08 14:24 UTC, Thomas Karpiniec
committed Details | Review

Description Kamil Páral 2009-10-26 17:31:53 UTC
Many shortcuts don't work for the first time. For example I have bound "display home folder" on Win+S combination. After I log in, it almost every time doesn't work the first time I press the combination. Nothing happens. When I press it again, Nautilus window pops up. But this happens not only after log in, but also after some time - I really don't know how long, it can be 30 minutes, maybe more. Then it again doesn't work for the first press, works on the second press. 

Similarly (and more substantially) this also happens for clipboard shortcuts. I'm going quite mad that Ctrl+c/Ctrl+x doesn't work so often. I experience it at least several times a day (all in one session), maybe even several times an hour(!). Ctrl+c just does nothing, only after second (or third) press is the file finally copied to clipboard (which you can determine by looking at the Nautilus status bar).

I see these symptoms on both Ubuntu 9.04 and Fedora 11, it is not distro-specific. Also I can vouch for not having broken keyboard, because I see this on several different hardware setups.

Annoying is that it is very hard to reproduce. It just works most of the time, but when you are not trying it for a long enough, then it just doesn't work for *once* and works again. This issue is one of the most pains I currently notice in Gnome.
Comment 1 Sense Hofstede 2009-12-15 19:54:49 UTC
The same bug has been reported at Launchpad in Ubuntu at <https://launchpad.net/bugs/390662>. It is indeed a very irritating bug.

(I personally can confirm this as well.)
Comment 2 Thomas Karpiniec 2010-06-08 14:24:20 UTC
Created attachment 163064 [details] [review]
patch (format-patch output)
Comment 3 Allan Day 2010-06-22 12:55:28 UTC
Confirming. It would be useful to have a description of which shortcuts this affects and which it doesn't.
Comment 4 Sense Hofstede 2010-06-23 12:44:39 UTC
At least 'Del', 'Ctrl+C', 'Ctrl+X' and I believe 'Ctrl+V' as well are affected.

I guess all short cuts related to operations on selected files don't work, but someone should test that.
Comment 5 Sandro Mani 2010-06-23 18:22:38 UTC
From what I can see, all file manipulation related shortcuts: CTRL+{C,X,V}, F2, Delete. Browsing keys work (arrows, enter, space).
Comment 6 Thomas Karpiniec 2010-06-26 09:40:04 UTC
The affected shortcuts are any which only become available after a file has been selected. This of course includes the clipboard actions C-x C-c C-v, rename F2, delete DEL, make link C-m, open C-o, and perhaps others.

The reason for the wide range of affected shortcuts is that there is a delayed call to real_update_menus(), as I described in more detail on the mailing list: <http://mail.gnome.org/archives/nautilus-list/2010-June/msg00023.html>.
Comment 7 Cosimo Cecchi 2010-07-04 13:16:32 UTC
*** Bug 606619 has been marked as a duplicate of this bug. ***
Comment 8 Cosimo Cecchi 2010-07-04 13:18:02 UTC
The patch seems to be right and works fine; I applied it to master.
Comment 9 Marcus Carlson 2010-07-28 21:03:08 UTC
*** Bug 137455 has been marked as a duplicate of this bug. ***
Comment 10 Marcus Carlson 2010-07-29 07:28:17 UTC
*** Bug 623249 has been marked as a duplicate of this bug. ***