touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

There is a suspend job running, which collides with shutting down (you
can only do one or the other). Do you know what triggered the suspend?
(lid close, indicator, or you didn't request this explicitly). Can you
reproduce this situation? Does suspend normally work for you?

The kernel log only shows that it's about to suspend, but doesn't
actually do it. That smells suspicious.

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

** Summary changed:

- poweroff no longer works
+ hanging suspend job prevents shutdown

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

Title:
  hanging suspend job prevents shutdown

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  poweroff (systemd poweroff) and reboot no longer work

  running sudo sytemd poweroff generates this:

  Failed to start poweroff.target: Transaction is destructive.

  journal log also shows:

  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
  Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

  
  Output of systemctl list-jobs
   JOB UNIT                    TYPE  STATE  
  6009 suspend.target          start waiting
  6010 systemd-suspend.service start running
  6014 anacron-resume.service  start waiting

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  7 18:32:27 2015
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.50
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions