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

Bug#631621: marked as done ([reportbug-ng] Crash on not readable source.list.d/file)



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 #631621,
regarding [reportbug-ng] Crash on not readable source.list.d/file
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.)


-- 
631621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631621
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---

Package: reportbug-ng

Version: 1.24

Severity: normal


--- Please enter the report below this line. ---


I did start report-ng for the first time and it did crash with the following output:


Traceback (most recent call last):

File "/usr/bin/reportbug-ng", line 72, in <module>

gui = RngGui(args)

File "/usr/share/reportbug-ng/rnggui.py", line 43, in __init__

self.setupUi(self)

File "/usr/share/reportbug-ng/ui/mainwindow.py", line 29, in setupUi

self.lineEdit = PackageLineEdit(self.centralwidget)

File "/usr/share/reportbug-ng/ui/packagelineedit.py", line 15, in __init__

cache = FilteredCache(Cache())

File "/usr/lib/python2.6/dist-packages/apt/cache.py", line 93, in __init__

self.open(progress)

File "/usr/lib/python2.6/dist-packages/apt/cache.py", line 140, in open

self._list.read_main_list()

SystemError: E:Opening /etc/apt/sources.list.d/opera.list - ifstream::ifstream (13: Permission denied)



The file opera.list was only readable for user root (-rw-------). Making it readable for all did solve the problem.


So IMHO reportbug-ng should check the accessability of the file and either report it in a more userfriendly way, or if the information is optional, just print a warning and continue without this file.


Greetings,

Gert


--- System information. ---

Architecture: amd64

Kernel: Linux 2.6.39-2.slh.1-aptosid-amd64


Debian Release: wheezy/sid

500 unstable ftp.uni-erlangen.de

500 unstable debian.netcologne.de

500 unstable deb.opera.com


--- Package information. ---

Depends (Version) | Installed

================================-+-============

python | 2.6.6-14

python-support (>= 0.90.0) | 1.0.13

python-debianbts (>= 1.0) | 1.10

python-qt4 | 4.8.3-2+b1

xdg-utils | 1.1.0~rc1-2

xterm | 270-1

python-apt (>= 0.7.93) | 0.8.0



Package's Recommends field is empty.


Package's Suggests field is empty.






--- 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: