[Touch-packages] [Bug 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root

2020-12-09 Thread Darxus 
** Changed in: systemd (Ubuntu)
   Status: Expired => 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/1891394

Title:
  systemd breaks upgrade with useless error if /var is not owned by root

Status in systemd package in Ubuntu:
  New

Bug description:
  I just upgraded from 16.04 to 18.04.  The upgrade broke.  The error,
  from systemd, was:

  "Unsafe symlinks encountered in /var/log/journal, refusing."

  That directory was empty.  The fix was "chmod root:root /var".  Yes,
  it's weird that my /var wasn't owned by root, but upgrade breaking
  errors should say something useful.

  panic:~# chown darxus:darxus /var
  panic:~# dpkg-reconfigure systemd
  Unsafe symlinks encountered in /var/spool/rsyslog, refusing.
  Unsafe symlinks encountered in /var/lib/colord, refusing.
  Unsafe symlinks encountered in /var/lib/colord/icc, refusing.
  Unsafe symlinks encountered in /var/cache/man, refusing.
  Unsafe symlinks encountered in /var/run/opendkim, refusing.
  Unsafe symlinks encountered in /var/lib/systemd, refusing.
  Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
  Unsafe symlinks encountered in /var/log/wtmp, refusing.
  Unsafe symlinks encountered in /var/log/btmp, refusing.
  Unsafe symlinks encountered in /var/log/lastlog, refusing.
  Unsafe symlinks encountered in /var/log, refusing.
  Unsafe symlinks encountered in /var/log/auth.log, refusing.
  Unsafe symlinks encountered in /var/log/mail.err, refusing.
  Unsafe symlinks encountered in /var/log/mail.log, refusing.
  Unsafe symlinks encountered in /var/log/kern.log, refusing.
  Unsafe symlinks encountered in /var/log/syslog, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
  panic:~# chown root:root /var
  panic:~# dpkg-reconfigure systemd

  I found the fix here: https://askubuntu.com/a/1095796
  Showing that I'm not the only one encountering this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.42
  Uname: Linux 5.6.14-x86_64-linode135 x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: i386
  Date: Wed Aug 12 15:58:33 2020
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: root=/dev/sda console=tty1 console=ttyS0 ro  
devtmpfs.mount=1
  ProcModules:
   
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2020-08-12 (0 days ago)
  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-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+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 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root

2020-10-10 Thread Darxus 
Var was owned by the user I usually log in as.  I don't know why, yes
it's weird, I fixed it.  I don't think that justifies this package's
upgrade braking behavior.

-- 
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/1891394

Title:
  systemd breaks upgrade with useless error if /var is not owned by root

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded from 16.04 to 18.04.  The upgrade broke.  The error,
  from systemd, was:

  "Unsafe symlinks encountered in /var/log/journal, refusing."

  That directory was empty.  The fix was "chmod root:root /var".  Yes,
  it's weird that my /var wasn't owned by root, but upgrade breaking
  errors should say something useful.

  panic:~# chown darxus:darxus /var
  panic:~# dpkg-reconfigure systemd
  Unsafe symlinks encountered in /var/spool/rsyslog, refusing.
  Unsafe symlinks encountered in /var/lib/colord, refusing.
  Unsafe symlinks encountered in /var/lib/colord/icc, refusing.
  Unsafe symlinks encountered in /var/cache/man, refusing.
  Unsafe symlinks encountered in /var/run/opendkim, refusing.
  Unsafe symlinks encountered in /var/lib/systemd, refusing.
  Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
  Unsafe symlinks encountered in /var/log/wtmp, refusing.
  Unsafe symlinks encountered in /var/log/btmp, refusing.
  Unsafe symlinks encountered in /var/log/lastlog, refusing.
  Unsafe symlinks encountered in /var/log, refusing.
  Unsafe symlinks encountered in /var/log/auth.log, refusing.
  Unsafe symlinks encountered in /var/log/mail.err, refusing.
  Unsafe symlinks encountered in /var/log/mail.log, refusing.
  Unsafe symlinks encountered in /var/log/kern.log, refusing.
  Unsafe symlinks encountered in /var/log/syslog, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
  panic:~# chown root:root /var
  panic:~# dpkg-reconfigure systemd

  I found the fix here: https://askubuntu.com/a/1095796
  Showing that I'm not the only one encountering this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.42
  Uname: Linux 5.6.14-x86_64-linode135 x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: i386
  Date: Wed Aug 12 15:58:33 2020
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: root=/dev/sda console=tty1 console=ttyS0 ro  
devtmpfs.mount=1
  ProcModules:
   
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2020-08-12 (0 days ago)
  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-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+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 1895686] Re: blkid always hangs, launched by dpkg --configure -a

2020-09-15 Thread Darxus 
** Description changed:

  I noticed last night that package install fails.  Then I noticed
- processes running from an automatic upgrade that ran on September 9th.
+ processes running from an automatic upgrade that ran on September first.
  Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
  When I run the same command manually through strace, it seems to get
  hung on opening the floppy drive, which does not exist:
  
  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779
  
  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
  
  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.
  
  https://ubuntuforums.org/showthread.php?t=2450510
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895686

Title:
  blkid always hangs, launched by dpkg --configure -a

Status in util-linux package in Ubuntu:
  New

Bug description:
  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September
  first.  Whenever I run "dpkg --configure -a", it gets stuck on blkid
  hanging.  When I run the same command manually through strace, it
  seems to get hung on opening the floppy drive, which does not exist:

  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779

  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC

  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.

  https://ubuntuforums.org/showthread.php?t=2450510

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+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 1895686] Re: blkid always hangs, launched by dpkg --configure -a

2020-09-15 Thread Darxus 
** Attachment added: "Full output of that strace"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+attachment/5411074/+files/blkid.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895686

Title:
  blkid always hangs, launched by dpkg --configure -a

Status in util-linux package in Ubuntu:
  New

Bug description:
  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September
  first.  Whenever I run "dpkg --configure -a", it gets stuck on blkid
  hanging.  When I run the same command manually through strace, it
  seems to get hung on opening the floppy drive, which does not exist:

  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779

  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC

  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.

  https://ubuntuforums.org/showthread.php?t=2450510

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+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 1895686] [NEW] blkid always hangs, launched by dpkg --configure -a

2020-09-15 Thread Darxus 
Public bug reported:

I noticed last night that package install fails.  Then I noticed
processes running from an automatic upgrade that ran on September first.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
hung on opening the floppy drive, which does not exist:

# strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
b6a3-888f7368c779

...
lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
access("/dev/fd0", F_OK)= 0
stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
close(4)= 0
openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC

This bug was submitted by running ubuntu-bug on one of the hung
instances of blkid.

https://ubuntuforums.org/showthread.php?t=2450510

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: util-linux 2.34-0.1ubuntu9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Sep 15 10:18:23 2020
ExecutablePath: /sbin/blkid
InstallationDate: Installed on 2016-05-28 (1571 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September 9th.
  Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
  When I run the same command manually through strace, it seems to get
  hung on opening the floppy drive, which does not exist:
  
  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779
  
  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
  
+ https://ubuntuforums.org/showthread.php?t=2450510
  
- https://ubuntuforums.org/showthread.php?t=2450510
+ This bug was submitted by running ubuntu-bug on one of the hung
+ instances of blkid.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

** Description changed:

  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September 9th.
  Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
  When I run the same command manually through strace, it seems to get
  hung on opening the floppy drive, which does not exist:
  
  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779
  
  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
  
- https://ubuntuforums.org/showthread.php?t=2450510
- 
  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.
+ 
+ https://ubuntuforums.org/showthread.php?t=2450510
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2

[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot

2020-08-15 Thread Darxus 
I think I had the same problem.  I think it was fixed with "chown
root:root /var".

Related to this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394

I think it also caused screen to be unusable until it was run by root.

-- 
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/1811580

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Expired

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caught by it in the middle of setting up a new server
  yesterday, and it took a whole day to find the source.

  The appropriate fix would be to ensure that systemd can successfully
  'start ssh.service' even when 'UsePrivilegeSeparation yes' is set.
  systemd needs to test that /var/run/sshd/ exists before starting sshd,
  just as the init.d script for sshd does. openssl could also be patched
  so that UsePrivilegeSeparation is no longer enabled by default,
  however that is not going to solve the problem for millions of pre-
  existing config files. Only an update to openssl to force-override
  that flag to 'no' would solve the problem. Thus systemd still needs to
  be responsible for ensuring that it inits sshd properly by ensuring
  that /var/run/sshd/ exists before it sends the 'start' command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 1891394] [NEW] systemd breaks upgrade with useless error if /var is not owned by root

2020-08-12 Thread Darxus 
Public bug reported:

I just upgraded from 16.04 to 18.04.  The upgrade broke.  The error,
from systemd, was:

"Unsafe symlinks encountered in /var/log/journal, refusing."

That directory was empty.  The fix was "chmod root:root /var".  Yes,
it's weird that my /var wasn't owned by root, but upgrade breaking
errors should say something useful.

panic:~# chown darxus:darxus /var
panic:~# dpkg-reconfigure systemd
Unsafe symlinks encountered in /var/spool/rsyslog, refusing.
Unsafe symlinks encountered in /var/lib/colord, refusing.
Unsafe symlinks encountered in /var/lib/colord/icc, refusing.
Unsafe symlinks encountered in /var/cache/man, refusing.
Unsafe symlinks encountered in /var/run/opendkim, refusing.
Unsafe symlinks encountered in /var/lib/systemd, refusing.
Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
Unsafe symlinks encountered in /var/log/wtmp, refusing.
Unsafe symlinks encountered in /var/log/btmp, refusing.
Unsafe symlinks encountered in /var/log/lastlog, refusing.
Unsafe symlinks encountered in /var/log, refusing.
Unsafe symlinks encountered in /var/log/auth.log, refusing.
Unsafe symlinks encountered in /var/log/mail.err, refusing.
Unsafe symlinks encountered in /var/log/mail.log, refusing.
Unsafe symlinks encountered in /var/log/kern.log, refusing.
Unsafe symlinks encountered in /var/log/syslog, refusing.
Unsafe symlinks encountered in /var/log/journal, refusing.
Unsafe symlinks encountered in /var/log/journal, refusing.
Unsafe symlinks encountered in /var/log/journal, refusing.
Unsafe symlinks encountered in /var/log/journal, refusing.
Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
panic:~# chown root:root /var
panic:~# dpkg-reconfigure systemd

I found the fix here: https://askubuntu.com/a/1095796
Showing that I'm not the only one encountering this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.42
Uname: Linux 5.6.14-x86_64-linode135 x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: i386
Date: Wed Aug 12 15:58:33 2020
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcKernelCmdLine: root=/dev/sda console=tty1 console=ttyS0 ro  devtmpfs.mount=1
ProcModules:
 
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2020-08-12 (0 days ago)
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-q35-3.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-3.1
dmi.sys.vendor: QEMU

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386

-- 
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/1891394

Title:
  systemd breaks upgrade with useless error if /var is not owned by root

Status in systemd package in Ubuntu:
  New

Bug description:
  I just upgraded from 16.04 to 18.04.  The upgrade broke.  The error,
  from systemd, was:

  "Unsafe symlinks encountered in /var/log/journal, refusing."

  That directory was empty.  The fix was "chmod root:root /var".  Yes,
  it's weird that my /var wasn't owned by root, but upgrade breaking
  errors should say something useful.

  panic:~# chown darxus:darxus /var
  panic:~# dpkg-reconfigure systemd
  Unsafe symlinks encountered in /var/spool/rsyslog, refusing.
  Unsafe symlinks encountered in /var/lib/colord, refusing.
  Unsafe symlinks encountered in /var/lib/colord/icc, refusing.
  Unsafe symlinks encountered in /var/cache/man, refusing.
  Unsafe symlinks encountered in /var/run/opendkim, refusing.
  Unsafe symlinks encountered in /var/lib/systemd, refusing.
  Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
  Unsafe symlinks encountered in /var/log/wtmp, refusing.
  Unsafe symlinks encountered in /var/log/btmp, refusing.
  Unsafe symlinks encountered in /var/log/lastlog, refusing.
  Unsafe symlinks encountered in /var/log, refusing.
  Unsafe symlinks encountered in /var/log/auth.log, refusing.
  Unsafe symlinks encountered in /var/log/mail.err, refusing.
  Unsafe symlinks encountered in /var/log/mail.log, refus

[Touch-packages] [Bug 1436558] Re: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of pa

2015-10-20 Thread Darxus 
I'm not certain I had the same problem, but the workaround I used was:

dpkg --force-depends -r purge libldap-2.4-2:amd64 libldap-2.4-2:i386
apt-get -f install

Because apt-get purge refuses due to dependencies.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1436558

Title:
  package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade:
  trying to overwrite shared '/etc/ldap/ldap.conf', which is different
  from other instances of package libldap-2.4-2:amd64

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap package in Debian:
  Confirmed

Bug description:
  package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade:
  Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes
  libldap-2.4-2:amd64 ist

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libldap-2.4-2 2.4.31-1+nmu2ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Wed Mar 25 16:48:52 2015
  DuplicateSignature: package:libldap-2.4-2:2.4.31-1+nmu2ubuntu8:Versuch, 
gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches verschieden 
von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libldap-2.4-2:amd64 ist
  InstallationDate: Installed on 2014-11-23 (122 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  SourcePackage: openldap
  Title: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: 
Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ldap.ldap.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1436558/+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 565364] Re: pinning a specific package does not work

2015-08-12 Thread Darxus 
Nice, that (debian) bug is 10 years old.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/565364

Title:
  pinning a specific package does not work

Status in apt package in Ubuntu:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  Binary package hint: apt

  "Package: *" in /etc/apt/preferences works for pinning as expected.
  "Package: nano" should work, but currently does not.  This is already
  known in Debian (c.f. http://bugs.debian.org/317186).  Setting this
  ticket to confirmed.

  Specifying only part of the package name is currently unsupported.
  There is an RFE ticket in Debian to include support for this:
  http://bugs.debian.org/121132 which is tracked in LP bug 399474

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/565364/+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