[Bug 1945202] [NEW] Tar changes folder ownership when run under root
Public bug reported: I got locked out of my server via SSH, simply by extracting a tar file. No matter how crazy it sounds, it is reproducible. 1. login as root 2. wget https://github.com/aristocratos/btop/releases/download/v1.0.9/btop-1.0.9-linux-x86_64.tbz` 3. tar -xjvf btop-1.0.9-linux-x86_64.tbz` At this point the /root folder has ownership of user:user (1000:1000) and the root is locked out from SSH login. I had to fix the server via KVM. auth.log contained the following: "Authentication refused: bad ownership or modes for directory /root" This seems to be a bug in tar, as the above behaviour doesn't happen when logged in under any non-root user. With non-root users the directory does not change ownership. With root user, no matter where I extract the tar file, the directory changes ownership. --- lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 apt-cache policy tar tar: Installed: 1.29b-2ubuntu0.2 Candidate: 1.29b-2ubuntu0.2 ** Affects: tar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945202 Title: Tar changes folder ownership when run under root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1945202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctls are ignored on boot
I feel it's important to add that the very last comment (Stanley Sisneros (stanley-sisneros) wrote on 2018-05-30) is wrong, and the right workaround is by Tomasz Konefal (twkonefal-j) wrote on 2018-05-07. That is, add this to crontab: @reboot root sleep 5 && sysctl --system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctls are ignored on boot
Actually, the line which works without specifying a PATH in a cron.d file is the following: @reboot root /bin/sleep 5 && /sbin/sysctl --system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645002] [NEW] ssh sessions are not cleanly terminated on shutdown/restart with systemd
Public bug reported: In Ubuntu 16.04, a "reboot" command does not terminate the ssh session. This results in clients hanging, until timing out (sometimes as much as 120 seconds). This also introduces bugs to all orchestration / automation tools which work over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 hosts. For example, have a look at this issue for Fabric: https://github.com/fabric/fabric/issues/1488 The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. There is a very detailed discussion in their bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645002 Title: ssh sessions are not cleanly terminated on shutdown/restart with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1645002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644996] [NEW] logrotate config uses syslog group
Public bug reported: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980312] [NEW] libssl0.9.8o-7ubuntu1 works with Aventail; libssl0.9.8o-7ubuntu2 breaks it
Public bug reported: cannot install my Aventail client in Kubuntu 12.04 because it does not like 12.04's version of libssl.0.9.8. Although Aventail will install without complaining when 0.9.8o-7ubuntu1 is installed, it's a different story with 0.9.8o-7ubuntu2, the version that 12.04 wants to install. With 0.9.8o-7ubuntu2, I get the following errors: Code: linux-gate.so.1 = (0xb77c7000) libpthread.so.0 = /lib/i386-linux-gnu/libpthread.so.0 (0xb7798000) libssl.so.0.9.7 = not found libcrypto.so.0.9.7 = not found libm.so.6 = /lib/i386-linux-gnu/libm.so.6 (0xb776b000) libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xb75c5000) /lib/ld-linux.so.2 (0xb77c8000) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libssl0.9.8 0.9.8o-7ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 12 14:18:16 2012 InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120228.1) ProcEnviron: LANGUAGE= TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl098 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl098 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980312 Title: libssl0.9.8o-7ubuntu1 works with Aventail; libssl0.9.8o-7ubuntu2 breaks it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl098/+bug/980312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980312] Re: libssl0.9.8o-7ubuntu1 works with Aventail; libssl0.9.8o-7ubuntu2 breaks it
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980312 Title: libssl0.9.8o-7ubuntu1 works with Aventail; libssl0.9.8o-7ubuntu2 breaks it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl098/+bug/980312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192366] Re: Smartcard reader not working (CASTLES EZ100PU)
Hi! After a long long time ago with this problem I found a solution! In this web are the solution: http://starryalley.twbbs.org/blog/index.php?/archives/1149-Thank-you-E .Sun-Bank.I-can-use-WebATM-on-Linux!.html I use ubuntu 9.04 amd64 and it's work -- Smartcard reader not working (CASTLES EZ100PU) https://bugs.launchpad.net/bugs/192366 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 301659] Re: memtest update problem
*** This bug is a duplicate of bug 252900 *** https://bugs.launchpad.net/bugs/252900 Thanks -- From: Jean-Baptiste Lallement [EMAIL PROTECTED] Sent: Thursday, November 27, 2008 11:49 PM To: [EMAIL PROTECTED] Subject: [Bug 301659] Re: memtest update problem *** This bug is a duplicate of bug 252900 *** https://bugs.launchpad.net/bugs/252900 Thanks for your feedback. Sadly, symlinks are not supported on fat filesystems a workaround is to use ntfs instead but it's not always possible depending on your system setup. This has already been reported and I'm marking this report as duplicate of bug 252900. Thank you and don't hesitate to submit any new bug. ** Changed in: memtest86+ (Ubuntu) Status: Incomplete = Confirmed ** This bug has been marked a duplicate of bug 252900 vfat : wubi 8.04.1-rev506 kernel upgrade fails -- memtest update problem https://bugs.launchpad.net/bugs/301659 You received this bug notification because you are a direct subscriber of the bug. Status in “memtest86+” source package in Ubuntu: Confirmed Bug description: Binary package hint: memtest86+ Hello, When I whant to update my Ubuntu 8.10, I get this error : E: /var/cache/apt/archives/memtest86+_2.01-1ubuntu2_i386.deb: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version Thanks for help ProblemType: Package Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 ErrorMessage: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version: Opération non permise Package: memtest86+ 1.70-3ubuntu1 SourcePackage: memtest86+ Title: package memtest86+ 1.70-3ubuntu1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version: Opération non permise Uname: Linux 2.6.27-7-generic i686 -- memtest update problem https://bugs.launchpad.net/bugs/301659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 301659] Re: memtest update problem
Yes, it is a wubi install. The file system /boot is FAT 32 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 25 Nov 2008 15:09:15 + Subject: [Bug 301659] Re: memtest update problem Thanks for your report. Is it a wubi install ? What is the filesystem type of /boot ? This is very likely a dup of bug 252900. Thanks in advance. ** Changed in: memtest86+ (Ubuntu) Status: New = Incomplete -- memtest update problem https://bugs.launchpad.net/bugs/301659 You received this bug notification because you are a direct subscriber of the bug. Status in “memtest86+” source package in Ubuntu: Incomplete Bug description: Binary package hint: memtest86+ Hello, When I whant to update my Ubuntu 8.10, I get this error : E: /var/cache/apt/archives/memtest86+_2.01-1ubuntu2_i386.deb: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version Thanks for help ProblemType: Package Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 ErrorMessage: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version: Opération non permise Package: memtest86+ 1.70-3ubuntu1 SourcePackage: memtest86+ Title: package memtest86+ 1.70-3ubuntu1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version: Opération non permise Uname: Linux 2.6.27-7-generic i686 _ Email envoyé avec Windows Live Hotmail. Dites adieux aux spam et virus, passez à Hotmail ! C'est gratuit ! http://www.windowslive.fr/hotmail/default.asp -- memtest update problem https://bugs.launchpad.net/bugs/301659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301659] [NEW] memtest update problem
Public bug reported: Binary package hint: memtest86+ Hello, When I whant to update my Ubuntu 8.10, I get this error : E: /var/cache/apt/archives/memtest86+_2.01-1ubuntu2_i386.deb: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version Thanks for help ProblemType: Package Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 ErrorMessage: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version: Opération non permise Package: memtest86+ 1.70-3ubuntu1 SourcePackage: memtest86+ Title: package memtest86+ 1.70-3ubuntu1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./boot/memtest86+.bin » avant d'installer une nouvelle version: Opération non permise Uname: Linux 2.6.27-7-generic i686 ** Affects: memtest86+ (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- memtest update problem https://bugs.launchpad.net/bugs/301659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301659] Re: memtest update problem
** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/19903154/DpkgTerminalLog.txt -- memtest update problem https://bugs.launchpad.net/bugs/301659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
