** Tags removed: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to more duplicate filings
To manage notifications about this
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to more duplicate filings
To manage notifications about this
Hey, @ubuntu-johnwash. I agree @tafthorne's comment was long, but it
also went into more detail than mine (mine left some steps as "exercises
for the reader"). I'm glad I was able to summarize the key part for you
:-).
Yes, would be nice if a maintainer wanted to pick this up. I don't have
any
@kfogel: really? Is that what tafthorne's suggestion was? Well, in
that case, I agree, that's brilliant.
@tafthorne: why did I not realise how brilliant your suggestion was?
Simple. Because its length made me mutter 'tl;dr' and skip on to the
next. Please, if you're going to make further
+1 on @tafthorne's suggestion in comment#21 that there be a widget that
a maintainer can use to easily swap a private master bug with some
chosen public duplicate bug. (Actually, nothing about this widget is
specifically about private vs public, but I'll talk about it in those
terms here, since
This bug happened to me today. I found an easily reproducible bug in a
package, so because I am a helpful person, I did a fresh install just to
repro it in +1, and submitted a core dump through apport. Because I knew
for a fact that there was no private information in the clean install I
set my
reverting to Triaged.
** Changed in: apport (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to
Would 'Confirmed' be a more appropriate status than 'In progress'?
Indeed, given that this bug was reported over 5 years ago, even
mentioning the word 'progress' carries a touch of irony. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
changed to "in progress" as im not able to set it back to "triaged"
** Changed in: apport (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to more duplicate
I would like to +1 the idea of a
A. Public master bug
However I do not think is a job that apport could be expected to do safely. It
cannot interpret what data is safe to make public, what summary would be
helpful to future reports trying to determine duplicates or what should go in
the
For the record, http://errors.ubuntu.com is working really well these
days, and is the designated successor of using LP bugs. It solves the
privacy issue in a different way.
** Changed in: apport (Ubuntu)
Assignee: Martin Pitt (pitti) = (unassigned)
--
You received this bug notification
I'm not saying that the problem is easy to solve, but currently
errors.ubuntu.com do not solve it for me. I get the message:
Sorry, you are not a member of a group that is allowed to see the data
from error reports. A non-disclosure agreement is being written that
will allow for wider access.
I
Confirm that loging with our usual login/password on errors.ubuntu.com
fail with the error posted above (#19)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are
** Description changed:
Binary package hint: apport
Apport currently tracks the master bug as a private bug visible only to
Ubuntu developers (bugcontrol) and makes duplicate bugs public after
stripping their data.
This works well but has some downsides:
- Launchpad cannot show
(Preventing public duplicates of private bug reports is bug 396406,
discouraging it is bug 943497, and presenting it better is bug 434733.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
wouldn't the problem be solved if a private bug would only fence off the
attachments and leave the comments open? Now everyone can see what the bug is
about and check if it is the same bug they are troubled by while all sensitive
data remains protected.
As long as nobody is using the bugtracker
That would be an unsafe and confusing UI. Unsafe because if someone
pastes in private data from the private attachments, disclosure would
occur. Confusing because being able to see the bug but not the
attachments referred to in the bug is confusing.
--
You received this bug notification because
#14, @Robert. Someone who has access to private data and is
irresponsible or careless is always a danger, no more in this than any
other scenario. Obviously private attachments would need to be clearly
marked as private.
Why would it be confusing to have attachments marked 'private'? Private
Someone needs to fix apport, which we have determined is the root
cause of the problem; once apport is fixed, we can consider prevent
marking duplicates across visibility boundaries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just hit this same problem on submitting bug #975939.
There seems to be an assumption that a crash dump always contains data
that must be kept private. That isn't always true. If I'm testing a
beta and doing it on a scratch pc, even my login info is fake and would
not be a security risk if
hi Martin,
got a aptd crash on Precise i386 today, and apport identify it as a
duplicate of bug #639616 (wow so old one), seems too funny but not
serious, LTS coming out soon.
Hopes that whishlist does not mean never looked. Of course that
mysterious bug #639616 cant be checked, probably a
Per comments #6, #7, and #8, the code that generates the duplicate
notification email should check whether the recipient's account has
access to the original bug.
I still can't see the master bug report for my bug, despite that mine is
now public. This decreases the number of people who can
Same issue here.
Very confusing to the submitter as to what has happened.
I suspected it was a temporary dummy-spit from Launchpad and was considering
resubmitting as a natural reaction.
I'd like to be able to track the duplicate obviously in case I can
provide some useful test info when the
different bug same problem, can't see the original bug so don't know if I can
provide additional information or help in any way.
(https://bugs.launchpad.net/ubuntu/+source/nux/+bug/926769)
No way to help, no way to know if my issue will be fixed, no way to see
if there are workarounds. Not very
error ID OOPS-00f68b83cc60b5c0598f6e8179080f8c the bug i reported was
made public but marked as a duplicate to a private bug which i cant
access
the bug i reported
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/908486
which is marked as duplicate of this bug but which is at private
Please take as an example #829741 and #827164 (both public) which were
filed as a duplicate of #832029 (private!) by Apport retracing
service. The reminder window in the two original bug says that it is a
duplicate, and you should only comment when you think it is wrong. But
without seeing the
** Tags added: pet-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to more duplicate filings
To manage notifications about this bug go
- having potentially a two-times increase in open bugs
Not quite, I'd expect that the extra bug that apport would create to
move the private attachments to would be a duplicate of the master bug.
So it would add an extra dupe only, plus a link to the data dupe into
the description.
--
You
** Changed in: apport (Ubuntu)
Status: New = Triaged
** Changed in: apport (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: apport (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
Binary package hint: apport
Apport currently tracks the master bug as a private bug visible only to
Ubuntu developers (bugcontrol) and makes duplicate bugs public after
stripping their data.
This works well but has some downsides:
- - Launchpad cannot show
-1 to the proposed solution. I think it adds more problems than it
solves.
However, I agree with the premise that private apport crash reports
could use some improvements.
1. Stripping of private data (core dumps) to make bug public. This has
the problem that _sometimes_ you want to
@bryce do you mean 'veto' or 'dislike' with that -1? If the former can
you please explain the problems it adds so that we can iterate on the
approach and try to solve them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@robert, https://lists.ubuntu.com/archives/ubuntu-
devel/2011-April/033037.html
I've received your reply on that thread; you've acknowledged the issues
I raised as problems this would add. On several points you've offered
some arguments, however it doesn't change my mind. My concern/feedback
@Bryce I hadn't seen that before I commented - sorry for any confusion
added. I'm not aiming for a long debate, merely to find the cheapest
overall solution.
For folk just reading the bug report, the concerns are:
- having potentially a two-times increase in open bugs
- making it harder to
35 matches
Mail list logo
