Bug 127317 – Shift-insert broken with release of x11-libs/vte 0.11.18

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Owen Berry 2006-03-23 08:08:18 UTC]

Shift-insert now pastes from the CLIPBOARD instead of pasting from PRIMARY. This affects gnome-terminal as well.

Steps to reproduce:

* Open a terminal in X (either vte or gnome-terminal)
* Type ls to get some text on the screen
* Use mouse to highlight some text
* Using keyoard type ctrl-shift-c to copy to CLIPBOARD
* Use mouse to highlight a different piece of text
* Verify that it's in PRIMARY by middle clicking. The second set of text should be pasted where the cursor is.
* On keyboard type shift-insert. You'll get the text from CLIPBOARD instead of PRIMARY.

The original (and standard) behavour was that ctrl-shift-v would paste from CLIPBOARD and shift-insert pastes from PRIMARY.

Version information:

x11-libs/vte-0.11.18                 use: -debug -static
x11-terms/gnome-terminal-2.12.0      use: -debug -doc +python

Everything else Gnome-wise is the stable version. And so is most of the system.

Looking at this, it looks like an upstream problem:
  https://launchpad.net/distros/ubuntu/+source/vte/+bug/31354

Let me know if I can provide any more information.

[Comment 1 Leonardo Boshell (RETIRED) 2006-03-30 17:06:38 UTC]

Seeing vte's ChangeLog, this seems to have been fixed for vte-0.11.19. Could you try with vte-0.11.20 that is in our tree (hardmasked)?

[Comment 2 Owen Berry 2006-03-31 07:42:16 UTC]

Do you mean 0.12.0? There is not 0.11.20 that I can see.

[Comment 3 Leonardo Boshell (RETIRED) 2006-03-31 17:42:18 UTC]

(In reply to comment #2)
> Do you mean 0.12.0? There is not 0.11.20 that I can see.
> 

Indeed, sorry for the confusion. vte-0.12.0 doesn't depend on any other hardmasked stuff so it should be reasonable simple to test it. Thanks.

[Comment 4 Owen Berry 2006-04-03 07:39:15 UTC]

> Indeed, sorry for the confusion. vte-0.12.0 doesn't depend on any other
> hardmasked stuff so it should be reasonable simple to test it. Thanks.

Yes, that is fixed in 0.12.0. It also fixed the problem in gnome-terminal without recompilation. Thanks!

[Comment 5 Owen Berry 2006-04-05 07:53:06 UTC]

Note that I just tried 0.11.18 and this bug is NOT fixed there.

[Comment 6 Gilles Dartiguelongue (RETIRED) 2006-06-15 08:39:04 UTC]

this should be consider solved for gnome 2.14 I think. If gnome 2.14 hits stable in the near future, I think it is not appropriate to patch 0.11.18. It would be one more patch that would need to be maintained for no good reason considering it is solved upstream.

[Comment 7 Mart Raudsepp 2006-10-11 20:42:25 UTC]

Considering this fixed upstream, as 0.12.2 is stable on major arches.