dx-packages team mailing list archive

[Dmitry Shachnev <mitya57@xxxxxxxxx>]

rubik-cube: there are some issues with your patch:

1) Do not hardcode x86_64-linux-gnu triplet, which only works on amd64. Instead, you can use `dpkg-architecture -qDEB_HOST_MULTIARCH` for example.
2) `test -L /usr/bin/qdbus` will be *always* true, as the binary is managed by qtchooser.
3) Finally, please generate a proper debdiff with a changelog entry.

Also, please note that instead of specifying full paths to qdbus binary,
you can just run `qdbus -qt4` or `qdbus -qt5` without caring about the
paths (though not sure if it's helpful here).

Unsubscribing sponsors unless these issues are resolved.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1201180

Title:
  powerbtn.sh conflicts with logind

Status in “acpid” package in Ubuntu:
  Fix Released
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling "poweroff", but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root      4998  0.0  0.0 177932  2104 ?        Sl   20:41   0:00 /usr/lib/x86_64-linux-gnu/systemd-shim
  root      5012  0.0  0.0   4440   624 ?        S    20:41   0:00  \_ sh -c /sbin/poweroff
  root      5013  0.0  0.0   4440   628 ?        S    20:41   0:00      \_ /bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

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