from:"David Anderson"

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2018-08-24 Thread David Anderson

I thought one aspect of the bug that nobody specifically highlighted was
interesting:

dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed

Notice the replacement has an extra .systemd on the end of the name.

The fix instructions reported above worked for me.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd-shim package in Ubuntu:
  Incomplete
Status in systemd source package in Bionic:
  Confirmed
Status in systemd-shim source package in Bionic:
  Confirmed

Bug description:
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1688933] Re: systemd restart-loops logind

2017-11-20 Thread David Anderson

Does anyone have an idea how to do a temp fix job on this? For us, this
happens on an off the shelf gitlab AWS image (Ubuntu 16.04) Because the
gitlab runners ssh into the gitlab server very many times, each one of
those ssh logins needs to timeout on the login1 hand off and sometimes
it crashes the build, so it's pretty serious for us. This is our log

Nov 20 09:37:59 ip-10-159-8-x systemd[1]: Stopped Login Service.
Nov 20 09:37:59 ip-10-159-8-x systemd[1]: Starting Login Service...
Nov 20 09:38:07 ip-10-159-8-x dbus[25038]: [system] Activating systemd to 
hand-off: service name='org.freedesktop.login1' uni
t='dbus-org.freedesktop.login1.service'
Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
Nov 20 09:38:24 ip-10-159-8-x systemd[1]: Failed to start Login Service.
Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Unit entered 
failed state.
Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Failed with 
result 'exit-code'.
Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Service has 
no hold-off time, scheduling restart.
Nov 20 09:38:24 ip-10-159-8-x systemd[1]: Stopped Login Service.

many thanks
Dave

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

Title:
  systemd restart-loops logind

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Syslog logs systemd trying to restart logind every few seconds:

  May  7 00:51:29 server systemd[1]: Starting Login Service...
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:51:54 server systemd[1]: Failed to start Login Service.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:51:54 server systemd[1]: Stopped Login Service.
  May  7 00:51:54 server systemd[1]: Starting Login Service...
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:52:19 server systemd[1]: Failed to start Login Service.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:52:19 server systemd[1]: Stopped Login Service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May  7 00:51:07 2017
  InstallationDate: Installed on 2013-08-21 (1353 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago)
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DQ67OW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG12528-309
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688933/+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 1692997] [NEW] libelf test for section size in wrong place

2017-05-23 Thread David Anderson

Public bug reported:

It seems to me that the test for an invalid section size
wants be moved up from the map case to cover both the read and the map
case.

To guard against a bogus section size for both cases.
Rather than relying on a malloc failure to catch a 
completely bogus section size.  
Thus allowing a more accurate error indication.

>From elfutils_0.165.orig.tar.bz2

elfutils-0.165/libelf/elf_getdata.c


--- elf_getdata.c.orig  2017-05-23 10:56:05.547607473 -0700
+++ elf_getdata.c   2017-05-23 11:08:27.459670572 -0700
@@ -292,21 +292,20 @@
  __libelf_seterrno (ELF_E_INVALID_DATA);
  return 1;
}
+ /* First see whether the information in the section header is
+   valid and it does not ask for too much.  Check for unsigned
+   overflow.  */
+  if (unlikely (offset > elf->maximum_size
+  || elf->maximum_size - offset < size))
+{
+  /* Something is wrong.  */
+  __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
+  return 1;
+}
 
   /* We can use the mapped or loaded data if available.  */
   if (elf->map_address != NULL)
{
- /* First see whether the information in the section header is
-valid and it does not ask for too much.  Check for unsigned
-overflow.  */
- if (unlikely (offset > elf->maximum_size
- || elf->maximum_size - offset < size))
-   {
- /* Something is wrong.  */
- __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
- return 1;
-   }
-
  scn->rawdata_base = scn->rawdata.d.d_buf
= (char *) elf->map_address + elf->start_offset + offset;
}

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

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

Title:
  libelf test for section size in wrong place

Status in elfutils package in Ubuntu:
  New

Bug description:
  It seems to me that the test for an invalid section size
  wants be moved up from the map case to cover both the read and the map
  case.

  To guard against a bogus section size for both cases.
  Rather than relying on a malloc failure to catch a 
  completely bogus section size.  
  Thus allowing a more accurate error indication.

  From elfutils_0.165.orig.tar.bz2

  elfutils-0.165/libelf/elf_getdata.c

  
  --- elf_getdata.c.orig2017-05-23 10:56:05.547607473 -0700
  +++ elf_getdata.c 2017-05-23 11:08:27.459670572 -0700
  @@ -292,21 +292,20 @@
  __libelf_seterrno (ELF_E_INVALID_DATA);
  return 1;
}
  + /* First see whether the information in the section header is
  + valid and it does not ask for too much.  Check for unsigned
  + overflow.  */
  +  if (unlikely (offset > elf->maximum_size
  +  || elf->maximum_size - offset < size))
  +{
  +  /* Something is wrong.  */
  +  __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
  +  return 1;
  +}
   
 /* We can use the mapped or loaded data if available.  */
 if (elf->map_address != NULL)
{
  -   /* First see whether the information in the section header is
  -  valid and it does not ask for too much.  Check for unsigned
  -  overflow.  */
  -   if (unlikely (offset > elf->maximum_size
  -   || elf->maximum_size - offset < size))
  - {
  -   /* Something is wrong.  */
  -   __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
  -   return 1;
  - }
  -
  scn->rawdata_base = scn->rawdata.d.d_buf
= (char *) elf->map_address + elf->start_offset + offset;
}

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1692997/+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 1773859] Re: upgrades to 18.04 fail

[Touch-packages] [Bug 1688933] Re: systemd restart-loops logind

[Touch-packages] [Bug 1692997] [NEW] libelf test for section size in wrong place

3 matches

Site Navigation

Mail list logo

Footer information