Your message dated Thu, 08 Mar 2007 14:16:57 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410818: s2ram's stderr output needs to be sent to /dev/null
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: hal
Version: 0.5.8.1-6
Severity: normal
s2ram by default outputs a lot of stuff to stderr. This makes HAL (at
least gnome-power-manager) think that the command was not successful,
even though it returns an exit status of 0. A simple 2>/dev/null after
s2ram makes gnome-power-manager stop complaining. :-)
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.1
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Versions of packages hal depends on:
ii adduser 3.102 Add and remove users and groups
ii dbus 1.0.2-1 simple interprocess messaging syst
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.71-3 simple interprocess messaging syst
ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li
ii libglib2.0-0 2.12.6-2 The GLib library of C routines
ii libhal-storage1 0.5.8.1-6 Hardware Abstraction Layer - share
ii libhal1 0.5.8.1-6 Hardware Abstraction Layer - share
ii libusb-0.1-4 2:0.1.12-4 userspace USB programming library
ii libvolume-id0 0.103-2 libvolume_id shared library
ii lsb-base 3.1-23 Linux Standard Base 3.1 init scrip
ii pciutils 1:2.2.4-1 Linux PCI Utilities
ii udev 0.103-2 /dev/ and hotplug management daemo
ii usbutils 0.72-7 USB console utilities
Versions of packages hal recommends:
ii eject 2.1.4-2.1 ejects CDs and operates CD-Changer
-- no debconf information
--- End Message ---
--- Begin Message ---
Steinar H. Gunderson wrote:
> Package: hal
> Version: 0.5.8.1-6
> Severity: normal
>
> s2ram by default outputs a lot of stuff to stderr. This makes HAL (at
> least gnome-power-manager) think that the command was not successful,
> even though it returns an exit status of 0. A simple 2>/dev/null after
> s2ram makes gnome-power-manager stop complaining. :-)
>
I can't confirm this behaviour:
Adding this to hal-system-power-suspend-linux
echo "stderr" >&2
echo "stdout"
exit 1
Triggers the warning/failure message in g-p-m. The echo message (return
messag) is actually not necessary and not used/displayed in g-p-m at all.
This:
echo "stderr" >&2
echo "stdout"
exit 0
Gives me no error message in g-p-m.
So, the output to stdout/stderr is not the deciding factor, only the
return code.
But then again, I tested with g-p-m 2.16 from experimental. Maybe g-p-m
from unstable does not check the return code but the return message. If
so it is a fault in g-p-m in unstable.
Closing this bug. If you think this is a problem in g-p-m please reopen
and reassign the bug accordingly.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
