Bug#1061831: restricted tab completion broken for directory names with blanks

2024-01-29 Thread Michael Kiermaier

Package: bash-completion
Version: 1:2.11-6

I'm in bash. In the current directory there is a subdirectory named
dir\ blank
Now I type
$ unzip dir\ bla
and then I press the tab key twice for autocomplete. But the completion
doesn't work.

Notes:
* The completion does not work no matter if there is a zip file in
  dir\ blank or not.
* When I do the same for 'ls' instead of 'unzip', completion works.
* The problem is not specific for the unzip command. My impression is
  that any command with a restricted list of completions produces this
  bug, like okular, xdvi etc.
* Autocomplete works as long as the entered part does not contain the
  blank. For example, tab-completion at
  $ unzip dir
  works, but at
  $ unzip dir\
  it does not.

A variant of this bug has been discussed here:
https://lists.debian.org/debian-user/2024/01/msg01380.html

The above has been produced in konsole in KDE, but I don't think it is
relevant.

I'm on Debian 12 (stable) amd64.

Package versions:

konsole  4:22.12.3-1
bash  5.2.15-2+b2
bash-completion   1:2.11-6

$ uname -a
Linux goblin 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1
(2023-12-30) x86_64 GNU/Linux



Bug#1034261: autofs attempts communication with portmapper (port 111) even for NFS4 mounts

2023-05-16 Thread Michael Kiermaier

Many thanks for the fast response.

I just realized that I gave an incorrect link to the corresponding bug
report at Ubuntu. It should have been this one:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1970264

Best,

~Michael



Bug#1034261: autofs attempts communication with portmapper (port 111) even for NFS4 mounts

2023-05-16 Thread Michael Kiermaier

I consider this bug quite severe as it may break working setups after an
update.

The corresponding bug report for Ubuntu might be this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034261

It is the same bug reported on the autofs mailing list here:
https://www.spinics.net/lists/autofs/msg02389.html
Apparently, it has been introduced in the transition of autofs from
5.1.7 to 5.1.8.

A fix has been posted here:
https://www.spinics.net/lists/autofs/msg02391.html
and again
https://www.spinics.net/lists/autofs/msg02434.html