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

Bug#806681: marked as done (reportbug: Improve feedback "unable to connect to debian.org" after opening email client)

Your message dated Sat, 5 Dec 2020 21:42:14 +0100
with message-id <c7605bf7-8a54-29bc-c5c1-93d3abc62e67@web.de>
and subject line Re: Bug#806681: reportbug: Improve feedback "unable to connect to debian.org" after opening email client
has caused the Debian Bug report #806681,
regarding reportbug: Improve feedback "unable to connect to debian.org" after opening email client
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.)


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

Dear Maintainer,

After opening the local email client the operation fails with an very vague error message like
"unable to connect to debian.org". This error message has to contain the requested URI, the protocol status code and error
message as well as suggestions how to proceed in order to be of any use for the user.

This report is about the specific mentioned feedback. The fact that it's possible to figure out a correct configuration which
avoids this issue doesn't affect it.


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

** /home/richter/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui text
realname "Karl-Philipp Richter"
email krichter@posteo.de
smtphost posteo.de:587
smtpuser krichter@posteo.de
smtppasswd <omitted>
smtptls

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 3.16.0-4-powerpc
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt               1.0.9.8.1
ii  python            2.7.9-1
ii  python-reportbug  6.6.3
pn  python:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
pn  debconf-utils                              <none>
pn  debsums                                    <none>
pn  dlocate                                    <none>
pn  emacs23-bin-common | emacs24-bin-common    <none>
ii  exim4-daemon-light [mail-transport-agent]  4.84-8
ii  file                                       1:5.22+15-2
ii  gnupg                                      1.4.18-7
pn  python-gtk2                                <none>
pn  python-gtkspell                            <none>
pn  python-urwid                               <none>
pn  python-vte                                 <none>
pn  xdg-utils                                  <none>

Versions of packages python-reportbug depends on:
ii  apt               1.0.9.8.1
ii  python-debian     0.1.27
ii  python-debianbts  1.12
pn  python:any        <none>

python-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sun, 29 Nov 2015 23:54:52 +0000 Sandro Tosi <morph@debian.org> wrote:

control: tag -1 +moreinfo

On Sun, Nov 29, 2015 at 11:47 PM, Karl-Philipp Richter
<krichter@posteo.de> wrote:
> After opening the local email client the operation fails with an very vague error message like
> "unable to connect to debian.org". This error message has to contain the requested URI, the protocol status code and error
> message as well as suggestions how to proceed in order to be of any use for the user.

what is generating the error message? I suspect the MUA as reportbug
correctly reports those information (check from the command-line);
please clarify
This report is quite unclear as to when exactly the problem occurs, and does not describe the exact error message either. It also does not explain the role of the local email client. 

No more info has been provided in 5 years, closing now.

--- End Message ---
Reply to: