Bug#839560: marked as done (tech-ctte: failure to suspend sesion or lock computer)
Your message dated Sun, 2 Oct 2016 13:18:52 -0700
with message-id <20161002201852.62dmuzwfvumyuyno@qor.donarmstrong.com>
and subject line Re: Bug#839560: tech-ctte: failure to suspend sesion or lock computer
has caused the Debian Bug report #839560,
regarding tech-ctte: failure to suspend sesion or lock computer
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.)
--
839560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839560
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tech-ctte
Severity: serious
Tags: security
Justification: must
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)
--- End Message ---
--- Begin Message ---
On Sat, 01 Oct 2016, Timothy Danielson wrote:
> 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.
The Technical Committee isn't the group which is responsible for this
particular issue.
You should ask debian-user@lists.debian.org for assistance in finding
the proper package to file your bug against. [Possible gnome, or
something else; unfortunately, you did not include enough detail in your
bug report for me to even guess.]
--
Don Armstrong https://www.donarmstrong.com
"That is why I am still tyrant of [Ankh-Morpork]. The way to retain
power, I have always thought, is to ensure the absolute unthinkability
of oneself not being there."
-- Terry Pratchett _Unseen Academicals_ p391
--- End Message ---
Reply to: