-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Package: kildclient
Version: 3.0.0-1
Severity: important
Tags: upstream

Dear Maintainer,

On my machine, after a recent dist-upgrade (from a 2.x version),
KildClient no longer automatically scrolls the display buffer when new
text arrives, even when the buffer is scrolled as far down as I can get
it to go.

The documentation (/usr/share/doc/kildclient/html/x458.html) seems to
imply that when the buffer is scrolled all the way to the bottom,
new text arriving should cause it to scroll to remain at the
bottom.

I have tested enabling the "Scroll on output" option (under World ->
Edit... -> Miscellaneous), which is documented to cause scrolling
when new text arrives even when the buffer is not currently scrolled all
the way to the bottom. This has produced no visible change in behavior.

I have tested removing ~/.kildclient/ and starting with a clean profile.
The same behavior still occurs in that situation.

I have also tested on a second machine (my laptop), on which kildclient
had never previously been installed, and seen the same behavior.

All of this testing has been done with a connection to a single private
MUSH, for which I am probably not authorized to hand out connection
information. I have not tried connecting to any other MU* for
comparison, in part because I do not know and would prefer not to have
to bother to learn the protocols and etiquette of any others. However,
since scrollback worked just fine on this MUSH with KildClient 2.x and
since other people (at least one of whom also uses KildClient) are able
to use it with no problems, I doubt that the problem is MUSH-specific.


I have tagged this as important, since autoscroll is an effectively
essential feature for a MU*, and trying to use one without it is painful
to say the least. If the behavior turns out to be specific to me for
whatever reason (i.e., other people see autoscroll in 3.0.0 just fine),
then it would probably be appropriate to downgrade it to normal.

I have also tagged this as upstream, since I don't see any plausible way
this could possibly be caused by packaging or by the interaction between
packages. There is always the possibility that I'm wrong in that
assessment, however.

(In the absence of autoscroll, I would prefer to downgrade to 2.x until
some resolution can be found. However, 2.x depends on libperl5.14, which
depends on a matching version of perl-base, which cannot now be
installed without (removing testing from my sources.list and)
downgrading a large swath of my system. As such, until such time as a
fix for this can be found, my only possible solution for avoiding the
problem would seem to be building KildClient 2.x from source myself. Any
suggestions for alternate workarounds would be appreciated.)


- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kildclient depends on:
ii  libc6                   2.19-13
ii  libglib2.0-0            2.42.0-2
ii  libgnutls-deb0-28       3.3.8-5
ii  libgtk-3-0              3.14.4-2
ii  libgtkspell3-3-0        3.0.6-1
ii  libjson-perl            2.61-1
ii  liblocale-gettext-perl  1.05-8+b1
ii  libpango-1.0-0          1.36.8-2
ii  libperl5.20             5.20.1-3
ii  zlib1g                  1:1.2.8.dfsg-2+b1

kildclient recommends no packages.

Versions of packages kildclient suggests:
ii  kildclient-doc  3.0.0-1
pn  libgtk3-perl    <none>

- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJUgS03AAoJEASpNY00KDJr97YQAK3EzRNZiP8AI38CIVbSamsm
7EFdtakM6PLw4yB6T/C+I6aMj0MdJhbz+eoJVUFJT8k9SJJDCet2e6aoReMfIMyQ
H5n4RVI8vOE1A/L8Y6cLzesrIjXJEeCBNqqAf/+VEmoyQzyfrkDLlSOT9ctyPw/o
vSMHFpfVRkclYMtCoR5tfDc1WJGCpk5K2f5VunJ5nMVpPvcLOYtrpov7EdJBXPJL
18YjTJpJsfprhnKu2EUNy7OWzDGb1zoXahocRnWPZQ7O1lTFOuiQCOJJUozP7OWk
BqgxnCjybf1Zk1l7sDs4LwVyfsE7v3o+wDL1OU/GWiaY/jQ1JTxAt91NwKgQ1H+n
EIc84A6vPiGnJPZ/rK7+f3++ImkoHhX6pEyHtgUN5w3cpCoN91iT/jPQAhGPWhyl
LusbtvCDVLG3nfrFvvptt4VvwJZPKzOpxLwX1k+6vYclbfW/ti8MuoOaPenA/QiH
aK8Oa5JOSZd/3jK1/sFTYzFy3QdBkHRI+Y5v2e34OTmbyAzQi7/YZ6FpTFTVUsin
m08wSn3YWRi/Ka5L/MSYpc8+ZndeJZQrj4UODQqJoL20V21loIDoCyUGzCAUo2ky
EV5tMV6xzy4QW0zEl/ge7Q3BbhS79MAJ/fbLL9Jh5VTtrWU5dK7stzZIES2szhNv
gbQ8ZY3wLOgvLtYgsnBU
=0IBm
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to