GNOME Bugzilla – Bug 761800
Startup focus with X
Last modified: 2016-03-04 20:06:28 UTC
I don't know if this pertains to bug 761227. Ever time gnome-terminal is started the session doesn't have focus to start typing. In order start typing one must click inside the terminal. Switching between applications and back to gnome terminal, the terminal doesn't have focus until clicking in the terminal. Clicking the Add Tab button will create another terminal and give that terminal session focus right away. Selecting first tab will also give the first terminal session focus. Running version 3.18.2-1 on X from Arch Linux and is occurring on all my computers.
Just did some more troubleshooting it works just fine if dconfig settings tab-policy is set to automatic but if the setting is change to always, then focus at startup does not work.
Yup, confirmed. Annoying as hell. The first window's terminal does not get the focus, or if a new window is opened by the global desktop-wide shortcut (Ctrl+Alt+T for me on Unity) then it does not get the focus either. New windows opened from within g-t (with Ctrl+Shift+N) do get the focus though - at least for me.
Not reproducible here on gnome-shell: the first window created gets focus to the VteTerminal just fine. I don't have global shortcuts, but if they don't work right, that's a bug in the WM not g-t.
Still reproducible on Xenial alpha, Unity. To make it clear: it's not that a global shortcut doesn't work, and it's not that the window is not focused. The window is focused as expected, but within that the terminal widget is not. Pressing Tab repairs it. I guess that the notebook label is the focused Gtk+ widget rather than vte. Recently we had that change that he tab bar can't be focused, I guess it's just that we still need another grab() call somewhere.
Just for reference: I was testing with 0.42/3.18, not git master. Bug 746665 was not yet fixed in that branch.
Can't reproduce with git master. I guess bug 746665's patch fixed this as well.
Marking as duplicate. Also, I've backported the fix to 3-18. *** This bug has been marked as a duplicate of bug 746665 ***