lubuntu-qa team mailing list archive

[Jackson Doak <doak.jackson@xxxxxxxxx>]

i reccomend you make a new bug and mark the original as a duplicate of it.
that should stop anyone being offended


On Fri, Apr 19, 2013 at 11:47 AM, Aere Greenway
<Aere@xxxxxxxxxxxxxxxxxxxx>wrote:

> All:
>
> The original bug (in the attached e-mail) was declared invalid because it
> happened on a machine that doesn't meet the minimum system requirements of
> Ubuntu/Unity-Desktop, even though I was using Lubuntu.
>
> I since observed it to occur on a machine within the Ubuntu minimum system
> requirements, and the attached e-mail came as a result of reporting that
> event.
>
> Yet the bug:
>
> https://bugs.launchpad.net/**bugs/1159589<https://bugs.launchpad.net/bugs/1159589>
>
> Still shows up as being invalid.
>
> I am wondering if once a bug is declared to be invalid, that nobody ever
> sees it again, or any additional information posted to it - kind of a
> black-hole that sucks up any additional information, consigning it to some
> bit-bucket.
>
> In light of the fact that I was using Lubuntu in the first place, and that
> I have observed it happening on a machine running Ubuntu Unity-Desktop (and
> within the minimum system requirements of Ubuntu/Unity), is there any way
> the bug can be re-classified as something that needs to be looked at?
>
> - Aere
>
> --
> Mailing list: https://launchpad.net/~lubuntu-qa
> Post to     : lubuntu-qa@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~lubuntu-qa
> More help   : https://help.launchpad.net/ListHelp
>
>