On Fri, Jan 25, 2008 at 12:03:59AM +0100, maximilian attems wrote:
> you have to repost to the other one.
> but be warned oops or bugs with tainted kernels don't get love here
> unless they are reproduced without proprietary crap.
I have resubmitted it to the correct bug number.
Please disregard
On Thu, 24 Jan 2008, Lennart Sorensen wrote:
> Any way to tell the bug system to move a message to another bug? Or to
> delete it so I can send it to the right bug?
you have to repost to the other one.
but be warned oops or bugs with tainted kernels don't get love here
unless they are reproduced
On Thu, Jan 24, 2008 at 04:08:23PM +0100, maximilian attems wrote:
> On Thu, Jan 24, 2008 at 09:43:03AM -0500, Lennart Sorensen wrote:
> > There is no reason what so ever to say it is a driver bug.
> >
>
> no idea what bug you are reffering to but your message seems
> in no way to correlate with
On Thu, Jan 24, 2008 at 09:43:03AM -0500, Lennart Sorensen wrote:
> There is no reason what so ever to say it is a driver bug.
>
no idea what bug you are reffering to but your message seems
in no way to correlate with 461182 that still misses quite some
output in order to be useful.
--
To UN
There is no reason what so ever to say it is a driver bug.
kwin crashes with the nvidia driver. kwin should not crash no matter
what garbage the driver may return to it. It can detect that it got bad
data back and give an error, but a crash is simply sloppy coding and
hence a bug in kwin. There
5 matches
Mail list logo
