[Touch-packages] [Bug 1788958] [NEW] /usr/bin/file fails with Bash process substitution
Public bug reported: == System information == Description:Ubuntu 16.04.5 LTS Release:16.04 file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages == Expected behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: POSIX shell script, ASCII text executable == Actual behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: broken symbolic link to pipe:[10687339] Note that Bash process substitution does work properly in general: $ /bin/cat <( echo '#!/bin/sh' ) #!/bin/sh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 24 18:07:43 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (661 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1788958 Title: /usr/bin/file fails with Bash process substitution Status in file package in Ubuntu: New Bug description: == System information == Description: Ubuntu 16.04.5 LTS Release: 16.04 file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages == Expected behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: POSIX shell script, ASCII text executable == Actual behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: broken symbolic link to pipe:[10687339] Note that Bash process substitution does work properly in general: $ /bin/cat <( echo '#!/bin/sh' ) #!/bin/sh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 24 18:07:43 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (661 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1788958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788958] Re: /usr/bin/file fails with Bash process substitution
Reported upstream at https://bugs.astron.com/view.php?id=32 ** Bug watch added: bugs.astron.com/ #32 https://bugs.astron.com/view.php?id=32 ** Also affects: file via https://bugs.astron.com/view.php?id=32 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1788958 Title: /usr/bin/file fails with Bash process substitution Status in osFileManager: Unknown Status in file package in Ubuntu: New Bug description: == System information == Description: Ubuntu 16.04.5 LTS Release: 16.04 file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages == Expected behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: POSIX shell script, ASCII text executable == Actual behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: broken symbolic link to pipe:[10687339] Note that Bash process substitution does work properly in general: $ /bin/cat <( echo '#!/bin/sh' ) #!/bin/sh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 24 18:07:43 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (661 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/file/+bug/1788958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789461] [NEW] file reports incorrect bug reporting location
Public bug reported: === System information === $ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 $ apt policy file file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages === Problem === The `man` page and `--help` output for `file` both give an incorrect bug reporting location: $ /usr/bin/file --help | tail -2 Report bugs to http://bugs.gw.com/ $ man 1 file | fgrep -A 2 BUGS BUGS Please report bugs and send patches to the bug tracker at http://bugs.gw.com/ or the mailing list at ⟨f...@mx.gw.com⟩ (visit http://mx.gw.com/mailman/listinfo/file first to subscribe). As can be seen quite quickly by visiting the site, http://bugs.gw.com/ is defunct. The correct location according to the GitHub mirror of the `file` repository (at https://github.com/file/file#readme) is: Mailing List: f...@astron.com Mailing List archives: http://mailman.astron.com/pipermail/file/ Bug tracker: http://bugs.astron.com/ E-mail: chris...@astron.com Build Status: https://travis-ci.org/file/file === Solution === 1. Please backport the fix to the `man` page located at the commit https://github.com/file/file/commit/5d6eba6f3281887de8263fdc481daabc98007945 2. Please correct address at bottom of `file --help` output (located here in the source tree: https://github.com/file/file/blob/master/src/file.c#L643-L661) 2. If you know how to submit a patch, they don't accept GitHub pull requests, but the upstream bug report for `file --help` output is at https://bugs.astron.com/view.php?id=33 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 28 10:39:47 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (665 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file Importance: Unknown Status: Unknown ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Bug watch added: bugs.astron.com/ #33 https://bugs.astron.com/view.php?id=33 ** Also affects: file via https://bugs.astron.com/view.php?id=33 Importance: Unknown Status: Unknown ** Description changed: === System information === - $ lsb_release -rd - Description: Ubuntu 16.04.5 LTS - Release: 16.04 - - $ apt policy file - file: - Installed: 1:5.25-2ubuntu1.1 - Candidate: 1:5.25-2ubuntu1.1 - Version table: - *** 1:5.25-2ubuntu1.1 500 - 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages - 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages - 100 /var/lib/dpkg/status - 1:5.25-2ubuntu1 500 - 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages + $ lsb_release -rd + Description: Ubuntu 16.04.5 LTS + Release: 16.04 + + $ apt policy file + file: + Installed: 1:5.25-2ubuntu1.1 + Candidate: 1:5.25-2ubuntu1.1 + Version table: + *** 1:5.25-2ubuntu1.1 500 + 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages + 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages + 100 /var/lib/dpkg/status + 1:5.25-2ubuntu1 500 + 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages === Problem === The `man` page and `--help` output for `file` both give an incorrect bug reporting location: - $ /usr/bin/file --help | tail -2 - - Report bugs to http://bugs.gw.com/ - - $ man 1 file | fgrep -A 2 BUGS - BUGS - Please report bugs and send patches to the bug tracker at http://bugs.gw.com/ or the mailing list at ⟨f...@mx.gw.com⟩ (visit http://mx.gw.com/mailman/listinfo/file first to subscribe). + $ /usr/bin/file --help | tail -2 + + Report bugs to http:/
[Touch-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs
The problem is not that it's impossible to work around the incorrect
default. The problem is the incorrect default itself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1639531
Title:
GCC compiles programs to shared object instead of executable,
preventing GUI file managers from executing programs
Status in gcc-defaults:
Unknown
Status in shared-mime-info:
Unknown
Status in shared-mime-info package in Ubuntu:
Triaged
Bug description:
Release of Ubuntu being used
Description:Ubuntu 16.10
Release:16.10
Version of the package being used
=
gcc:
Installed: 4:6.1.1-1ubuntu2
Candidate: 4:6.1.1-1ubuntu2
Version table:
*** 4:6.1.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status
What was expected
=
Programs compiled using `gcc -o program program.c` should be runnable
by double-clicking them from a GUI file manager.
Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.2)`) produces the following output from
`/usr/bin/file program`:
program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped
This is correct behavior, allowing the executables to run from
Nautilus and Thunar.
What happened instead
=
Programs compiled using `gcc -o program program.c` are not runnable by
double-clicking them from a GUI file manager, even though they are
runnable from the terminal.
Compiling a simple program (`void main() { }`) using the current
version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
the following output from `/usr/bin/file program`:
program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped
The program is also identified as a "shared library" instead of an
"executable" in Thunar, causing it to not be runnable from the GUI.
Others are unable to run such programs from Nautilus.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827753] [NEW] udev package doesn't mark as a configuration file fbdev-blacklist.conf
Public bug reported: System information $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy udev udev: Installed: 237-3ubuntu10.21 Candidate: 237-3ubuntu10.21 Version table: *** 237-3ubuntu10.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.19 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Problem = The `udev` package includes `/lib/modprobe.d/fbdev-blacklist.conf`, a configuration file blacklisting several kernel modules. It's not listed as a configuration file in the package, though: $ cat /var/lib/dpkg/info/udev.conffiles /etc/init.d/udev /etc/udev/udev.conf This means that, if I want to go ahead and use the `sisfb` kernel module, for example, I unblacklist it in the two files it's blacklisted in. However, any updated version of `udev` that's installed will throw away my changes to `/lib/modprobe.d/fbdev-blacklist.conf` by simply overwriting the file and again blacklist the kernel module, which doesn't work well when the system is being used by someone very new to computers. I can't avoid that by simply telling APT to leave configuration files alone because the `.conf` file here technically isn't a configuration file. Also, `chattr +i /lib/modprobe.d/fbdev-blacklist.conf` causes APT to require someone with technical knowledge to take extra effort to repair things when the end user agrees to an install in the weekly GUI reminder of new software. Request = Please mark `/lib/modprobe.d/fbdev-blacklist.conf` as a configuration file in `udev`. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 70-snap.core.rules 70-snap.cnctsun.rules 70-snap.cncra2yr.rules 70-snap.cncra.rules 60-vboxdrv.rules Date: Sat May 4 21:51:42 2019 InstallationDate: Installed on 2018-12-27 (128 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 020: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd09/27/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - System information + System information - $ lsb_release -rd - Description: Ubuntu 18.04.2 LTS - Release: 18.04 + $ lsb_release -rd + Description: Ubuntu 18.04.2 LTS + Release: 18.04 - $ apt-cache policy udev - udev: - Installed: 237-3ubuntu10.21 - Candidate: 237-3ubuntu10.21 - Version table: - *** 237-3ubuntu10.21 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 237-3ubuntu10.19 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 237-3ubuntu10 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + $ apt-cache policy udev + udev: + Installed: 237-3ubuntu10.21 + Candidate: 237-3ubuntu10.21 + Version table: + *** 237-3ubuntu10.21 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 237-3ubuntu10.19 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 237-3ubuntu10 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - Problem + Problem = The `udev` package includes `/lib/modprobe.d/fbdev-blacklist.conf`, a configuration file blacklisting several kernel modules. It's not listed as a configuration file in the package, though: - $ cat /var/lib/dpkg/info/udev.conffiles
[Touch-packages] [Bug 1827753] Re: udev package doesn't mark as a configuration file fbdev-blacklist.conf
** Description changed: System information $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy udev udev: Installed: 237-3ubuntu10.21 Candidate: 237-3ubuntu10.21 Version table: *** 237-3ubuntu10.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.19 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Problem = The `udev` package includes `/lib/modprobe.d/fbdev-blacklist.conf`, a configuration file blacklisting several kernel modules. It's not listed as a configuration file in the package, though: $ cat /var/lib/dpkg/info/udev.conffiles /etc/init.d/udev /etc/udev/udev.conf This means that, if I want to go ahead and use the `sisfb` kernel - module, for example, any updated version of `udev` that's installed will - again blacklist the kernel module, which doesn't work well when the - system is being used by someone very new to computers. + module, for example, I unblacklist it in the two files it's blacklisted + in. However, any updated version of `udev` that's installed will throw + away my changes to `/lib/modprobe.d/fbdev-blacklist.conf` by simply + overwriting the file and again blacklist the kernel module, which + doesn't work well when the system is being used by someone very new to + computers. I can't avoid that by simply telling APT to leave configuration files alone because the `.conf` file here technically isn't a configuration file. Also, `chattr +i /lib/modprobe.d/fbdev-blacklist.conf` causes APT to require someone with technical knowledge to take extra effort to repair things when the end user agrees to an install in the weekly GUI reminder of new software. Request = Please mark `/lib/modprobe.d/fbdev-blacklist.conf` as a configuration file in `udev`. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 70-snap.core.rules 70-snap.cnctsun.rules 70-snap.cncra2yr.rules 70-snap.cncra.rules 60-vboxdrv.rules Date: Sat May 4 21:51:42 2019 InstallationDate: Installed on 2018-12-27 (128 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 020: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd09/27/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1827753 Title: udev package doesn't mark as a configuration file fbdev-blacklist.conf Status in systemd package in Ubuntu: New Bug description: System information $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy udev udev: Installed: 237-3ubuntu10.21 Candidate: 237-3ubuntu10.21 Version table: *** 237-3ubuntu10.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.19 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Problem = The `udev` package includes `/lib/modprobe.d/fbdev-blacklist.conf`, a configuration file blacklisting several kernel modules. It's not listed as a configuration file in the package, though: $ cat /var/lib/dpkg/info/udev.conffiles /etc/init.d/udev /etc/udev/udev.conf This means that, if I want to go ahead and use the `sisf
[Touch-packages] [Bug 1861364] [NEW] /etc/environment.d cannot be used to add to PATH
Public bug reported: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: github.com/systemd/systemd/issues #6414 https://github.com/systemd/systemd/issues/6414 ** Also affects: systemd via https://github.com/systemd/systemd/issues/6414 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861364 Title: /etc/environment.d cannot be used to add to PATH Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Li
[Touch-packages] [Bug 1861363] [NEW] /etc/environment.d cannot be used to add to PATH
Public bug reported: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co.,
[Touch-packages] [Bug 1861363] Re: /etc/environment.d cannot be used to add to PATH
My `/etc/profile` doesn't seem to set the PATH, so the systemd bug
resolution may not be applicable:
$ grep PATH /etc/profile
$
I have Ubuntu 18.04 (Server, I assume) installed on a cloud server. I
access it only via SSH/Mosh and have no GUI (X or Wayland) installed as
far as I know.
I'm not sure in what order the PATH is set during boot, login, etc. All
I know is that `man environment.d` is incorrect when it says `PATH` can
be changed in a `.conf` file located in `/etc/environment.d`:
Example
Example 1. Setup environment to allow access to a program installed in
/opt/foo
/etc/environment.d/60-foo.conf:
FOO_DEBUG=force-software-gl,log-verbose
PATH=/opt/foo/bin:$PATH
LD_LIBRARY_PATH=/opt/foo/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
XDG_DATA_DIRS=/opt/foo/share:${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861363
Title:
/etc/environment.d cannot be used to add to PATH
Status in systemd package in Ubuntu:
New
Bug description:
I've added an executable file `/etc/environment.d/60-haskell.conf`
with the following contents:
PATH=/opt/ghc/bin:$PATH
According to `man environment.d`, this is a proper procedure for
altering the PATH variable via systemd. However, it does not work on
Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`.
This is due to `/etc/profile` incorrectly overwriting the PATH
according to comment #10 on
https://github.com/systemd/systemd/issues/6414.
There is a Debian bug at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=869144 that was prematurely closed because on
the Debian side **because it was a Debian issue** rather than a
systemd issue, which seems quite nonsensical. Perhaps that issue can
be reopened or another can be opened.
==
Description:Ubuntu 18.04.3 LTS
Release:18.04
systemd:
Installed: 237-3ubuntu10.33
Candidate: 237-3ubuntu10.33
Version table:
*** 237-3ubuntu10.33 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
237-3ubuntu10.29 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.33
ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Wed Jan 29 19:07:31 2020
InstallationDate: Installed on 2019-10-10 (111 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic
root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.1
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.1
dmi.sys.vendor: QEMU
modified.conffile..etc.systemd.timesyncd.conf: [modified]
mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861363] Re: /etc/environment.d cannot be used to add to PATH
To add to the issue, `/etc/environment` has one line setting `PATH` and throwing out any old versions of `PATH` (it doesn't contain `$PATH`). Changing that changed my `PATH` consistently on reboot: $ cat /etc/environment PATH="/opt/ghc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" $ printenv PATH /home/ubuntu/.cargo/bin:/home/ubuntu/bin:/opt/ghc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin I tried adding a line to `/etc/environment.d/60-haskell.conf` setting `ZOMG=zomg`, but it wasn't picked up on reboot, so it appears that files in `/etc/environment.d` do nothing at all, not that they're just overwritten by `/etc/environment`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861363] Re: /etc/environment.d cannot be used to add to PATH
I've found out that `/etc/environment.d` is not intended for setting environment variables for login shells. From poettering at https://github.com/systemd/systemd/issues/12938: @dschepler is right. systemd-environment-d-generator gets run by systemd --user, and thus set environment variables for the systemd per- user service manager and their child processes only. Login shells (such as those started via getty on the console or ssh) are not children of systemd and hence the generators have no effect on them whatsoever. For login sessions use pam_env or some .profile script or similar to set env vars... Sorry. ** Bug watch added: github.com/systemd/systemd/issues #12938 https://github.com/systemd/systemd/issues/12938 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: Invalid Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641213] [NEW] PAM blocks fixing `chsh`ing root to a nonexistent shell
Public bug reported: Ubuntu release == Description:Ubuntu 16.04.1 LTS Release:16.04 Package version === According to `apt-file search /etc/pam.d/chsh`, package `passwd` owns that file. passwd: Installed: 1:4.2-3.1ubuntu5 Candidate: 1:4.2-3.1ubuntu5 Version table: *** 1:4.2-3.1ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen === The following should mess up root's default shell and then fix it to use `bash`: sudo chsh -s /bin/nonexistent sudo chsh -s /bin/bash What happened instead = PAM blocks what should be a simple fix: $ sudo chsh -s /bin/nonexistent chsh: Warning: /bin/nonexistent does not exist $ sudo chsh -s /bin/bash Password: chsh: PAM: Authentication failure Note especially that the password prompt above isn't the standard `sudo` password prompt. `sudo` has already been recently given a password, so it didn't ask again. $ SHELL=/bin/bash sudo --shell # chsh -s /bin/bash Password: chsh: PAM: Authentication failure This happens even though the `root` account is disabled and thus has no password. Even setting a password for `root` and using that password doesn't work, so it's apparently not asking for the `root` password. Workaround == 1. Edit `/etc/pam.d/chsh` 2. Comment out the line `auth required pam_shells.so` 3. Run `sudo chsh -s /bin/bash` 4. Edit `/etc/pam.d/chsh` 5. Uncomment the line `auth required pam_shells.so` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 14:42:57 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (10 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1641213 Title: PAM blocks fixing `chsh`ing root to a nonexistent shell Status in shadow package in Ubuntu: New Bug description: Ubuntu release == Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version === According to `apt-file search /etc/pam.d/chsh`, package `passwd` owns that file. passwd: Installed: 1:4.2-3.1ubuntu5 Candidate: 1:4.2-3.1ubuntu5 Version table: *** 1:4.2-3.1ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen === The following should mess up root's default shell and then fix it to use `bash`: sudo chsh -s /bin/nonexistent sudo chsh -s /bin/bash What happened instead = PAM blocks what should be a simple fix: $ sudo chsh -s /bin/nonexistent chsh: Warning: /bin/nonexistent does not exist $ sudo chsh -s /bin/bash Password: chsh: PAM: Authentication failure Note especially that the password prompt above isn't the standard `sudo` password prompt. `sudo` has already been recently given a password, so it didn't ask again. $ SHELL=/bin/bash sudo --shell # chsh -s /bin/bash Password: chsh: PAM: Authentication failure This happens even though the `root` account is disabled and thus has no password. Even setting a password for `root` and using that password doesn't work, so it's apparently not asking for the `root` password. Workaround == 1. Edit `/etc/pam.d/chsh` 2. Comment out the line `auth required pam_shells.so` 3. Run `sudo chsh -s /bin/bash` 4. Edit `/etc/pam.d/chsh` 5. Uncomment the line `auth required pam_shells.so` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 14:42:57 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate
[Touch-packages] [Bug 1641213] Re: PAM blocks fixing `chsh`ing root to a nonexistent shell
** Description changed: Ubuntu release == Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version === According to `apt-file search /etc/pam.d/chsh`, package `passwd` owns that file. passwd: - Installed: 1:4.2-3.1ubuntu5 - Candidate: 1:4.2-3.1ubuntu5 - Version table: - *** 1:4.2-3.1ubuntu5 500 - 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:4.2-3.1ubuntu5 + Candidate: 1:4.2-3.1ubuntu5 + Version table: + *** 1:4.2-3.1ubuntu5 500 + 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status What you expected to happen === The following should mess up root's default shell and then fix it to use `bash`. - sudo chsh -s /bin/nonexistent - sudo chsh -s /bin/bash + sudo chsh -s /bin/nonexistent + sudo chsh -s /bin/bash What happened instead = PAM blocks what should be a simple fix: - $ sudo chsh -s /bin/noexistent - chsh: Warning: /bin/noexistent does not exist - $ sudo chsh -s /bin/bash - Password: - chsh: PAM: Authentication failure + $ sudo chsh -s /bin/nonexistent + chsh: Warning: /bin/nonexistent does not exist + $ sudo chsh -s /bin/bash + Password: + chsh: PAM: Authentication failure Note especially that the password prompt above isn't the standard `sudo` password prompt. `sudo` has already been recently given a password, so it didn't ask again. - $ SHELL=/bin/bash sudo --shell - # chsh -s /bin/bash - Password: - chsh: PAM: Authentication failure + $ SHELL=/bin/bash sudo --shell + # chsh -s /bin/bash + Password: + chsh: PAM: Authentication failure This happens even though the `root` account is disabled and thus has no password. Even setting a password for `root` and using that password doesn't work, so it's apparently not asking for the `root` password. Workaround == 1. Edit `/etc/pam.d/chsh` 2. Comment out the line `auth required pam_shells.so` 3. Run `sudo chsh -s /bin/bash` 4. Edit `/etc/pam.d/chsh` 5. Uncomment the line `auth required pam_shells.so` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 14:42:57 2016 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-20160624-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (10 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Ubuntu release == Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version === According to `apt-file search /etc/pam.d/chsh`, package `passwd` owns that file. passwd: Installed: 1:4.2-3.1ubuntu5 Candidate: 1:4.2-3.1ubuntu5 Version table: *** 1:4.2-3.1ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen === The following should mess up root's default shell and then fix it to use - `bash`. + `bash`: sudo chsh -s /bin/nonexistent sudo chsh -s /bin/bash What happened instead = PAM blocks what should be a simple fix: - $ sudo chsh -s /bin/nonexistent - chsh: Warning: /bin/nonexistent does not exist + $ sudo chsh -s /bin/noexistent + chsh: Warning: /bin/noexistent does not exist $ sudo chsh -s /bin/bash Password: chsh: PAM: Authentication failure Note especially that the password prompt above isn't the standard `sudo` password prompt. `sudo` has already been recently given a password, so it didn't ask again. $ SHELL=/bin/bash sudo --shell # chsh -s /bin/bash Password: chsh: PAM: Authentication failure This happens even though the `root` account is disabled and thus has no password. Even setting a password for `root` and using that password doesn't work, so it's apparently not asking for the `root` password. Workaround == 1. Edit `/etc/pam.d/chsh` 2. Comment out the line `auth required pam_shells.so` 3. Run `sudo c
[Touch-packages] [Bug 1642863] [NEW] Upgrading unattended-upgrades gives errors and a warning
Public bug reported: Ubuntu release == Description:Ubuntu 16.04.1 LTS Release:16.04 Package version === unattended-upgrades: Installed: 0.90ubuntu0.2 Candidate: 0.90ubuntu0.2 Version table: *** 0.90ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages What I expected to happen = No error or warning messages during a software upgrade. What happened instead = When an updated version of unattended-upgrades is installed, the following error messages appear because /tmp is mounted noexec for security reasons (see the Securing Debian Manual, section 4.10 at https://www.debian.org/doc/manuals/securing-debian- howto/ch4.en.html#s4.10): Preconfiguring packages ... Can't exec "/tmp/unattended-upgrades.config.5svL0F": Permission denied at /usr/share/perl/5.22/IPC/Open3.pm line 178. open2: exec of /tmp/unattended-upgrades.config.5svL0F configure 0.90ubuntu0.1 failed at /usr/share/perl5/Debconf/ConfModule.pm line 59. Also, the following warning occurs later on: Setting up unattended-upgrades (0.90ubuntu0.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 18 02:36:54 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-11-07T13:58:08.805628 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1642863 Title: Upgrading unattended-upgrades gives errors and a warning Status in unattended-upgrades package in Ubuntu: New Bug description: Ubuntu release == Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version === unattended-upgrades: Installed: 0.90ubuntu0.2 Candidate: 0.90ubuntu0.2 Version table: *** 0.90ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages What I expected to happen = No error or warning messages during a software upgrade. What happened instead = When an updated version of unattended-upgrades is installed, the following error messages appear because /tmp is mounted noexec for security reasons (see the Securing Debian Manual, section 4.10 at https://www.debian.org/doc/manuals/securing-debian- howto/ch4.en.html#s4.10): Preconfiguring packages ... Can't exec "/tmp/unattended-upgrades.config.5svL0F": Permission denied at /usr/share/perl/5.22/IPC/Open3.pm line 178. open2: exec of /tmp/unattended-upgrades.config.5svL0F configure 0.90ubuntu0.1 failed at /usr/share/perl5/Debconf/ConfModule.pm line 59. Also, the following warning occurs later on: Setting up unattended-upgrades (0.90ubuntu0.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 18 02:36:54 2016 DistributionChannelDescriptor: # This i
