Apport retracer dupes bugs that aren't dupes

Bug #861645 reported by Scott Kitterman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Bug #861560 was marked a duplicate of Bug #629753, but it's not.

They are close, but not the same:

Traceback:
 Traceback (most recent call last):
   File "/usr/share/kde4/apps/printer-applet/monitor.py", line 376, in get_notifications
     jobid = event['notify-job-id']
 KeyError: 'notify-job-id'

Traceback:
 Traceback (most recent call last):
   File "/usr/share/kde4/apps/printer-applet/monitor.py", line 394, in get_notifications
     attrs['job-originating-user-name'] != cups.getUser ()):
 KeyError: 'job-originating-user-name'

This is in a slightly different part of the code and although the error class (KeyError) is the same, the missing key is different. These bugs shouldn't be duped.

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in apport (Ubuntu):
status: New → Incomplete
Revision history for this message
Scott Kitterman (kitterman) wrote :

9 years later. Lovely. I don't even use Ubuntu anymore.

Changed in apport (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

I'm so sorry this issue went unanswered for 9 years.. The backlog we've accrued here is truly unfortunate. We'd really like to see the situation improve, but with nearly 1300 open bugs, manually testing each has become virtually impossible. The aim in pinging neglected bugs such as this was to allow those still effected to get their issue back on the radar.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 861645] Re: Apport retracer dupes bugs that aren't dupes

On Friday, March 6, 2020 2:49:21 AM EST you wrote:
> I'm so sorry this issue went unanswered for 9 years.. The backlog we've
> accrued here is truly unfortunate. We'd really like to see the situation
> improve, but with nearly 1300 open bugs, manually testing each has
> become virtually impossible. The aim in pinging neglected bugs such as
> this was to allow those still effected to get their issue back on the
> radar.

Don't worry about it. I was a very active Ubuntu developer at one point, so I
totally understand. I was just in a bad mood yesterday for other reasons.

On the off chance you manage to remember, if you notice any of these filed by me
in the future, feel free to close them without the ping. If you don't notice,
that's fine too.

Scott K

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

Thanks for your understanding Scott.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.