Hello,
I have patiently submitted, resubmitted and submitted again. This bug is DEFINITELY a security issue. Also, it seems quite odd that a 'stable' release has such an easy to find bug in the basic operation of the OS. I am NOT a software developer by any means. Also, this is not a 'criticism', rather, it is a statement of my surprise. The following is the bug report I wrote the second time, as the fist one did not include my answers in it and I didn't know where it was to be found. I have seen a similar report to this on line, I certainly hope that you will find the information useful.
Here it is:
Subject: tech-ctte: failure to suspend session or lock computer
Package: tech-ctte
Justification: must
Severity: serious
Tags: security
Dear Maintainer,
* Q: What led up to the situation? A: attempt to lock, suspend or hibernate the sytemt to NOT shut down entirely.
* Q: What exactly did you do (or not do) that was effective (or
ineffective)? A: I attempted the three mentioned options.
* Q: What was the outcome of this action? A: forced restart in all cases, resulting on fallback to journaled entries.
* Q: What outcome did you expect instead? I expected those functions to... function.
-- System Information:
Debian Release: 8.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/6 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)
the page I listed my issue on line is:
| | | | lock screen & session suspension in Debian Jessie I just read of an issue that seemed similar to mine, and as I cannot comment yet and my problem is different I w... | | | |