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

Bug#900438: marked as done (general: fails to hibernate correctly)

Your message dated Fri, 08 Jun 2018 09:34:47 +0200
with message-id <87in6tzq7c.fsf@hands.com>
and subject line Re: Bug#900438: general: fails to hibernate correctly
has caused the Debian Bug report #900438,
regarding general: fails to hibernate correctly
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.)


-- 
900438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900438
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: general
Severity: important

Dear Maintainer,

Anytime I try to hibernate my laptop the process of hibernation starts, the
screen turns black, (not turned off, it shows a black background with an active
light), and just stays like that forever.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Ralph, Hi Rolando,

Ralph Boland <rpboland@gmail.com> writes:

> Package: general
> Followup-For: Bug #900438
>
> Dear Maintainer,
>
> Problems began when I upgraded from Debian 8.x  to Debian 9.4.

There seems to be no common ground between the behaviour that you are
reporting, and the bug you've followed up to.  One is about a failure to
suspend, and the other is about problems with subsequently restoring.

Also, both of these problems are almost certainly due to very specific
features of your particular combination of hardware, configuration and
software.

I would therefore suggest that you ask for help on the normal support
channels (i.e. debian-user@lists.debian.org and #debian on IRC -- see
the wiki for more info: https://www.debian.org/support).

Hopefully you will then get advice on how to diagnose your problem,
which will either point towards configuration changes required, or might
reveal a bug in a particular package.

Bugs against particular packages are _much_ more likely to get fixed
than bugs against 'general', so please don't be discouraged from
reporting them by the fact that I'm now going to close this bug.  I'm
doing that because it's not really actionable as it stands.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/    http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,    GERMANY

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: