Your message dated Mon, 30 Apr 2018 11:11:58 -0400
with message-id
<cab4xwxyk-uyyx8pk4zuuayqw+rku4vrswvggh3z2++lfjux...@mail.gmail.com>
and subject line Re: Bug#892270: [reportbug] Crash when report type set to None
has caused the Debian Bug report #892270,
regarding [reportbug] Crash when report type set to None
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 [email protected]
immediately.)
--
892270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 7.1.10
Severity: grave
--- Please enter the report below this line. ---
Reportbug (gtk2 ui) crash when i select package.
The command line output :
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2265, in <module>
main()
File "/usr/bin/reportbug", line 1109, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1721, in user_interface
latest_first=self.options.latest_first)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
1764, in func
args, kwargs = op.sync_pre_operation(*args, **kwargs)
TypeError: 'NoneType' object is not iterable
And when i start report bug with --test option there is no crash and the
commmand line output is :
invalid report type None, defaulting to debbugs
--- System information. ---
Architecture:
Kernel: Linux 4.14.0-3-amd64
500 testing ftp.fr.debian.org
--- Package information. ---
Depends (Version) | Installed
===================================-+-==============
python3:any |
apt | 1.6~beta1
python3-reportbug (= 7.1.10) | 7.1.10
sensible-utils | 0.0.11
python3:any (>= 3.3.2-2~) |
apt | 1.6~beta1
python3-debian | 0.1.32
python3-debianbts (>= 1.13) | 2.7.2
file | 1:5.32-2
python3-requests | 2.18.4-2
python3-apt | 1.4.0~beta3+b1
Package's Recommends field is empty.
Suggests (Version) | Installed
=====================================-+-============
postfix |
OR exim4 |
OR mail-transport-agent |
gnupg | 2.2.5-1
OR pgp |
debconf-utils (>> 1.1.0) |
debsums (>= 2.0.47) | 2.2.2
file (>> 1.30) | 1:5.32-2
dlocate |
python3-urwid |
python3-gi | 3.26.1-2
python3-gi-cairo | 3.26.1-2
gir1.2-gtk-3.0 | 3.22.28-1
gir1.2-vte-2.91 | 0.50.2-4
python3-gtkspellcheck | 4.0.5-1
xdg-utils | 1.1.2-2
emacs24-bin-common |
OR emacs25-bin-common |
claws-mail (>= 3.8.0) | 3.16.0-1
reportbug | 7.1.10
--- Output from package bug script ---
** Environment settings:
EMAIL="[email protected]"
DEBFULLNAME="BARDOT??Jerome"
** /home/jerome/.reportbugrc:
reportbug_version "6.6.5"
mode novice
ui gtk2
email "[email protected]"
no-cc
header "X-Debbugs-CC: [email protected]"
smtphost reportbug.debian.org
0x03878A98.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Thanks Nis for investigating this!
On Mon, Apr 30, 2018 at 10:54 AM, Bardot Jérôme <[email protected]> wrote:
>
> Hello
>
> Le 29/04/2018 à 23:43, Nis Martensen a écrit :
> > control: tags -1 unreproducible moreinfo
> > control: severity -1 important
> > This should normally not happen on any Debian system.
> > /etc/dpkg/origins/debian is the file from which the sysinfo['btsroot']
> > setting is populated. Did you modify any files in /etc/dpkg/origins/?
>
> But it is happen :)
>
> You re right, I can explain it.
>
> I needed some software (i use testing) from kali and i did a mistake
> update, upgrade with no kali source list # which modify
> /etc/dpkg/origins/debian
>
> After that i have to clean my system (kernel base-files, etc).
>
> But it’s look like the apt-get install --reinstall base-files not
> recreate /etc/dpkg/origins/debian. I will work on solve it soon.
>
>
> I don’t know if an error should be add in order to be more clear for the
> user.
Bardot, you managed your system in an unsupported way, after that you
failed to restore it to the correct configuration. you cannot expect
any tool to behave correctly if you do not follow debian procedures.
there is no message to be added to make it "more clear to the user".
once you diverge from debian practices, you're on your own.
I'm going to close this report as a user issue.
Regards,
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
--- End Message ---
