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 388972 - When pressing enter quickly after pressing a shortcut, enter is not sent to the new dialog
When pressing enter quickly after pressing a shortcut, enter is not sent to t...
Status: RESOLVED OBSOLETE
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: Normal normal
: 1.4
Assigned To: GNOME Commander maintainer(s)
epiotr
Depends on:
Blocks:
 
 
Reported: 2006-12-23 17:03 UTC by rmails
Modified: 2018-08-03 17:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rmails 2006-12-23 17:03:09 UTC
Please describe the problem:
When pressing a shortcut. For example F5 for copying a file. And pressing enter without waiting for the copy-dialog to appear (I know what is written there...). The dialog never gets the Enter. But the Enter is executed on the active pane, resulting in opening the file, instead of starting the copy command.

Steps to reproduce:
1. Press F5
2. Quickly press enter
3. 


Actual results:
The file having the focus will be opened

Expected results:
The copy process should be started

Does this happen every time?
yes.

Other information:
Comment 1 dpc 2017-01-09 13:36:11 UTC
I have exactly the same problem which occurs after the application has been used a while. The focus on the dialog windows gets lost for copying files or connecting to ftp servers. This affects all users that use keyboard shortcuts extensively. The only way I found to workaround that problem is to restart gnome-commander.
Comment 2 GNOME Infrastructure Team 2018-08-03 17:51:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-commander/issues/6.