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

Bug#706421: marked as done (reportbug-ng will not send bugs: fails invoking mail client)



Your message dated Fri, 15 Feb 2019 20:55:13 +0000
with message-id <E1gukVt-0004Xs-DV@fasolo.debian.org>
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #706421,
regarding reportbug-ng will not send bugs: fails invoking mail 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.)


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

Dear Maintainer,
This warrants higher severity if it's not caused by something weird on
my system.  May be related to 699169 and 440568.

   * What led up to the situation?
Launched reportbug from KDE4, selected kdesvn, report a new bug.
Dialog appears, which I filled out and hit OK.
Something flashed very fast on the screen and then disappeared,
leaving the dialog unchanged.
mutt is configured as my mail client; it is on the system.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Looked at .xsession-errors.
Launched from command line to look for errors.
Tried submitting a bug on a different package (reportbug-ng) with
normal priority (earlier one was minor priority).

   * What was the outcome of this action?
Nothing very promising in .xsession; I've done my best to excerpt a
section created while I was doing these experiments (below).
Nothing at all on the terminal.

   * What outcome did you expect instead?
An editor with my bug report coming up.


Comment: I am using a remote host for mail sending, though exim is
running locally (it can't send out).
A day or two ago I successfully submitted a bug via report bug (I
think); I'm not sure what's different now.  I have been updating the
system and adding packages to it; it is a fresh wheezy install.

kmail is also on the system.

<.xsession-errors>
plasma-desktop(6471)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(6471)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Error, cannot create transaction proxy 
QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get owner of name 'org.freedesktop.PackageKit': no such name") 
plasma-desktop(6471)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
[/usr/bin/nepomukservicestub] virtual void Soprano::Server::LocalServer::incomingConnection(quintptr) 
void Soprano::Server::ServerCorePrivate::addConnection(Soprano::Server::ServerConnection*) New connection. New count: 12
[/usr/bin/nepomukservicestub] Soprano::ODBC::Connection::Connection() Soprano::Server::ServerConnection(0x7f83b4037370)
void Nepomuk::Query::QueryServiceClient::close() 
void Nepomuk::Query::QueryServiceClient::close() 
void Nepomuk::Query::QueryServiceClient::close() 
void Nepomuk::Query::QueryServiceClient::close() 
[/usr/bin/nepomukservicestub] virtual void Soprano::Server::ServerConnection::run() thread done.
[/usr/bin/nepomukservicestub] virtual Soprano::ODBC::Connection::~Connection() Soprano::Server::ServerConnection(0x7f83b4037370) 
void Soprano::Server::ServerCore::serverConnectionFinished() 
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection
[/usr/bin/nepomukservicestub] void Soprano::Server::ServerCore::serverConnectionFinished() Connection removed. Current count: 11
</.xsession-errors>

<.reportbug-ng>
[general]
lastmua = mutt
sortbycol = 4
sortasc = False
script = True
presubj = True
wishlist = #808000
minor = #008000
normal = #000000
important = #ff0000
serious = #800080
grave = #800080
critical = #800080
resolved = #a0a0a4

[mainwindow]
x = 0
y = 0
width = 1752
height = 1054
menubar = True

[listview]
bugnrwidth = 100
summarywidth = 1088
statuswidth = 100
severitywidth = 100
lastactionwidth = 100
hideclosedbugs = True


</.reportbug-ng>
*** End of the template - remove these lines ***


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages reportbug-ng depends on:
ii  python            2.7.3-4
ii  python-apt        0.8.8.2
ii  python-debianbts  1.11
ii  python-qt4        4.9.3-4
ii  python-support    1.0.15
ii  xdg-utils         1.1.0~rc1+git20111210-6
ii  xterm             278-4

reportbug-ng recommends no packages.

reportbug-ng suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 2.2+rm

Dear submitter,

as the package reportbug-ng has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/922382

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply to: