Your message dated Mon, 06 Nov 2006 10:23:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397120: uswsusp: s2disk wants to run /usr/sbin/grubonce
which doesn't exist
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: uswsusp
Severity: normal
>From the log file:
...
checking ndiswrapper
------------------------------------------------------------------------------
prepare_sleep finished for suspend2disk
------------------------------------------------------------------------------
preparing boot-loader: selecting entry 0, kernel /boot/2.6.18-1-686
/usr/sbin/grubonce not found, not preparing bootloader
time needed for sync: 0.5 seconds, time needed for grub: 0.0 seconds.
calculated image_size: 500
========we are back from suspend, cleaning up.========
...
This binary doesn't seem to exist in Debian at all. If it's needed it
has to be available, if not, it shouldn't be called.
Michael
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Michael Meskes wrote:
>> I don't quite see the problem (or bug) here. If grubonce exists,
>
> Why not?
>
>> powersaved makes use of it, otherwise not. It's not that suspend_to_disk
>> fails, if grubonce does not exist. powersaved just writes to the log
>
> True, but definitely not clear to the user. If something doens't work,
> the first thing a user does is/should be looking into the log. Seeing an
> error message there at least suggests that this is the reason for
> his/her problems.
>
>> file, that it didn't find grubonce. I can see nothing wrong with that.
>> Could you please elaborate? Otherwise I'm going to close this bug report.
>
> Having a package printing an error message because of a missing binary
> is definitely not a correct behaviour. Especially if that binary is not
Huh? It's not an error message. powersaved is just printing exactly,
what it is doing:
preparing boot-loader: selecting entry 1, kernel /boot/2.6.19-rc4
/usr/sbin/grubonce not found, not preparing bootloader
time needed for sync: 0.2 seconds, time needed for grub: 0.0 seconds.
> available at all in Debian. Since it's not needed you could simply call
> true instead or just patch out the call.
Patching out the above message might leave the user in the false
impression, that powersaved is mangling with the grub settings, which it
does not, if grubonce is not available.
> I can see no reason however to just close the report.
Given the above reasoning, I think removing the log message entry makes
things worse. Closing this bug report.
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 ---
