Package: lv
Version: 4.51-3
Followup-For: Bug #504768

Sorry if a previous garbage message is accepted: I tried to make reportbug
send an archived message in /tmp/, but that didn't worked as expected
(possibly because it was encoded in base64).

So, this bug seems to still be in Debian stable and probably is more
likely to happens when /etc/alternatives/pager is linked to /usr/bin/lv

What is very annoying and confusing, is that at first there is no clear
reason why the string "(END):" appears instead of the prompt line, and
that you also don't see what you are typing even if commands does work.

So almost all line start with this:

(END):

This prompt disappear once you kill the pager process (and then
everything seems to goes back to normal).

For example, killing sh (whose parent terminated and is now init) won't
change anything, same for sensible-pager, but "kill 21151" (the lv pager)
makes everything goes back to normal:

~> pstree -pl | fgrep sensible-pager
   |-sh(21149)---sensible-pager(21150)---pager(21151)


Note that the parent of process 21149 is now the process 1, which happens
in some situation when the calling app abnormaly terminated (ironically,
it my case it was querybts and then reportbug that crashed).

For clarity in reporducing it, here are my settings for the default pager:

~> update-alternatives --config pager                                           
                                                                                
 [5:42:05pm]
Il existe 6 choix pour l'alternative pager (qui fournit /usr/bin/pager).

  Sélection    Chemin          Priorité   État
------------------------------------------------------------
  0            /bin/less        77        mode automatique
  1            /bin/less        77        mode manuel
  2            /bin/more        50        mode manuel
* 3            /usr/bin/lv      55        mode manuel
  4            /usr/bin/most    60        mode manuel
  5            /usr/bin/pg      10        mode manuel
  6            /usr/bin/w3m     25        mode manuel


My understanding is that lv should have terminated on its own, and that
there is some signals that are not always properly handled by "pager"
(which really is /usr/bin/lv), as when it happens "pager" often start to
use almost all the CPU.

I can get the same behaviour from bash or tcsh, so at first I tough it
didn't matter at all, but when trying with dash as reported, the terminal
indeed get way more confused for some reason, and killing lv is not enough
and <CTRL-Q> is needed so as to be able to use the terminal again.


Have a nice day,

Simon Valiquette



-- System Information:
Debian Release: 9.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1), LANGUAGE=fr_CA 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lv depends on:
ii  libc6      2.24-11+deb9u3
ii  libtinfo5  6.0+20161126-1+deb9u2

Versions of packages lv recommends:
ii  bzip2     1.0.6-8.1
ii  xz-utils  5.2.2-1.2+b1

lv suggests no packages.

Reply via email to