[Pkg-utopia-maintainers] Bug#744743: dbus: Does not suspend laptop anymore after first suspend since boot time.

[Simon McVittie]

reassign 744743 upower
thanks

On 14/04/14 09:00, Sthu wrote:
> $ /usr/bin/dbus-send --system --print-reply --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend
> 
> works only once after boot time, then on resume, it will never suspend my laptop, giving this error:
> 
> Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
> Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply,
> the reply timeout expired, or the network connection was broken.

Of the possible reasons cited in the error message:

* "the remote application did not send a reply" is possible; if that's
  what happened, it would be UPower's fault.

* "the message bus security policy blocked the reply" seems unlikely:
  if it worked once, it's likely to work again. However, if this is what
  happened, you will see messages in /var/log/auth.log (or wherever your
  syslog puts LOG_AUTHPRIV messages). They look something like this,
  and in particular, "matched rules" is a good thing to grep for:

  Apr 14 09:18:07 archetype dbus[1323]: [system] Rejected send message,
  1 matched rules; type="method_call", sender=":1.6051" (uid=1000
  pid=10845 comm="dbus-send --system --print-reply --dest=org.freede")
  interface="com.example" member="Hello" error name="(unset)"
  requested_reply="0" destination="org.freedesktop.UPower" (uid=0
  pid=1320 comm="/usr/lib/upower/upowerd ")

* "the reply timeout expired" is pretty generic: the reply didn't
  get there for some unspecified reason. If D-Bus is otherwise working
  normally, this is unlikely to be dbus' fault, and more likely to
  be upower not replying to the message.

* "the network connection was broken" is extremely unlikely, since
  the system dbus-daemon uses a Unix socket.

So I'm reassigning this to upower. Please reply to the bug address with
the information from "reportbug --template upower". The maintainers of
upower will probably also ask you for log/debug information from upower
itself; I don't know how to obtain that.

Regards,
    S

> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing-updates
>   APT policy: (700, 'testing-updates'), (700, 'testing'), (600,
'stable-updates'), (600, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages dbus depends on:
> ii  adduser              3.113+nmu3
> ii  libaudit1            1:2.3.4-1
> ii  libc6                2.18-4
> ii  libcap-ng0           0.7.3-1+b1
> ii  libdbus-1-3          1.8.0-3
> ii  libexpat1            2.1.0-4
> ii  libselinux1          2.2.2-1
> ii  libsystemd-journal0  204-8
> ii  libsystemd-login0    204-8
> ii  lsb-base             4.1+Debian12
>
> dbus recommends no packages.
>
> Versions of packages dbus suggests:
> ii  dbus-x11  1.8.0-3
>
> -- no debconf information