I have to get this out, I am sorry. Intrepid is in *alpha*, I don't
have non-production machines, this is an absurd request to a person
who took the time to find the bug. Its like asking them to your job
for you.
This is the trend I see in Ubuntu bug reporting. User files bug, no
one looks at it for months, then they mark it as lacking information
(when it does not, I even have the steps to reproduce it and have
filed the bug against hardy *not* intrepid), they expect users to do
some kind of massive test report for them and because they don't they
finally mark the bug closed. Hurray, problem solved.
This is the second of my bugs where I have been asked to devote some
unusual amount of time to provide more information. I feel it to be
completely unnecessary since some time spent by the developer on the
problem can solve it. This is just a way of moving responsibility
around.
I ain't filing any more bugs.
Good luck with everything,
Akshay
On Wed, Sep 24, 2008 at 7:39 AM, Pedro Villavicencio <email address hidden> wrote:
> We are closing this bug report because it lacks the information we need
> to investigate the problem, as described in the previous comments.
> Please reopen it if you can give us the missing information, and don't
> hesitate to submit bug reports in the future. To reopen the bug report
> you can click on the current status, under the Status column, and change
> the Status back to New. Thanks again!.
>
> ** Changed in: evince (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> new files opened in evince does not bring its window to top
> https://bugs.launchpad.net/bugs/224867
> You received this bug notification because you are a direct subscriber
> of the bug.
>
I have to get this out, I am sorry. Intrepid is in *alpha*, I don't
have non-production machines, this is an absurd request to a person
who took the time to find the bug. Its like asking them to your job
for you.
This is the trend I see in Ubuntu bug reporting. User files bug, no
one looks at it for months, then they mark it as lacking information
(when it does not, I even have the steps to reproduce it and have
filed the bug against hardy *not* intrepid), they expect users to do
some kind of massive test report for them and because they don't they
finally mark the bug closed. Hurray, problem solved.
This is the second of my bugs where I have been asked to devote some
unusual amount of time to provide more information. I feel it to be
completely unnecessary since some time spent by the developer on the
problem can solve it. This is just a way of moving responsibility
around.
I ain't filing any more bugs.
Good luck with everything,
Akshay
On Wed, Sep 24, 2008 at 7:39 AM, Pedro Villavicencio <email address hidden> wrote: /bugs.launchpad .net/bugs/ 224867
> We are closing this bug report because it lacks the information we need
> to investigate the problem, as described in the previous comments.
> Please reopen it if you can give us the missing information, and don't
> hesitate to submit bug reports in the future. To reopen the bug report
> you can click on the current status, under the Status column, and change
> the Status back to New. Thanks again!.
>
> ** Changed in: evince (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> new files opened in evince does not bring its window to top
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>