Thank you so much for taking the time to investigate this old issue. The machine where I encountered this problem now runs Jessie. I've tried to reproduce it there and found that the directory was correctly created with world-readable permissions, despite the more restrictive global umask. So the issue seems to be resolved on Jessie.
Cheers! Philippe On Fri, 9 Nov 2018 at 11:25, Gabriel F. T. Gomes <[email protected]> wrote: > Control: tags -1 = unreproducible > > I could not reproduce this bug. Here's what I did to try: > > I edited /etc/login.defs, setting UMASK to 0027, then rebooted. Even > after reboot, when I run the command `umask', I get 0022. To work > around it, I manually set umask to 0027. > > # umask > 0022 > # umask 0027 > # umask > 0027 > > Afterwards, with bash-completion purged/uninstalled, I checked what > were the permissions of the relevant files and directories: > > # ls -lha /usr/share/bash-completion/ > total 88K > drwxr-xr-x 3 root root 4.0K Nov 8 23:34 . > drwxr-xr-x 301 root root 12K Nov 9 08:01 .. > drwxr-xr-x 2 root root 68K Nov 8 23:56 completions > > Notice that, even with bash-completion purged, the directory for > completions (/usr/share/bash-completion/completions) is present. > That's because other packages install their own completion files, as > can be seen in the following output: > > # dpkg --search /usr/share/bash-completion/completions/* | head > adb: /usr/share/bash-completion/completions/adb > util-linux: /usr/share/bash-completion/completions/addpart > apt: /usr/share/bash-completion/completions/apt > util-linux: /usr/share/bash-completion/completions/blkdiscard > util-linux: /usr/share/bash-completion/completions/blkid > util-linux: /usr/share/bash-completion/completions/blkzone > util-linux: /usr/share/bash-completion/completions/blockdev > systemd: /usr/share/bash-completion/completions/bootctl > btrfs-progs: /usr/share/bash-completion/completions/btrfs > devscripts: /usr/share/bash-completion/completions/bts > > In order to understand if the *installation of bash-completion* was > setting the wrong permissions, I temporarily moved the whole directory > out of the way: > > # mv /usr/share/bash-completion/ /usr/share/bash-completion_BACKUP > # ls -lha /usr/share/bash-completion/ > ls: cannot access '/usr/share/bash-completion/': No such file or > directory > > Finally, I installed bash-completion and checked the permissions: > > # aptitude install bash-completion > The following NEW packages will be installed: > bash-completion > 0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded. > Need to get 0 B/207 kB of archives. After unpacking 1,393 kB will be > used. > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > Selecting previously unselected package bash-completion. > (Reading database ... 391843 files and directories currently > installed.) > Preparing to unpack .../bash-completion_1%3a2.8-2_all.deb ... > Unpacking bash-completion (1:2.8-2) ... > Setting up bash-completion (1:2.8-2) ... > Processing triggers for man-db (2.8.4-3) ... > > # ls -lha /usr/share/bash-completion/ > total 120K > drwxr-xr-x 4 root root 4.0K Nov 9 08:04 . (OK) > drwxr-xr-x 303 root root 12K Nov 9 08:04 .. > -rw-r--r-- 1 root root 71K Nov 4 18:01 bash_completion (OK) > drwxr-xr-x 2 root root 28K Nov 9 08:04 completions > drwxr-xr-x 2 root root 4.0K Nov 9 08:04 helpers > > Permissions look correct to me. Maybe the reason why I couldn't > reproduce this bug is related to way I modified /etc/login.defs. So, > if you have more information about it, please let me know. > > I'm marking this bug as unreproducible and I'll wait some time before > closing it. Please feel free to reopen it afterwards. > > > Philippe, > > Are you still seeing this problem? > Do you have any advice about the umask comments I mentioned above? > > > Thank you. >
