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

Bug#949289: marked as done (bugs.debian.org: No wifi and no sound after suspend)

Your message dated Sun, 27 Jul 2025 16:40:55 +0200
with message-id <aIY6d10fzOTOlL4u@per.namespace.at>
and subject line Re: Bug#949289: No wifi and no sound after suspend
has caused the Debian Bug report #949289,
regarding bugs.debian.org: No wifi and no sound after suspend
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.)


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

Dear Maintainer,

Since a recent update in january WiFi and sound do no longer recover from
suspend (after closing and opening laptop lid).
Keyboard, touchpad and screen seem to be ok, but shutdown and restart
(gnomeshell) are broken as well. No reaction.
The laptop has to be restarted by hard power off.
This never happened before.
Hardware: HP Elitebook G 840

I haven't found a workaroud yet. Looks like the resume from suspend is broken,
as more than a single function is affected.

Wolf-Dieter



-- System Information:
Debian Release: 9.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-11-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Sun, Mar 21, 2021 at 08:05:01PM +0100, Bart M wrote:
> Hi Wolf-Dieter, is this bug for "oldstable", as mentioned in the system info on
> the initial bug report? Does the problem also happen on stable=buster and
> testing=bullseye?

Closing for lack of more info.

Chris

--- End Message ---
Reply to: