the person who registered it could not access it to view /
>> > > update etc.
>> > >
>> > > I had a chat with the bug squad about this. If this happens they ask
>> > > that you go to #ubuntu-bugs and raise it with them. The bot does go
>> >
appens they ask
> > > that you go to #ubuntu-bugs and raise it with them. The bot does go
> > > trawling for duplicated bugs, but it is not aware if the bug it is
> > > using as master is private. I'll get the wiki area updated.
> >
> > To expand a bit m
go
> > trawling for duplicated bugs, but it is not aware if the bug it is
> > using as master is private. I'll get the wiki area updated.
>
> To expand a bit more on it: there are two major types of private bugs:
>
> (this is centered on Ubuntu, but should be simila
;ll get the wiki area updated.
To expand a bit more on it: there are two major types of private bugs:
(this is centered on Ubuntu, but should be similar on other projects,
like Lubuntu)
* born private (usually security and apport crashdump bugs)
* made private later on.
The apport crashdumps are
On Tuesday, September 04, 2012 06:35:58 PM Phill Whiteside wrote:
> Hi folks,
>
> recently a bug reported by a QA member was marked as a duplicate (no harm
> there), but the 'master' bug was set as 'private'. This meant that the
> person who registered it could not access it to view / update etc.
a updated.
>
> Regards,
>
> Phill.
>
>
>
That is a good idea :-) I have had problems with unreadable private bugs
too.
--
Ubuntu-qa mailing list
Ubuntu-qa@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Hi folks,
recently a bug reported by a QA member was marked as a duplicate (no harm
there), but the 'master' bug was set as 'private'. This meant that the
person who registered it could not access it to view / update etc.
I had a chat with the bug squad about this. If this happens they ask that
y
