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

Bug#966561: marked as done (reportbug: lock screen button and the equivelent - it going asleep;inactivity - force me to solve by power button thus i lose my work)



Your message dated Thu, 30 Jul 2020 22:35:55 +0200
with message-id <3008f56e-88fb-3688-6561-691fad98e604@web.de>
and subject line Re: Bug#966561: reportbug: lock screen button and the equivelent - it going asleep;inactivity - force me to solve by power button thus i lose my work
has caused the Debian Bug report #966561,
regarding reportbug: lock screen button and the equivelent - it going asleep;inactivity - force me to solve by power button thus i lose my work
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.)


-- 
966561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966561
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.5.3~deb10u1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/garreth/.reportbugrc:
reportbug_version "7.5.3~deb10u1"
mode novice
ui gtk
realname "Sean"
email "g1800@gmx.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt                1.8.2.1
ii  python3            3.7.3-1
ii  python3-reportbug  7.5.3~deb10u1
ii  sensible-utils     0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                              <none>
pn  debconf-utils                           <none>
pn  debsums                                 <none>
pn  dlocate                                 <none>
pn  emacs-bin-common                        <none>
ii  file                                    1:5.35-4+deb10u1
ii  gnupg                                   2.2.12-1+deb10u1
pn  postfix | exim4 | mail-transport-agent  <none>
pn  python3-urwid                           <none>
ii  reportbug-gtk                           7.5.3~deb10u1
ii  xdg-utils                               1.1.3-1+deb10u1

Versions of packages python3-reportbug depends on:
ii  apt                1.8.2.1
ii  file               1:5.35-4+deb10u1
ii  python3            3.7.3-1
ii  python3-apt        1.8.4.1
ii  python3-debian     0.1.35
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1
ii  sensible-utils     0.0.12

python3-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hey Sean,

Thank you for using reportbug. However, your report is missing any
details that would allow us to identify the exact problem, therefore it
is not possible to resolve it. Hence I'm closing this bug.

Notice that you have filed this bug against the 'reportbug' package. The
description you provide in the subject line does not provide any
indication that your problem is at all related to this specific package.

Please, when filing a bug:
 - Identify the correct package with the buggy program. If you don't
   know it, you can use the 'general' pseudopackage, but it is unlikely
   that you'll receive much support there. The more detail you can
   figure out yourself the better.
 - Instead of providing the entire description in the message subject,
   follow the instructions in the message template and replace
   the text from the template with the proper information. I'm referring
   to the part of your message quoted below.

Thanks!


On 30.07.2020 19.53, Sean wrote:
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    * What was the outcome of this action?
>    * What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***

--- End Message ---

Reply to: