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

Bug#771030: marked as done (reportbug-ng: reportbug does not allow to edit bugreport, hangs)

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 #771030,
regarding reportbug-ng: reportbug does not allow to edit bugreport, hangs
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.)


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

Dear Maintainer,

I installed reportbug-ng and attempted to use it to report a bug in vlc. The reportbug-ng interface presented a dialog with the options including bug severity, short description, etc. On pressing 'OK' button reportbug-ng presented a dialog with further debug information for vlc, with only 'OK' button available. After pressing 'OK' button, reportbug-ng reverted to search screen. I did not know what to do at this point, as there had been no indication that a bugreport had been sent and I had expected to be asked for more information before sending the report. I chose "Additional Information" from the Bugs menu and reportbug-ng hung. It did not respond to any input so I used xkill to kill it.

I then checked bugs.debian.org and did not see any reference to the bug I had attempted to file. 

Then I started reportbug-ng again from a terminal and duplicated the steps above. This time, after pressing the OK button the second time, reportbug-ng returned to the search screen but the "Additional Information" item on the Bugs menu is grayed out.
Reportbug-ng did not hang again, but the following message:
ReportbugNG  WARNING  Mailbody to long for os.pipe
showed up on the terminal output.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-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/bash

Versions of packages reportbug-ng depends on:
ii  python            2.7.8-2
ii  python-apt        0.9.3.11
ii  python-debianbts  1.12
ii  python-qt4        4.11.2+dfsg-1
pn  python:any        <none>
ii  xdg-utils         1.1.0~rc1+git20111210-7.1
ii  xterm             312-1

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: