[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#577054: marked as done (acpi: After upgrade, computer does not turn off)

Your message dated Sun, 2 Oct 2011 14:35:37 -0500
with message-id <20111002193537.GB17331@elie>
and subject line Re: acpi: After upgrade, computer does not turn off
has caused the Debian Bug report #577054,
regarding acpi: After upgrade, computer does not turn off
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
577054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577054
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: acpi
Version: 1.4-2
Severity: important


After the upgrade that happened around 2010-03-04 or 2010-03-22, the
computer does not turn off after shutdown procedure.  The disk spins down,
the kernel says 'Power down' and I must push the box's turn off button for
it to shutdown.

Happy to provide more info as requested...

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (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 acpi depends on:
ii  libc6                         2.10.2-6   Embedded GNU C Library: Shared lib

acpi recommends no packages.

acpi suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Γιώργος Πάλλας wrote:

> Hi!
> This goes so much time in the past that I don't remember anything about
> the case. Since then I followed the regular squeeze upgrades and the
> problem vanished at some point. So there is none of the data you
> requested available!

Drat. :)  Please do still send output from

	/usr/share/bug/linux-image-$(uname -r)/script 3>&1

and dmesg output from just after booting (you can probably find the
latter in /var/log/kern.log* somewhere) for reference, so we can
understand what happened better and prevent it from happening again.

Any other observations (e.g., around which month you remember it being
fixed, if you remember) would also still be welcome.

Thanks for the update,
Jonathan

--- End Message ---
Reply to: