Your message dated Sun, 30 Aug 2020 13:51:13 +0200 with message-id <[🔎] 20200830135113.4d1618cbb70489127e6e3254@mailbox.org> and subject line Re: Mass-closing old installation-report bugs --- round 7 has caused the Debian Bug report #784751, regarding Hibernation does not work using "tweak tool" (Power - power button action - hibernate) 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.) -- 784751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784751 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: OS: Jessie amd64, hardware: W650SZ-i7. Hibernation works with "sudo hibernate", but does not work properly, when configured via the "tweak tool" (Power - power button action - hibernate). This is probably a hardware issue, since hibernation works on a Lenovo T410s laptop (using the configured power button and the fn+F12 key). Best regards, François P. Rotzinger
- From: François P. Rotzinger <Am843@gmx.ch>
- Date: Fri, 08 May 2015 15:22:07 +0200
- Message-id: <20150508132207.4226.23429.reportbug@lpipc12>
Package: none Version: hibernate Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Pressing the Power button (configured as "hibernate" with "tweak tool"). * What exactly did you do (or not do) that was effective (or ineffective)? "sudo hibernate" works, pressing the power button hibernates the computer, but it does wake up properly in most cases. * What was the outcome of this action? Waking up in most cases takes place, but subsequently, the machine reboots, and an "fsck" is executed. * What outcome did you expect instead? That it resumes normally from hibernation as after "sudo hibernate". This is probably a hardware-dependent issue, since this works fine on a Lenovo T410s laptop (hibernation works using fn+F12 and using the power button configured with "tweak tool"). -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
- To: debian-boot@lists.debian.org
- Cc: 731720-done@bugs.debian.org, 739986-done@bugs.debian.org, 751973-done@bugs.debian.org, 759606-done@bugs.debian.org, 782798-done@bugs.debian.org, 784751-done@bugs.debian.org, 795507-done@bugs.debian.org, 798282-done@bugs.debian.org, 841236-done@bugs.debian.org, 865032-done@bugs.debian.org, 865562-done@bugs.debian.org, 962701-done@bugs.debian.org
- Subject: Re: Mass-closing old installation-report bugs --- round 7
- From: Holger Wansing <hwansing@mailbox.org>
- Date: Sun, 30 Aug 2020 13:51:13 +0200
- Message-id: <[🔎] 20200830135113.4d1618cbb70489127e6e3254@mailbox.org>
- In-reply-to: <[🔎] 20200804000901.ada4d3e7ac8e2e0050ab3eb3@mailbox.org>
- References: <[🔎] 20200804000901.ada4d3e7ac8e2e0050ab3eb3@mailbox.org>
Hi, Holger Wansing <hwansing@mailbox.org> wrote: > > I'm closing the reports below. > > That's installation-reports for Debian 7 with > - undefined errors > - problems which are likely to have been fixed in the meantime > - successful installation > > Because of the age, there is no chance to analyse them further and therefore > they are no longer relevant or of any use for current releases: And thank you for filing these installation bug reports, they have been very useful at the time they were filed! If you know, that the issue you reported (and gets closed here) is still existing in recent installation images, please file a new report for that! round 7 (some reports I overlooked recently): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731720 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739986 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751973 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759606 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782798 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784751 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795507 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798282 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841236 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865032 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865562 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962701 -- Holger Wansing <hwansing@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---