[Touch-packages] [Bug 1808183] [NEW] server console output extremely slow after upgrade to 18.04
Public bug reported: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: server console output extremely slow after upgrade to 18.04 Status in xorg package in Ubuntu: New Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1808183/+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 1802469] Re: after upgrade to 18.04 the system sometimes just boots into emergency mode
Today it happened again and I have attached a screenshot here. As said, after a ctrl-alt-delete the system booted ok and I can see no sign of the failed disk in the logs. ** Attachment added: "IMG_20181114_081408_739.jpg" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802469/+attachment/5212555/+files/IMG_20181114_081408_739.jpg -- 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/1802469 Title: after upgrade to 18.04 the system sometimes just boots into emergency mode Status in systemd package in Ubuntu: New Bug description: After I updated my server (no GUI) from 16.04 to 18.04 my system sometimes gets stuck in emergency mode. Normally my system needs about 20 seconds to get through the dmesg part, and then another 2-5 seconds until the login prompt. The dmesg part is still fine but, after that, about once a week, I see very slow boot messages dripping down the screen at a rate of 1 line/second. If this happens, somewhere along the way, the system issues a warning about a device which has timed out like below: dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device: Job dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device/start timed out.` and, some time later, there is a message about starting an emergency shell. But then, the system seems to hang, and I get no prompt nor any console feedback upon typing. I can issue a Ctrl+Alt+Del though which does a reboot. After I had done that the system up to now always came up properly in about 20 seconds as stated above and I do not see the device which was complained about before. I have no clue how I can troubleshoot the issue. Is this a known problem due to some conflicting conditions in the "glorious" systemd boot mechanisms? Is there a command like "systemd-analyze blame" which can analyze a failed previous boot? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.4 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Nov 9 08:52:32 2018 MachineType: ASUSTeK COMPUTER INC. P9D-X Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-11 (28 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802469/+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 1802469] [NEW] after upgrade to 18.04 the system sometimes just boots into emergency mode
Public bug reported: After I updated my server (no GUI) from 16.04 to 18.04 my system sometimes gets stuck in emergency mode. Normally my system needs about 20 seconds to get through the dmesg part, and then another 2-5 seconds until the login prompt. The dmesg part is still fine but, after that, about once a week, I see very slow boot messages dripping down the screen at a rate of 1 line/second. If this happens, somewhere along the way, the system issues a warning about a device which has timed out like below: dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device: Job dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device/start timed out.` and, some time later, there is a message about starting an emergency shell. But then, the system seems to hang, and I get no prompt nor any console feedback upon typing. I can issue a Ctrl+Alt+Del though which does a reboot. After I had done that the system up to now always came up properly in about 20 seconds as stated above and I do not see the device which was complained about before. I have no clue how I can troubleshoot the issue. Is this a known problem due to some conflicting conditions in the "glorious" systemd boot mechanisms? Is there a command like "systemd-analyze blame" which can analyze a failed previous boot? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.4 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Nov 9 08:52:32 2018 MachineType: ASUSTeK COMPUTER INC. P9D-X Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-11 (28 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - upgrade to 18.04 sometimes runs into emergency mode + after upgrade to 18.04 the system sometimes just boots into emergency mode ** Description changed: - After I updated my server (no GUI) from 16.04 to 18.04 my system sometimes get stuck in emergency mode. + After I updated my server (no GUI) from 16.04 to 18.04 my system sometimes gets stuck in emergency mode. Normally my system needs about 20 seconds to get through the dmesg part, and then another 2-5 seconds until the login prompt. The dmesg part is still fine but, after that, about once a week, I see very slow boot messages dripping down the screen at a rate of 1 line/second. If this happens, somewhere along the way, the system issues a warning about a device which has timed out like below: - dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device: - Job dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device/start timed out.` + dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device: + Job dev-disk-by\x2duuid-db5f4fae\x2d18a0\x2d4df3\x2d8ba3\x2d709f00eac21c.device/start timed out.` and, some time later, there is a message about starting an emergency shell. But then, the system seems to hang, and I get no prompt nor any console feedback upon typing. I can issue a Ctrl+Alt+Del though which does a reboot. - After I did that the system always came up properly in about 20 seconds as stated above and I do not see the device which was complained about before. + After I had done that the system up to now always came up properly in about 20 seconds as stated above and I do not see the device which was complained about before. I have no clue how I can troubleshoot the issue. Is this a known problem due to some conflicting conditions in the "glorious" systemd boot mechanisms? Is there a command like "systemd-analyze blame" which can analyze a failed previous boot? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.4 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Nov 9 08:52:32 2018 MachineType: ASUSTeK
[Touch-packages] [Bug 1169581] Re: desktop LTS 12.04.2 broken cifs support on install
This bug is still open with Ubuntu 18.04.1 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1169581 Title: desktop LTS 12.04.2 broken cifs support on install Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Precise: Confirmed Status in initramfs-tools package in Baltix: New Bug description: desktop LTS 12.04/.2 broken cifs support on install While initrd.lz includes cifs.ko the modules des_generic.ko and md4.ko are missing. CIFS is very handy when PXE booting Ubuntu LTS Desktop live from Windows OSs as Serva does it here. http://vercot.com/~serva/an/NonWindowsPXE3.html The inclusion of des_generic.ko and md4.ko within initrd.lz would avoid the need of loading manually made complementary initrd files. I hope you guys can add these 2 files for 12.04.3 considering this is an LTS. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1169581/+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 1169581] Re: desktop LTS 12.04.2 broken cifs support on install
with windows cifs not supporting vers=1.0 anymore it is crucial that the crypto kernel modules are included in the initial ram images. Otherwise it is not possible to mount any cifs volumes from the ram image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1169581 Title: desktop LTS 12.04.2 broken cifs support on install Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Precise: Confirmed Status in initramfs-tools package in Baltix: New Bug description: desktop LTS 12.04/.2 broken cifs support on install While initrd.lz includes cifs.ko the modules des_generic.ko and md4.ko are missing. CIFS is very handy when PXE booting Ubuntu LTS Desktop live from Windows OSs as Serva does it here. http://vercot.com/~serva/an/NonWindowsPXE3.html The inclusion of des_generic.ko and md4.ko within initrd.lz would avoid the need of loading manually made complementary initrd files. I hope you guys can add these 2 files for 12.04.3 considering this is an LTS. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1169581/+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 1761474] [NEW] missing perl utilities like find2perl, a2ps, s2ps
Public bug reported: What has happened to those perl utilities find2perl, a2p and s2p ? These utilities are normally a part of perl distribution, but they now seem to be stripped off on Ubuntu. They used to be part of perl-doc until perl-doc_5.18.2-2ubuntu1_all on ubuntu 14.04 LTS. I do not see the reason why these valuable tools are not supported on the later Ubuntu revisions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: perl 5.22.1-9ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Apr 5 13:00:08 2018 SourcePackage: perl UpgradeStatus: Upgraded to xenial on 2017-12-06 (120 days ago) ** Affects: perl (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 perl in Ubuntu. https://bugs.launchpad.net/bugs/1761474 Title: missing perl utilities like find2perl, a2ps, s2ps Status in perl package in Ubuntu: New Bug description: What has happened to those perl utilities find2perl, a2p and s2p ? These utilities are normally a part of perl distribution, but they now seem to be stripped off on Ubuntu. They used to be part of perl-doc until perl-doc_5.18.2-2ubuntu1_all on ubuntu 14.04 LTS. I do not see the reason why these valuable tools are not supported on the later Ubuntu revisions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: perl 5.22.1-9ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Apr 5 13:00:08 2018 SourcePackage: perl UpgradeStatus: Upgraded to xenial on 2017-12-06 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1761474/+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 1741176] Re: ssh-keyscan returns no key on some hosts
SOLVED: I found that for some reason I needed to extend the default timeout to get the proper response ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1741176 Title: ssh-keyscan returns no key on some hosts Status in openssh package in Ubuntu: Invalid Bug description: after upgrading our control server to Ubunto 16.04 LTS I do not get a key response from ssh-keyscan from some legacy hosts while others with the same OpenSSH revision work ok. Here is a sample output where you can see that in the first query that there is just the SSH version displayed but no key part. The queried hosts are all HP-UX 10.20 with OpenSSH 4.1 ssh-keyscan -t rsa -4 host1 # host1:22 SSH-2.0-OpenSSH_4.1 ssh-keyscan -t rsa -4 host2 # host2:22 SSH-2.0-OpenSSH_4.1 host2 ssh-rsa B3NzaC1yc2EBIwAAAIEAswUwKzs87EU9Q7gVGIyupZowMT1o8FB+u/DKAy6sgjyZ8/RBGwl0R7DIdNw5U6E9sAwE5tyB4CQp2G39o8YpHDo75co9+ALULiRC+xqaGmvMtY7aipHzlOyE6Sa0t0xKcfPXsk2ekq46S84vzhWy3yIJCHVbTBjiN4NXv96gPBU= If I do the same on host1 from an Ubuntu 14.04.5 LTS it works ssh-keyscan -t rsa host1 # host1 SSH-2.0-OpenSSH_4.1 host11 ssh-rsa B3NzaC1yc2EBIwAAAIEAtBAPXd7KxHoKH52Q8jwPKRM2m9TFdivAyizkOTj7m0YHqdNjohLz6ID/7jlsq+8ou9KjSydpukiwc5goNutb2ndsAd/5+XcqRAGt1TyMxVAF0X5uFoic0QW3AvBORvIkhym36CS2ivMkaYkHaCn9k8XjbVjzXLW4+xmkplWdjXU= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1741176/+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 1741176] Re: ssh-keyscan returns no key on some hosts
Attached is an output of ssh-keyscan -vv to give more details ** Attachment added: "ssh.log" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1741176/+attachment/5030888/+files/ssh.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1741176 Title: ssh-keyscan returns no key on some hosts Status in openssh package in Ubuntu: New Bug description: after upgrading our control server to Ubunto 16.04 LTS I do not get a key response from ssh-keyscan from some legacy hosts while others with the same OpenSSH revision work ok. Here is a sample output where you can see that in the first query that there is just the SSH version displayed but no key part. The queried hosts are all HP-UX 10.20 with OpenSSH 4.1 ssh-keyscan -t rsa -4 host1 # host1:22 SSH-2.0-OpenSSH_4.1 ssh-keyscan -t rsa -4 host2 # host2:22 SSH-2.0-OpenSSH_4.1 host2 ssh-rsa B3NzaC1yc2EBIwAAAIEAswUwKzs87EU9Q7gVGIyupZowMT1o8FB+u/DKAy6sgjyZ8/RBGwl0R7DIdNw5U6E9sAwE5tyB4CQp2G39o8YpHDo75co9+ALULiRC+xqaGmvMtY7aipHzlOyE6Sa0t0xKcfPXsk2ekq46S84vzhWy3yIJCHVbTBjiN4NXv96gPBU= If I do the same on host1 from an Ubuntu 14.04.5 LTS it works ssh-keyscan -t rsa host1 # host1 SSH-2.0-OpenSSH_4.1 host11 ssh-rsa B3NzaC1yc2EBIwAAAIEAtBAPXd7KxHoKH52Q8jwPKRM2m9TFdivAyizkOTj7m0YHqdNjohLz6ID/7jlsq+8ou9KjSydpukiwc5goNutb2ndsAd/5+XcqRAGt1TyMxVAF0X5uFoic0QW3AvBORvIkhym36CS2ivMkaYkHaCn9k8XjbVjzXLW4+xmkplWdjXU= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1741176/+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 1741176] [NEW] ssh-keyscan returns no key on some hosts
Public bug reported: after upgrading our control server to Ubunto 16.04 LTS I do not get a key response from ssh-keyscan from some legacy hosts while others with the same OpenSSH revision work ok. Here is a sample output where you can see that in the first query that there is just the SSH version displayed but no key part. The queried hosts are all HP-UX 10.20 with OpenSSH 4.1 ssh-keyscan -t rsa -4 host1 # host1:22 SSH-2.0-OpenSSH_4.1 ssh-keyscan -t rsa -4 host2 # host2:22 SSH-2.0-OpenSSH_4.1 host2 ssh-rsa B3NzaC1yc2EBIwAAAIEAswUwKzs87EU9Q7gVGIyupZowMT1o8FB+u/DKAy6sgjyZ8/RBGwl0R7DIdNw5U6E9sAwE5tyB4CQp2G39o8YpHDo75co9+ALULiRC+xqaGmvMtY7aipHzlOyE6Sa0t0xKcfPXsk2ekq46S84vzhWy3yIJCHVbTBjiN4NXv96gPBU= If I do the same on host1 from an Ubuntu 14.04.5 LTS it works ssh-keyscan -t rsa host1 # host1 SSH-2.0-OpenSSH_4.1 host11 ssh-rsa B3NzaC1yc2EBIwAAAIEAtBAPXd7KxHoKH52Q8jwPKRM2m9TFdivAyizkOTj7m0YHqdNjohLz6ID/7jlsq+8ou9KjSydpukiwc5goNutb2ndsAd/5+XcqRAGt1TyMxVAF0X5uFoic0QW3AvBORvIkhym36CS2ivMkaYkHaCn9k8XjbVjzXLW4+xmkplWdjXU= ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1741176 Title: ssh-keyscan returns no key on some hosts Status in openssh package in Ubuntu: New Bug description: after upgrading our control server to Ubunto 16.04 LTS I do not get a key response from ssh-keyscan from some legacy hosts while others with the same OpenSSH revision work ok. Here is a sample output where you can see that in the first query that there is just the SSH version displayed but no key part. The queried hosts are all HP-UX 10.20 with OpenSSH 4.1 ssh-keyscan -t rsa -4 host1 # host1:22 SSH-2.0-OpenSSH_4.1 ssh-keyscan -t rsa -4 host2 # host2:22 SSH-2.0-OpenSSH_4.1 host2 ssh-rsa B3NzaC1yc2EBIwAAAIEAswUwKzs87EU9Q7gVGIyupZowMT1o8FB+u/DKAy6sgjyZ8/RBGwl0R7DIdNw5U6E9sAwE5tyB4CQp2G39o8YpHDo75co9+ALULiRC+xqaGmvMtY7aipHzlOyE6Sa0t0xKcfPXsk2ekq46S84vzhWy3yIJCHVbTBjiN4NXv96gPBU= If I do the same on host1 from an Ubuntu 14.04.5 LTS it works ssh-keyscan -t rsa host1 # host1 SSH-2.0-OpenSSH_4.1 host11 ssh-rsa B3NzaC1yc2EBIwAAAIEAtBAPXd7KxHoKH52Q8jwPKRM2m9TFdivAyizkOTj7m0YHqdNjohLz6ID/7jlsq+8ou9KjSydpukiwc5goNutb2ndsAd/5+XcqRAGt1TyMxVAF0X5uFoic0QW3AvBORvIkhym36CS2ivMkaYkHaCn9k8XjbVjzXLW4+xmkplWdjXU= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1741176/+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 1727243] Re: systemd-logind
My apologies. I found that in fact after a server move my surveillance system tried to contact the new server every second. So it was a setup problem and the log messages were just confusing me. ** 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/1727243 Title: systemd-logind Status in systemd package in Ubuntu: Invalid Bug description: my auth.log is full of messages like below. The 79.247.. is my own address and there seems to be something which tries to reconnect every other second although I am already in a running session. What is going on here? Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... port 52067 ssh2: RSA SHA256:pru... Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root. Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 52067:11: disconnected by user Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067 Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897. Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... port 52068 ssh2: RSA SHA256:pru... Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:59 h... systemd-logind[285]: New session 2373898 of user root. Oct 25 10:38:59 h... sshd[6524]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:59 h... sshd[6524]: Received disconnect from 79.247... port 52068:11: disconnected by user Oct 25 10:38:59 h... sshd[6524]: Disconnected from 79.247... port 52068 Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:59 h... systemd-logind[285]: Removed session 2373898. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... CRON[6564]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... sshd[6562]: Accepted publickey for root from 79.247... port 52069 ssh2: RSA SHA256:pru... Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... systemd-logind[285]: New session 2373904 of user root. Oct 25 10:39:01 h... sshd[6562]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:01 h... sshd[6562]: Received disconnect from 79.247... port 52069:11: disconnected by user Oct 25 10:39:01 h... sshd[6562]: Disconnected from 79.247... port 52069 Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:01 h... systemd-logind[285]: Removed session 2373904. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session closed for user root Oct 25 10:39:02 h... sshd[6665]: Accepted publickey for root from 79.247... port 52070 ssh2: RSA SHA256:pru... Oct 25 10:39:02 h... sshd[6665]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:02 h... systemd-logind[285]: New session 2373945 of user root. Oct 25 10:39:03 h... sshd[6665]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:03 h... sshd[6665]: Received disconnect from 79.247... port 52070:11: disconnected by user Oct 25 10:39:03 h... sshd[6665]: Disconnected from 79.247... port 52070 Oct 25 10:39:03 h... sshd[6665]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:03 h... systemd-logind[285]: Removed session 2373945. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727243/+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 1727243] Re: pam_systemd
Upon investigating further I now suspect it is systemd-logind which causes the problem. As can be seen in auth.log, the system-logind tries to start a new session every second for an unknown reason. In /var/log/syslog I see corresponding messages like this: Oct 27 07:42:39 h2... systemd[19421]: Startup finished in 5ms. Oct 27 07:42:39 h2... systemd[19421]: Stopped target Default. Oct 27 07:42:39 h2... systemd[19421]: Stopped target Basic System. Oct 27 07:42:39 h2... systemd[19421]: Stopped target Timers. Oct 27 07:42:39 h2... systemd[19421]: Stopped target Sockets. Oct 27 07:42:39 h2... systemd[19421]: Reached target Shutdown. Oct 27 07:42:39 h2... systemd[19421]: Starting Exit the Session... Oct 27 07:42:39 h2... systemd[19421]: Stopped target Paths. Oct 27 07:42:39 h2... systemd[19421]: Received SIGRTMIN+24 from PID 19447 (kill). Oct 27 07:42:40 h2... systemd[19468]: Reached target Paths. Oct 27 07:42:40 h2... systemd[19468]: Reached target Timers. Oct 27 07:42:40 h2... systemd[19468]: Reached target Sockets. Oct 27 07:42:40 h2... systemd[19468]: Reached target Basic System. Oct 27 07:42:40 h2... systemd[19468]: Reached target Default. Oct 27 07:42:40 h2... systemd[19468]: Startup finished in 6ms. ** Summary changed: - pam_systemd + systemd-logind -- 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/1727243 Title: systemd-logind Status in systemd package in Ubuntu: New Bug description: my auth.log is full of messages like below. The 79.247.. is my own address and there seems to be something which tries to reconnect every other second although I am already in a running session. What is going on here? Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... port 52067 ssh2: RSA SHA256:pru... Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root. Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 52067:11: disconnected by user Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067 Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897. Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... port 52068 ssh2: RSA SHA256:pru... Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:59 h... systemd-logind[285]: New session 2373898 of user root. Oct 25 10:38:59 h... sshd[6524]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:59 h... sshd[6524]: Received disconnect from 79.247... port 52068:11: disconnected by user Oct 25 10:38:59 h... sshd[6524]: Disconnected from 79.247... port 52068 Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:59 h... systemd-logind[285]: Removed session 2373898. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... CRON[6564]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... sshd[6562]: Accepted publickey for root from 79.247... port 52069 ssh2: RSA SHA256:pru... Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... systemd-logind[285]: New session 2373904 of user root. Oct 25 10:39:01 h... sshd[6562]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:01 h... sshd[6562]: Received disconnect from 79.247... port 52069:11: disconnected by user Oct 25 10:39:01 h... sshd[6562]: Disconnected from 79.247... port 52069 Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:01 h... systemd-logind[285]: Removed session 2373904. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session closed for user root Oct 25 10:39:02 h... sshd[6665]: Accepted publickey for root from 79.247... port 52070 ssh2: RSA SHA256:pru... Oct 25 10:39:02 h... sshd[6665]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:02 h... systemd-logind[285]: New session 2373945 of user root. Oct 25 10:39:03 h... sshd[6665]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:03 h... sshd[6665]: Received disconnect from 79.247... port 52070:11: disconnected by user Oct 25 10:39:03 h... sshd[6665]: Disconnected from 79.247... port 52070 Oct 25 10:39:03 h... sshd[6665]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:03 h...
[Touch-packages] [Bug 1727243] Re: pam_systemd
Maybe it is more related to sshd than to pam. If I do a ps -ef | grep ssh I frequently see lines like below. To my understanding starting a new ssh session is totally unnecessary. # ps -ef | grep ssh root 406 1 0 Oct25 ?00:00:21 /usr/sbin/sshd -D root 1301 406 0 08:02 ?00:00:00 sshd: root@pts/0 # ps -ef | grep ssh root 406 1 0 Oct25 ?00:00:21 /usr/sbin/sshd -D root 1301 406 0 08:02 ?00:00:00 sshd: root@pts/0 root 14486 406 0 11:50 ?00:00:00 sshd: [accepted] sshd 14487 14486 0 11:50 ?00:00:00 sshd: [net] # ps -ef | grep ssh root 406 1 0 Oct25 ?00:00:21 /usr/sbin/sshd -D root 1301 406 0 08:02 ?00:00:00 sshd: root@pts/0 # ps -ef | grep ssh root 406 1 0 Oct25 ?00:00:21 /usr/sbin/sshd -D root 1301 406 0 08:02 ?00:00:00 sshd: root@pts/0 # ps -ef | grep ssh root 406 1 0 Oct25 ?00:00:21 /usr/sbin/sshd -D root 1301 406 0 08:02 ?00:00:00 sshd: root@pts/0 root 14520 406 0 11:50 ?00:00:00 sshd: [accepted] sshd 14521 14520 0 11:50 ?00:00:00 sshd: [net] -- 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/1727243 Title: pam_systemd Status in systemd package in Ubuntu: New Bug description: my auth.log is full of messages like below. The 79.247.. is my own address and there seems to be something which tries to reconnect every other second although I am already in a running session. What is going on here? Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... port 52067 ssh2: RSA SHA256:pru... Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root. Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 52067:11: disconnected by user Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067 Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897. Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... port 52068 ssh2: RSA SHA256:pru... Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:59 h... systemd-logind[285]: New session 2373898 of user root. Oct 25 10:38:59 h... sshd[6524]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:59 h... sshd[6524]: Received disconnect from 79.247... port 52068:11: disconnected by user Oct 25 10:38:59 h... sshd[6524]: Disconnected from 79.247... port 52068 Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:59 h... systemd-logind[285]: Removed session 2373898. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... CRON[6564]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... sshd[6562]: Accepted publickey for root from 79.247... port 52069 ssh2: RSA SHA256:pru... Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... systemd-logind[285]: New session 2373904 of user root. Oct 25 10:39:01 h... sshd[6562]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:01 h... sshd[6562]: Received disconnect from 79.247... port 52069:11: disconnected by user Oct 25 10:39:01 h... sshd[6562]: Disconnected from 79.247... port 52069 Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:01 h... systemd-logind[285]: Removed session 2373904. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session closed for user root Oct 25 10:39:02 h... sshd[6665]: Accepted publickey for root from 79.247... port 52070 ssh2: RSA SHA256:pru... Oct 25 10:39:02 h... sshd[6665]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:02 h... systemd-logind[285]: New session 2373945 of user root. Oct 25 10:39:03 h... sshd[6665]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:03 h... sshd[6665]: Received disconnect from 79.247... port 52070:11: disconnected by user Oct 25 10:39:03 h... sshd[6665]: Disconnected from 79.247... port 52070 Oct 25 10:39:03 h... sshd[6665]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:03 h... systemd-logind[285]: Removed session 2373945. To manage notifications about this bug go
[Touch-packages] [Bug 1727243] [NEW] pam_systemd
Public bug reported: my auth.log is full of messages like below. The 79.247.. is my own address and there seems to be something which tries to reconnect every other second although I am already in a running session. What is going on here? Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... port 52067 ssh2: RSA SHA256:pru... Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root. Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 52067:11: disconnected by user Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067 Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897. Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... port 52068 ssh2: RSA SHA256:pru... Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:59 h... systemd-logind[285]: New session 2373898 of user root. Oct 25 10:38:59 h... sshd[6524]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:59 h... sshd[6524]: Received disconnect from 79.247... port 52068:11: disconnected by user Oct 25 10:38:59 h... sshd[6524]: Disconnected from 79.247... port 52068 Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:59 h... systemd-logind[285]: Removed session 2373898. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... CRON[6564]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... sshd[6562]: Accepted publickey for root from 79.247... port 52069 ssh2: RSA SHA256:pru... Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:01 h... systemd-logind[285]: New session 2373904 of user root. Oct 25 10:39:01 h... sshd[6562]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:01 h... sshd[6562]: Received disconnect from 79.247... port 52069:11: disconnected by user Oct 25 10:39:01 h... sshd[6562]: Disconnected from 79.247... port 52069 Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:01 h... systemd-logind[285]: Removed session 2373904. Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session closed for user root Oct 25 10:39:02 h... sshd[6665]: Accepted publickey for root from 79.247... port 52070 ssh2: RSA SHA256:pru... Oct 25 10:39:02 h... sshd[6665]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:39:02 h... systemd-logind[285]: New session 2373945 of user root. Oct 25 10:39:03 h... sshd[6665]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:39:03 h... sshd[6665]: Received disconnect from 79.247... port 52070:11: disconnected by user Oct 25 10:39:03 h... sshd[6665]: Disconnected from 79.247... port 52070 Oct 25 10:39:03 h... sshd[6665]: pam_unix(sshd:session): session closed for user root Oct 25 10:39:03 h... systemd-logind[285]: Removed session 2373945. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1727243 Title: pam_systemd Status in systemd package in Ubuntu: New Bug description: my auth.log is full of messages like below. The 79.247.. is my own address and there seems to be something which tries to reconnect every other second although I am already in a running session. What is going on here? Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... port 52067 ssh2: RSA SHA256:pru... Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root. Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create session: Already running in a session Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 52067:11: disconnected by user Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067 Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for user root Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897. Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... port 52068 ssh2: RSA SHA256:pru... Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 25 10:38:59 h...
[Touch-packages] [Bug 1595076] Re: ubuntu 16 pwck error
Rationale: A users home directory may hold .ssh/authorized_keys and thus allow users to login without password. Thus our company has a check for those files because an unclean authorized_keys can be a big security issue. This check fails if a home directory doesn't exist. We can try to fix the check but as I stated the expectation is, that a freshly installed system wouldn't have any wrongly setup passwd file. -- 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/1595076 Title: ubuntu 16 pwck error Status in shadow package in Ubuntu: New Bug description: running pwck after installing ubuntu 16 gives an error: pwck user 'systemd-resolve': directory '/run/systemd/resolve' does not exist I think that every home directory specified in /etc/passwd must exist. If systemd-resolve has a volatile home directory I expect this directory to be created at boot time. It seems that there is no regression test before release that makes sure that no such errors are reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1595076/+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 1595076] Re: ubuntu 16 pwck error
Why was this bug marked as invalid? If a command gives a warning it shows that something is not properly implemented. Either the warning is deprecated or the cause for the warning is reasonable and the issue should be fixed. My understanding of proper programming is that every entry in /etc/passwd must have existing values. So if there is a home dir specified in /etc/passwd I expect it to exist or to be created at boot time. Ohterwise programs that may rely on the values in /etc/passwd may not work properly. ** Changed in: shadow (Ubuntu) Status: Invalid => Opinion ** Changed in: shadow (Ubuntu) Status: Opinion => New -- 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/1595076 Title: ubuntu 16 pwck error Status in shadow package in Ubuntu: New Bug description: running pwck after installing ubuntu 16 gives an error: pwck user 'systemd-resolve': directory '/run/systemd/resolve' does not exist I think that every home directory specified in /etc/passwd must exist. If systemd-resolve has a volatile home directory I expect this directory to be created at boot time. It seems that there is no regression test before release that makes sure that no such errors are reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1595076/+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 1595080] [NEW] /etc/shadow has wrong ownership
Public bug reported: I think this is identical to bug 50587 but the latter is rather old, dating from 2006. On the latest ubuntu 16.04 LTS the ownership of /etc/shadow is still not fixed. To my understanding it should be -r--r- 1 root shadow to conform to legacy programs as well and not -rw--- 1 root root as it is on a new install. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- 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/1595080 Title: /etc/shadow has wrong ownership Status in shadow package in Ubuntu: New Bug description: I think this is identical to bug 50587 but the latter is rather old, dating from 2006. On the latest ubuntu 16.04 LTS the ownership of /etc/shadow is still not fixed. To my understanding it should be -r--r- 1 root shadow to conform to legacy programs as well and not -rw--- 1 root root as it is on a new install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1595080/+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 1595076] [NEW] ubuntu 16 pwck error
Public bug reported: running pwck after installing ubuntu 16 gives an error: pwck user 'systemd-resolve': directory '/run/systemd/resolve' does not exist I think that every home directory specified in /etc/passwd must exist. If systemd-resolve has a volatile home directory I expect this directory to be created at boot time. It seems that there is no regression test before release that makes sure that no such errors are reported. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- 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/1595076 Title: ubuntu 16 pwck error Status in shadow package in Ubuntu: New Bug description: running pwck after installing ubuntu 16 gives an error: pwck user 'systemd-resolve': directory '/run/systemd/resolve' does not exist I think that every home directory specified in /etc/passwd must exist. If systemd-resolve has a volatile home directory I expect this directory to be created at boot time. It seems that there is no regression test before release that makes sure that no such errors are reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1595076/+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 1465180] [NEW] df: `/sys/kernel/debug': Function not implemented
Public bug reported: Kernel 3.2.0-85-generic #122-Ubuntu SMP Tue May 26 16:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux always gives `/sys/kernel/debug': Function not implemented when giving a df command. We have 4 machines running that kernel and all show the same issue. All other 100+ Ubuntu 12 and 14 hosts that we have don't show the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: coreutils 8.13-3ubuntu3.3 ProcVersionSignature: Ubuntu 3.2.0-85.122-generic 3.2.69 Uname: Linux 3.2.0-85-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Mon Jun 15 10:14:31 2015 MarkForUpload: True SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1465180 Title: df: `/sys/kernel/debug': Function not implemented Status in coreutils package in Ubuntu: New Bug description: Kernel 3.2.0-85-generic #122-Ubuntu SMP Tue May 26 16:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux always gives `/sys/kernel/debug': Function not implemented when giving a df command. We have 4 machines running that kernel and all show the same issue. All other 100+ Ubuntu 12 and 14 hosts that we have don't show the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: coreutils 8.13-3ubuntu3.3 ProcVersionSignature: Ubuntu 3.2.0-85.122-generic 3.2.69 Uname: Linux 3.2.0-85-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Mon Jun 15 10:14:31 2015 MarkForUpload: True SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1465180/+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
