vte @0.27.90: Cmd key is not recognized as Meta in gnome-terminal

[cubranic@…]

After upgrading gnome-terminal to 2.30.2_1, Cmd key does not act as Meta any more.

[cubranic@…]

My X11 keymap modifiers, unchanged from before the upgrade of terminal:

$ xmodmap -pm 
xmodmap:  up to 2 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x40),  Shift_R (0x44)
lock        Caps_Lock (0x41)
control     Control_L (0x43),  Control_R (0x46)
mod1        Alt_L (0x3f),  Alt_R (0x47)
mod2      
mod3      
mod4        Super_L (0x42),  Super_R (0x45)
mod5      

I cleaned the old version by mistake before trying out the new one, so I'm not sure what was the latest version of gnome-terminal that worked. But it was fairly recent, most likely not more than 4 weeks old.

[jmroot (Joshua Root)]

Please remember to cc the maintainer. Note that the last time gnome-terminal had its revision increased was 5 months ago in r72654, and that didn't really change anything; the last significant update was 7 months ago in r71559.

[cubranic@…]

I'm sorry, I mixed up the ports. It was a vte update that caused the problem with gnome-terminal. After reverting to vte @0.25.1_3+universal, Cmd is recognized as Meta, but with the most recent version that I had, vte @0.27.90_0+python26+universal, it is not.

[cubranic@…]

The problem is still present with vte @0.28+python26+universal.

[cubranic@…]

Replying to cubranic@…:

After upgrading gnome-terminal to 2.30.2_1, Cmd key does not act as Meta any more.

Despite being a reporter, I can't seem to be able to change the ticket's port, summary, or description. This is a more appropriate info:

port: vte
summary: Alt is not recognized as Meta
description: I have remapped Cmd to act as Alt (mod1), and Option to be Super (mod4). With vte post-@0.25.1_3, including the most current one (@0.28.0_0), gnome-terminal does not treat key combinations with Cmd as Meta.

[cubranic@…]

Seems to be Gnome bug(s): ​https://bugzilla.gnome.org/show_bug.cgi?id=601926 and ​https://bugzilla.gnome.org/show_bug.cgi?id=628545.

Also in Ubuntu, which solved it by backing out the problematic change to vte: ​https://bugs.launchpad.net/ubuntu/+source/vte/+bug/619754

[cubranic@…]

I tried modifying my xmodmap file to assign Meta to Cmd, on both mod1 and mod2, and none of the mappings were recognized with vte @0.28.0_0.

[cubranic@…]

Still a problem with vte @0.28.2_0

[jmroot (Joshua Root)]

Is this still a problem with the current version? I see the previously linked upstream bugs are marked as fixed.

[dbevans (David B. Evans)]

Replying to jmr@…:

Is this still a problem with the current version? I see the previously linked upstream bugs are marked as fixed.

Yes, I believe the related upstream bugs have been fixed but I'm unable to confirm that in practice for gnome-terminal because that port has been broken for some time on MacPorts and I have yet to be able to track down the root cause. I think I need someone with fresh eyes to take a look at this. See ​#46800.

However, since this is reputed to have been a vte issue, if I can verify it's fixed using the vte demonstration app, I'll go ahead and close this ticket.

Thanks for reminding me about this old issue.

[mascguy (Christopher Nielsen)]

Replying to dbevans:

Replying to jmr@…:

Is this still a problem with the current version? I see the previously linked upstream bugs are marked as fixed.

Yes, I believe the related upstream bugs have been fixed but I'm unable to confirm that in practice for gnome-terminal because that port has been broken for some time on MacPorts and I have yet to be able to track down the root cause. I think I need someone with fresh eyes to take a look at this. See ​#46800.

However, since this is reputed to have been a vte issue, if I can verify it's fixed using the vte demonstration app, I'll go ahead and close this ticket.

Appears to have been resolved long ago, but simply not closed.