[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#909474: xterm: cannot copy to both CLIPBOARD and PRIMARY



Package: xterm
Version: 337-1
Severity: important
Tags: upstream

What passes as a “fix” for #901249 broke things in a different manner.
I’m filing as a new bug instead of reopening, though, because the
original report was “behaviour does not match documentation”, and this
one is “behaviour does not match expectation, documentation silent”.

Same scenario as in #901249.

I have two words on the command line, “foo” and “bar”.

I wish to have “foo” in CLIPBOARD and “bar” in PRIMARY.

I select “foo” with Shift. Now I can paste it with ^V in
a GUI application, but not with middle-click. Okaaay…

Then I select “bar” without Shift. I can paste it with
middle-click, but ^V does not paste “foo” any more.

Then I select “foo” with Shift again. Now middle-click
is dead again.

This is *not* why I have multiple clipboards in X11 and
go through pains of mapping them distinctly in xterm!


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages xterm depends on:
ii  libc6           2.27-6
ii  libfontconfig1  2.13.0-5
ii  libfreetype6    2.8.1-2
ii  libice6         2:1.0.9-2
ii  libtinfo6       6.1+20180714-1
ii  libutempter0    1.1.6-3
ii  libx11-6        2:1.6.6-1
ii  libxaw7         2:1.0.13-1+b2
ii  libxft2         2.3.2-2
ii  libxinerama1    2:1.1.4-1
ii  libxmu6         2:1.1.2-2
ii  libxpm4         1:3.5.12-1
ii  libxt6          1:1.1.5-1
ii  xbitmaps        1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+4

Versions of packages xterm suggests:
pn  xfonts-cyrillic  <none>

-- no debconf information

Reply to: